I know some folks out there recommend not to rename the built-in administrator in Windows Server 2003. Instead, create another admin account with the same privileges and disable the built-in administrator account. But what if the situation is that I need to rename the administrator account? What would be the best procedure to do this without affecting my Exchange Server 2007, Other Member File Servers and Blackberry Enterprise Server? We've been using the administrator account to login to our windows servers as well as the other servers we have. What would be the step by step approach I need to do to ensure that the moment the administrator's name is renamed, my remaining servers will not crash. For sure there are certain situations where some software's installed as a service in windows would be affected and perhaps after the administrator name has been renamed, I probably need to go into each services on every windows server I have and start editing any software service that uses the administrator name when logging in before restarting each server? I appreciate everyone's advice. Thank you.
Open Group Policy Management, and the setting is found at
I can't think of any reason to not rename it on the Exchange server, but you can always create an OU that excludes Group Policy Inheritance and put the Exchange server in there, or use WMI filtering on the Group Policy to specifically exclude the Exchange server.
As far as installed software and services running as the Administrator account, that's both very bad, and not a default behavior on anything I'm familiar with. So, hopefully, you're worrying about nothing... and if not, it might be worth breaking that just so you can find and correct services running as the Administrator - create and use service accounts instead.
Nothing you've described will crash. Internally, Windows uses the SID, not the display name. That name is just there to be human-readable and friendly.