Migrating of SharePoint 2007 Server From One Domain to Another Domain


This article provides the step-by-step migration procedure of a SharePoint 2007 server from one domain to another domain (including the SharePoint 2007 installation as well). This article can also set an example of moving your contents DB from one server to another server. (Check out from Step 62).


  1. Ensure you have Microsoft Windows Server 2003 Enterprise or Standard.
  2. Ensure you have Microsoft Windows Server 2003 Service pack 1 or 2.
  3. Ensure you have IIS 6.0 with ASP.NET Enabled.
  4. Ensure that you have .NET Framework 3.0 installed.
  5. Ensure you have access to the destination SQL DB where you’re creating the Farm.
    a. DB Creator
    b. SysAdmin
    c. Security Admin
    d. Server Admin
  6. Ensure you have MSSharePoint2007.iso file.
  7. Ensure you have officeserver2007sp1-kb936984-x86-fullfile-en-us.exe file for SP1 upgrade. (If SQL Server is 2008 R2.)
  8. Ensure you have the following three accounts:
    a. Farm account -> SharePoint installation
    b. Search account -> Search Configuration
    c. Content account -> Content DB creation
  9. Ensure you have backed up the content DB to be stored in the destination server
    a. In our case it was Content_DB_80 and Content_DB_Mysite_81
  10. Ensure you have copied all the available WSPs that are deployed in the source Farm to the local file system. Link to Extract WSP step-by-step procedure.


