Ryan Adams (4/30/2012)
You are right about being able to alter that SP, but what happens when you install a CU or SP that changes it back? Although it can be done, it is not a good practice or reliable method. It would be better to use a workaround and use an alias when you create the connection so it looks the way you want it to.
Here is a link to a post on my blog where I go into this in more detail.
How to add your CMS server to a group[/url]
I fully agree with your point that's why I mentioned this is not a good practice and to do it at your own risk.
If a CU or a SP would change it back, no problem, the server would already be registered. It will only matter if you wanna update the concerned server (as the update stored procedure could have been roll backed as well).
Another point which might be blocking in case of a CU or SP would be if Microsoft would place a check constrain on the underlying table.
Do you think Microsoft plan to put time in that ?
When I looked up for the "update stored procedure solution", I was thinking about how to export/import a list of server from one box to another.
Using your workaround, you would need to replace all entries pointing to the receiving server in the exported file with the "tricked alias" and rename the entries of the source server having uncommon naming before importing it completely and cleanly.
Well both solutions, according to me, have pro and cons - it makes IT charm 😉
One question I still have in mind regarding this "restriction" is why has it been put in place and what is its added value ?
I would be glad to hear about potential side effect of working it around in anyway 🙂