changing AD domains with SS2005

We have the need to move a sql server 2005 server from domain “a” to dom
ain “b”
Is there anything such as certain store procedures to run or gotchas to be
looking out for to do this move between domains?
Thanks
-JasonHello Jason,
Based on my scope, SIDhistory does not work for this situation. After you
migrate the server to the new doamin, you have to migrate users of the old
domain to new domain so that the new domain users could have the same
permssions.
First, you need to transfer logins of old domain to new domain.
How to transfer the logins and the passwords between instances of SQL
Server 2005
http://support.microsoft.com/kb/918992/
Then you need to maintain the mapping between the logins in the master
database and the users in the user database by using the SIDs. This mapping
is necessary to maintain correct permissions for the logins in the user
databases. In SQL 2000, you could use the sp_sidmap stored procedure
mentioned in the following article to map SIDs for logins between original
and new server:
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
However, in SQL 2005, sp_SidMap doesn't work because it needs to write to
system table directly. You may need to develop a script to do the job
manually.
Please refer to the following article for more related information:
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
If you have any further concerns, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||what about the local groups that were created on the server at install?
e.g. SQLServer2005MSSQLServerADHelperUser$
and SQLServer2005MSSQLUser$
etc.
""Peter Yang[MSFT]"" wrote:

> Hello Jason,
> Based on my scope, SIDhistory does not work for this situation. After you
> migrate the server to the new doamin, you have to migrate users of the old
> domain to new domain so that the new domain users could have the same
> permssions.
> First, you need to transfer logins of old domain to new domain.
> How to transfer the logins and the passwords between instances of SQL
> Server 2005
> http://support.microsoft.com/kb/918992/
> Then you need to maintain the mapping between the logins in the master
> database and the users in the user database by using the SIDs. This mappin
g
> is necessary to maintain correct permissions for the logins in the user
> databases. In SQL 2000, you could use the sp_sidmap stored procedure
> mentioned in the following article to map SIDs for logins between original
> and new server:
> 240872 HOW TO: Resolve Permission Issues When You Move a Database Between
> http://support.microsoft.com/?id=240872
> However, in SQL 2005, sp_SidMap doesn't work because it needs to write to
> system table directly. You may need to develop a script to do the job
> manually.
> Please refer to the following article for more related information:
> 314546 HOW TO: Move Databases Between Computers That Are Running SQL Serve
r
> http://support.microsoft.com/?id=314546
> If you have any further concerns, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ========================================
==========
> Get notification to my posts through email? Please refer to
> l]
> ications
> <[url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx" target="_blank">http://msdn.microsoft.com/subscript...ps/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscript...rt/default.aspx>.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hello Jason,
These groups are for internal purpose which gets created during the time of
installation. You don't need to worry about the groups when migrating since
they are related to the local server other than the domains.
If you have any further quesitons or concerns, please feel free to let's
know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
========================================
=============
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.sql