SharePoint migrating domains

1
votes

I need to migrate our SharePoint farm to a new domain. Until everything is moved we have full trust set up between the domains.

Farm Hardware

One WFE/Index Server

Two SQL DB Servers (clustered)

I know how to do this using all new hardware from production to a dev environment but doing an in place migration seems more daunting. To take some of the pressure off we have a new beefy SharePoint box to install to that will be a fresh box on the new domain but we don't have enough hardware to have a separate SQL cluster.

I am told that all the boxes should be on the same domain so now the hard part is to bring the SQL box on the new domain. Can I just switch domains on the SQL DB cluster and then install SP on the new WFE?

3
sharepointsharepoint-2007active-directorymigrationcross-domain
You should ask this question on ServerFault.com . – Flo

3 Answers

1
votes

Voted to move to serverfault, but here's my 2 cents. Moving SQL Server 2 a new domain is easy, sql server will pick up any changes. The problem is sharepoint. SharePoint users to be exact. Any documents in your site(s) will have it's created by / modified by broken, because even though the same users exist in the new domain, the bindings will be incorrect, sharepoint expects for instance user [email protected], which is very different from user [email protected]. There is a way around this using httpmodules etc, but it is a pain in the ass.

Check out the result when googling migrate sharepoint new domain.

0
votes

I've run a similar setup before. If they're full trust, you should be able to reconnect to your pre-existing config/content dbs from the new SharePoint instance in the new domain.

0
votes

  • SQL server You can have your SQL server in a different domain as long as there is a trust between the domains.

  • Migrating users With regards to migrating your users, it's a daunting task because those user's SIDS own objects, I've used stsadm -o migrateuser but it's not terribly helpful, I'd consider looking into 3rd party software such as DocAve who have products that assist in migrating SharePoint content. If you really want to hack it, break open the Users table in your content databases and write a script to update the usernames and sids.