Monday, July 18, 2011 4:56 PM
We have a mix of SQL 2000 and SQL 2005 environments sitting on Windows 2003. They are sitting on a old domain which was part of an old take over. We are now cutting over to a new domain. Our goal is to simply remove the server from the old domain and join the new domain. We have a few SQL services that are tied into the old domain admin account. I looked online and a few users have asked the same question but I haven't come across any clear method to approach this. Does anyone know what steps should be taken so SQL doesn't fall apart after the domain name change? Let me know if additional info is required.
Thanks in advance!!!
Monday, July 18, 2011 6:12 PMModerator
Yes, you can do it, but you may have issues with the Windows logins. To solve those issues please read the following post by Joe Wu (MSFT):
I would change accounts used for SQL Server services from domain accounts to local accounts, before moving the server from one domain to another.
Hope this helps.
Tuesday, July 19, 2011 2:47 AMModerator
In addition, here are some basic steps to move your SQL Server box to a new domain:
- Remove all logins for current domain accounts/groups
- Make sure you have one login with sysadmin permissions, use which we can manage the instance after moving to new domain such as adding new logins. This login can be either a local Windows account or SQL Server Login account.
- Change all SQL Server service accounts from domain account to local Windows accounts or builtin accounts.
- Change the computer domain in the System Properties -> Computer Name/Domain Changes.
- After changing the domain, you can update SQL Server service accounts and add appropriates new domain logins in SQL Server.
Hope this helps.
Alex Feng | Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact firstname.lastname@example.org.
- Marked As Answer by Alex Feng (SQL)Moderator Monday, July 25, 2011 2:57 PM