• In lieu of using extended properties, I've done something similar with a table that maps 1-1 to the sysmanagment_shared_registered_servers, creating a central repository for all the server meta-data.

    We're still in the same predicament as you with many undocumented servers and many stakeholders, but it is getting better as a result of CMS. We're also spitting out a dynamic Sharepoint spreadsheet from the data for those more comfortable working from Excel, as well as a weekly spreadsheet to be used as a backup in the event of the CMS server failing.

    I am toying with the idea of extended properties on the individual databases, but frankly we're just not that far along yet.

    Also, I have grouped our servers by edition in CMS, as many of our scripts used in multi-instance queries do not work with SQL 2000, as I'm sure you have discovered.