Is there a way to distribute EM registrations ?
-
Is there a way to distribute EM registrations ?
We are getting all our clients reinstalled
Can I save and recall my EM settings and/or distribute them to other dba-s.
I've got 100+ registered servers at diffirent (sub)domains (sqlserver groups) and windows-domains.
tia
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data and code to get the best help- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Yes you can. Search in the registry for the servers you have registred in combination with EM. Export the key and sub-key's to a reg-file and distribute the reg-file to the other workstations.
If you cannot find it, I will look tomorrow for the right key, but it should be no problem to find it I think.
-
I've tested export of regestry keys "registered servers x" and "MSSQLserver" (with subkeys), but that did not do the trick
That only gives me the servergroups, but no actual server appears
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data and code to get the best help- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
I wil look into it, later today and reply.
-
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered Servers X]
And subkey's should do the trick.
Remember to close EM before you start. It worked fine for me... Just tested it and it worked.
-
Thanks for the testing.
Can you clarify your scenario ?
( from pc A to pc B ?  
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data and code to get the best help- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
I will try on a pc from my co worker
-
You are right. On other pc's it will not work...
-
indeed.
I guess there are other reg-keys which store the info in HEX and get a nice guid-like reg-key.
The quest goes on....
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data and code to get the best help- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Try in EM: Tools, Options, Server Registration Information. Maybe that can be of help for you?
If you can get it working I would be greatly interested in how. I get error's all the time...
From SQL Books On Line:
How to set up a central store for server registration information (Enterprise Manager)
To set up a central store for server registration information on a remote server
- Click the server, and then on the Tools menu, click Options.
- On the General tab, clear the Read/Store user independent check box.
- Use SQL Server Enterprise Manager to create server groups and register servers.
To set up a central store for server registration information on a local server
- Click the server, and then on the Tools menu, click Options.
- On the General tab, click Read from remote.
- In the Server name box, type the name of the remote server from which you want to use registration information.
-
The previous suggestion is what we use. You don't have to export and apply registry files. You just set up the registrations on a central server and have all the DBAs point to that server by using "Tools, Options, Read from remote".
But there's a problem with that. It works if the central server is Win NT but not Win 2000. Microsoft has documented it here - http://support.microsoft.com/default.aspx?scid=kb;en-us;280836&Product=sql2k. Apparently they don't plan to fix the problem.
-
Thanks for all the replies.
"Helas" all our central servers are already migrated to W2k or W2k3 .
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data and code to get the best help- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Same here...
[off topic] 'Helas' ? not 'Helaas'? Dutch? [/off topic]
- I have a similar situation: 100+ servers registered, multiple DBA's needing updated registration info, new DBA machines added or rebuilt, and also many servers added at different points in time.The registry save/restore did the trick on SQL7/NT4 for us, but not anymore on SQL2K/W2K (consistent with previous posts, also the centralized location for registrations was not working).We solved it with a DMO script running on the DBA workstation, saving registrations into a text file, and running the same script with the text file as a parameter of the same script to rebuild registration info. This also helps when deploying a bunch of servers: you can easily pre-register them without having them actually there. I can provide you the script, but I don't have it here right now. Please contact me to gustavo_merle at hotmail if you are interested in the script, I am not continuosly following these threads.Interesting side-note: our testing showed that standard security passwords are exposed by DMO without any restriction if you have access to the DBA workstation. Makes another good point for not using standard security. But if it is unavoidable, at least always use the "user independent" registration option ..., from another login you will not get access to them.RegardsGustavo
Viewing 14 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply