Export SQL Servers registration using Management Studio?
If you are managing hundreds of SQL Server and you might have organised your Management Studio screen with relevant server groups under Server registration. In this case if a new starter has joined and required to assist you in monitoring all of the SQL Server you are taking care, you wouldn't attempt or anyone to register each of the server when you have nearly 500 SQL instances to manage.
Until SQL Server 2000 this was a big problem to import and export the Server instance registations, there wasn't any easy way to do or rather you should import/export registry keys from the client's machine. Majority of them never worked due to the implications of security policy and privileges by the user on that machine, anyway that is irrelevant here.
So from SQL Server 2005 onwards there is an easy way to perform this task by simply saving and exporting the registered server information to distribute among your colleagues or servers. SQL Server Management Studio aka SSMS has this this export feature to present a consistent user interface on multiple computers, to accomplish this follow:
Open SSMS on your machine
Choose Registered Servers, right-click a server group, and then click Export
The default feature is it will attempt to export all of the registered server tree, or a subset of the registered server tree and similarly you can choose to export an individual server. On an enterprise wide network it is a best practice to save the registered server information to be available to other users or another computer by saving the export file on a network share where other users can access the file and import part or all of the registered server information without disturbing you for each and every server.
If you have SQL instances that are using SQL authentication then ensure to select Do not include user names and passwords in the export file although passwords are never exported as part of the export file. Refer to this MSDN http://technet.microsoft.com/en-us/library/ms186292.aspx article too.