Use the following procedure:

  1. Go to the folder where MSSharePoint2007.iso file is stored, for examle: C:\ MSSharePoint2007.iso file
  2. Unzip the MSSharePoint2007.iso file.
  3. Enter the product key from the key.txt file.
  4. Click Continue.
  5. Check I Agree to the license agreement and click Continue.

  6. Click Advanced to choose the advanced installation options as in the following:

  7. Select “Complete” to install SharePoint Server 2007 as complete installation and click Install Now.

  8. Wait while SharePoint setup installs its binaries.

  9. Check the check box and click Close.

  10. Click Next on the SharePoint Products and Technology Configuration Wizard.

  11. Click Yes on Services and IIS Reset dialog.

  12. Select “No, I want to create a new server Farm” and click Next.

  13. Enter the Database Server Name.
  14. Enter the user with Administrative permissions on the SQL Server . The user name should be in the form of Domain\User Name. (In other words ur content DB account) and click Next.

  15. Check the "Specify port number" checkbox and change the port number to 8080.
  16. The default Security settings will be NTLM.
  17. Click Next.

  18. Click Next to confirm the changes you have made.
  19. The Configuration Wizard will run the procedure again.

  20. Click Finish when you see the screen.
  21. The SharePoint Central Administration Site will open automatically.

  22. A pop-up window will appear.
  23. Click “Add” to add this site to the trusted sites.
  24. Click Add and Close.

  25. Now you will be able to see the Central Admin site.

  26. Enable Email Server on the environment.

  27. Click on Operations -> Outgoing e-mail settings.
  28. Enter Server name and Email Address and click “OK”.

  29. Now click on Operations -> Services on Server.

  30. Click on “Office SharePoint Server Search”.

  31. Under Query and Indexing section, select both of the Indexing and Query checkboxes.
  32. Enter Contact Email address.
  33. Enter the Search account.
  34. Select path for the index file that will be created by the SharePoint Server 2007 Crawler.

  35. Click Start when you are done.

  36. Click on “Windows SharePoint Services Search Service” to configure Shared Services.

  37. Enter search account details under Service Account section.
  38. Enter content account details under Content Access Account section.
  39. Enter Database server and Database name for Windows SharePoint Services Search under the Search Database section.

  40. Click Start When you are done.

  41. Now the services will begin.
  42. Creating a New Shared Service Provider for MOSS 2007 site.
  43. From left navigation click Shared Services Administration click on New SSP.

  44. From the new SSP Page Enter SSP Title and then click on Create a New web application for Administration Site host.

  45. Creating a New web application for Shared Services Administration Site.
  46. Enter Port Number 88.
  47. Select NTLM for security.

  48. In The application pool settings enter the Farm account user name and word for the administrator.
  49. Leave the remaning section unchanged.
  50. Now create a new web application for mysites with port 81.

  51. Now enter the Farm account details under SSP Service Credential section.

  52. Change the Database names for both SSP DB and SSP Search DB to some relevant names.
  53. Keep rest of the section as it is and click on “OK”.

  54. Now click on Start -> Run -> CMD iisreset and press Enter.

  55. Now create a web application.
  56. Click Application Management -> Create or Extend a New Web Application.

  57. Create a New Web application. Enter 80 as Port number.

  58. In the Application pool section enter the Farm account details.

  59. In the Database Name and authentication section change the Database name to some relevant name and click the “Ok” button.

  60. When you receive confirmation that the web application is created,
  61. Click Start -> Run -> CMDiisreset.

  62. Again click Start Run inetmgr. Check whether the website 80 is created.
  63. Note: If you are not able to create a new application with port 80 then check whether the default port is set to port 80 in IIS. If the Default port is set to 80 then stop the Default website and create a new web application with port 80 and now you should be able to see port 80 in IIS.

  64. Now run the SP1 upgrade.
  65. Double-click on SharePoint service pack 1 exe file. Check the check box and click on Continue.

  66. Wait until the Configuration wizard is successful.
  67. Now next step is to attach the content DB for which we have taken back from the source server and placed in the destination SQL Server.
  68. Now open the command prompt. Click on Start Run CMD.

  69. Navigate to 12 hive  bin folder using the cd command as in the following:

    cd “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”.

  70. Now attach the content db to the 80 web application.

  71. Syntax: stsadm -o addcontentdb -url http://webapplication_URL/ -databasename MOSS_ Content_80

    databasename backed up content db name.
    urlwebapplication url for which you the content db needs to be attached. (In our scenario we are attaching port 80 webapplication.)

  72. Now you need to deploy the WSPs that were available in the source to destination server. Navigate to the location where you stored the WSPs and copy the location details. Use the stsadm command to deply your WSPs to the Farm.
  73. If you are not aware of how to extract the WSPs kindly go through the following link Extract WSP step-by-step procedure

  74. Syntax: stsadm -o addsolution -filename F:\WSPS\client_site.wsp

    Filenamefull path of the file where you have placed your WSPs.
  75. Now navigate to Central Admin Operations Solution management.
  76. You should be able to see the WSP that you have deployed using stsadm command.
  77. Now deploy the solutions to a specific webapplication or all the webapplications based on configurations available in your source server.
  78. Still it's not over, you need to match the 12 hive folders, central admin configuration using UI, and so on.
  79. The following is the check list.

    CheckPoints for installation Comments
    Installation of SharePoint  
    Backup of the content DB and WSPs  
    SharePoint Farm configurations  
    Install the SharePoint or Windows patches  
    Attaching the content DB to newly created web application and for mysites stsadm -o addcontentdb -url http://weburl/ -databasename MOSS_CONTENT_80_P
    Detach the old content DBs using UI configuration.
    Deploying the WSPs stsadm -o addsolution -filename F:\WSPS\client_site.wsp
    Comparing the DLLs in the GAC folder w.r.t source 1) Open the Gac folder using the following command by click on Start-->Run-->"%windir%\assembly\GAC_MSIL" and click on Enter.

    2) Open the GAC folder, compare it with source and dump it in destination gac folder.
    Compare the web.config files 1)Navigate to C:\Inetpub\wwwroot\wss\VirtualDirectories and
    compare the source and detination web.config files using online tool http://www.quickdiff.com/ for all the web.config files.
    Compare the 12 hive folders  
    Compare the Search configurations and run the full crawl 1) Check for user profiles, files type, Authoritative pages, Scopes and so on.
    Central Admin Comparision (Operations) 1) When comapring the Timer job defeinition if the following timer jobs are not availble in the detination server:

    1) Scheduled Approval
    2) Scheduled Page Review
    3) Scheduled Unpublish
    4) Variations Propagate Page Job Definition
    5) Variations Propagate Site Job Definition

    Then you need not need to worry, navigate to the port 80 webapplication URL deactivate and activate the Office Server Publishing feature. If you get an access denied error then try using the following stsadm command.

    stsadm -o activatefeature -name PublishingResources -url http://webapplication.
    Central Admin Comparision (Application Management)  
    Compare the Master pages in _catalog page.  
    Metadata property mapping comparision. Once you run the full crawl, then only you can go ahead and check the metaData property mappings.
    Check for Task Scheduler 1) Check if there are any tasks that have been scheduled. If so then configure them.
    User Mapping using stsadm commands, if 1:1 mapping exists 1) Use the following stsadm command to migrate the users from one domain to another domain.
    stsadm -o migrateuser -oldlogin domain\username -newlogin domain\username -ignoresidhistory 
  80. That’s it. Now your destination server will be similar to your source server except the domain change.


  1. Now navigate to your port 80 web application URL.
  2. You should be able to open up the sites and the site experience will be similar to your source site.


Thus in this article you saw how to migrate a SharePoint 2007 server from one domain to another domain along with SharePoint 2007 installation.