Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1074
  • Last Modified:

Moving Sharepoint WSS 3.0 to another domain

As a part of an interforest migration, I need to move the WSS 3.0 server to the new domain. There is a trust that exists, but that will be broken at the end.
I am planning to use ADMT to move the user the accounts across and then add WSS to the new domain, first will this workor am I missing a step? What other considerations do I need to take into account as a part of this migration?

Many thanks in advance for the help.
0
mandalj
Asked:
mandalj
  • 5
  • 3
  • 3
3 Solutions
 
Christopher WhiteSenior EngineerCommented:
Hi

I have moved sharepoint from development domains to production domains, and the process is really straight forward.

Important changes

Farm Administration Account.  
Service Account
Site Collection Administrators. (For all your various web applications)

Making sure you have them all changed with new domain credentials. You should be good as gold.

 

0
 
mandaljAuthor Commented:
Chris - thank you.

So just to be clear, I change the accounts with new credentials first (as trust is already in place), then change the domain of the server hosting WSS?
0
 
Christopher WhiteSenior EngineerCommented:
Yes sounds good to me.

The service account is the only one which will need a little bit of extra configuration. It will need appropriate rights in the SQL instance. Which you may need to add manually.

Is SQL on the same box or on another host ?
0
Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

 
mandaljAuthor Commented:
It's on the same box.
0
 
Christopher WhiteSenior EngineerCommented:
Make sure the new service account has sysadmin or (dbcreator / public) rights on your instance of SQL.

+ Make sure the database SharePoint_Config has the new service account added as an owner (db_owner)

That should be that.
0
 
mandaljAuthor Commented:
Many thanks for your help
0
 
AllybeeCommented:
Did this work for you? Did you have to follow any other steps, like stsadm -o migrateuser -oldlogin <domain\name>  -newlogin <domain\name> ?

Thx
0
 
mandaljAuthor Commented:
Still waiting to implement this. Should be happening in the next 4/5 weeks.
0
 
AllybeeCommented:
mine should happen in the next 4-5 hours ;-)
0
 
mandaljAuthor Commented:
Good luck, let us know how it goes.
0
 
AllybeeCommented:
ok, I'm after this now :/

It was a nightmare, mainly because the server where WSS was hosted was a domain controller also. After I removed DC role from it as a prep for migration WSS seized to even start a service. It turned out that WSS created three groups and they were in the domain, so WSS service was unable to locate them when was no longer a DC. I had to re-create WSS_RESTRICTED_WPG, IIS_WPG, WSS_Admin_WPG and WSS_WPG and populate (vide http://social.technet.microsoft.com/Forums/en/sharepointgeneral/thread/28543da4-aada-4ec1-a1c0-c065929863f1). Then after service started I was unable to see any webparts due to missing temp and logfiles folders permissions, so here helped following article: http://support.microsoft.com/kb/826786
After that you can consider the move successful :)

Hope that helps :)
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 5
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now