Moving SQL Server 2000 to a new Domain

Hi,
Shortly, we will be migrating out exchange environment into a new AD
forest...
As we have a few SQL 2000 servers in the domain that is to be replaced,
are there any articles that describe the process of moving a SQL 2000
server into a new domain?
ThanksHi
1. Backup your SQL Server databases and copy them to another machine
2. Change SQL Server accounts to local system.
3. Restart SQL server and verify correct operation.
4. Stop and disable SQL Server Services.
5. Move the machine to the other domain
4. Enable SQL Server Services.
6. Start SQL Server
7. Change the service accounts to the new domains accounts (as per the 2
KB's below)
8. Restart the server to verify correct operation.
http://support.microsoft.com/defaul...kb;en-us;283811
http://msdn.microsoft.com/library/d.../>
ll_4yi1.asp
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Steven Bellamy" wrote:

> Hi,
> Shortly, we will be migrating out exchange environment into a new AD
> forest...
> As we have a few SQL 2000 servers in the domain that is to be replaced,
> are there any articles that describe the process of moving a SQL 2000
> server into a new domain?
> Thanks
>|||Thanks for the response, I'll look into this further...
Steven
Mike Epprecht (SQL MVP) wrote:
> Hi
> 1. Backup your SQL Server databases and copy them to another machine
> 2. Change SQL Server accounts to local system.
> 3. Restart SQL server and verify correct operation.
> 4. Stop and disable SQL Server Services.
> 5. Move the machine to the other domain
> 4. Enable SQL Server Services.
> 6. Start SQL Server
> 7. Change the service accounts to the new domains accounts (as per the 2
> KB's below)
> 8. Restart the server to verify correct operation.
> http://support.microsoft.com/defaul...kb;en-us;283811
> http://msdn.microsoft.com/library/d...yi
1.asp|||If you have SQL logins associated with the first domain. Database users
that are mapped from those logins will become orphaned and you need to map
those users to new logins. Even if you create the new domain accounts with
the same name as the old ones, their SIDs will be different. So, such NT
logins might be invalid after the moving to the new domain. Since each
Database User needs to be mapped to a valid login, you might see some
orphaned db users. This is somewhat similar to the situation when a
database is moved from one SQL Server to another in a different domain,
there can be a mismatch between the SIDs of the logins in the master
database and the users in the user database.
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/defaul...kb;EN-US;274188
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.