Steps performed on the Destination Server for Windows SBS 2008 migration

  • Article

Updated: January 22, 2009

Applies To: Windows SBS 2008

To configure the forward lookup zone for the internal Web site on the Destination Server

  1. Open the DNS Management Console in Windows SBS 2008. To open the console, click Start, click Administrative Tools, and then click DNS.

  2. Click Continue in the User Account Controls dialog box.

  3. In the navigation pane, expand the server name, expand Forward Lookup Zones, and then expand the internal domain name (for example, server.local).

  4. Right-click the internal Web site alias (CNAME) resource record, and then click Properties.

  5. Replace the FQDN for the target host entry with the name of the Destination Server (for example, NewServer.contoso.local).

To attach the content database

  1. Click Start, click All Programs, click Microsoft SQL Server 2005, right-click SQL Server Management Studio Express, and then click Run as Administrator.

  2. Click Continue in the User Account Control dialog box.

  3. To connect to the content database that the Destination Server uses, do the following:

    1. In the Server name text box, type \\.\pipe\mssql$microsoft##ssee\sql\query.

    2. Click Connect.

  4. To attach the content database, do the following:

    1. In the navigation pane, right-click Databases, and then click Attach.

    2. In the Attach Databases dialog box, in Databases to attach, click Add.

    3. In the Locate Database Files dialog box, navigate to the STS_<SourceServerName>_1.mdf file that you copied from the Source Server to the Destination Server, and then click OK.

    4. In the Attach Databases dialog box, in <DatabaseName> database details, confirm that the STS_<SourceServerName>_1.mdf file and the STS_<SourceServerName>_1_Log.ldf file are listed.

    5. Click OK.

    6. If you see a warning dialog box from MSSMSE, which asks about locating full text catalogs, click No.

    7. Verify that the STS_<SourceServerName>_1 database is listed in the Databases folder in the navigation pane.

  5. Close MSSMSE.

To create a new Web site to host the new internal Web site

  1. Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. Click Continue in the User Account Control dialog box.

  3. In the navigation pane, expand the <DestinationServerName>, right-click Sites, and then click Add Web Site.

  4. In the Add Web Site dialog box, do the following:

    1. In Site name, type OldCompanyWeb.

    2. In Application pool, accept the default OldCompanyWeb.

    3. In Physical path, browse to C:\inetpub, click Make New Folder, and then type OldCompanyWeb as the new folder name.

    4. In the Binding section, in Host name, type OldCompanyWeb.

    5. Click OK.

Note

OldCompanyWeb is added to the Sites folder.

  1. Close IIS Manager.

Create an alias (CNAME) resource record for OldCompanyWeb

  1. Click Start, click Administrative Tools, and then click DNS.

  2. Click Continue in the User Account Control dialog box.

  3. In the navigation pane, expand the Forward Lookup Zones.

  4. Right-click <DomainName>.local, and then click New Alias (CNAME).

  5. In the New resource Record dialog box, do the following:

    1. In Alias name (uses parent domain if left bank), type OldCompanyWeb.

    2. In Fully qualified domain name (FQDN) for target host, type <ServerName>.<DomainName>.local (for example, NewServer.contoso.local).

    3. Click OK.

  6. Note that the OldCompanyWeb alias (CNAME) resource record is now listed in the Forward Lookup Zone.

  7. Close DNS Manager.

Create a new Windows SharePoint Services Web application named OldCompanyWeb

  1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

  2. Click Continue in the User Account Control dialog box.

  3. On the Home page, in the navigation bar, click the Application Management tab.

  4. On the Application Management page, in the Windows SharePoint Services Web Application Management section, click Create or extend Web application.

  5. On the Create or Extend Web Application page, click Create a new Web application.

  6. On the Create New Web Application page, in the IIS Web Site section, do the following:

    1. Click Use an existing IIS Web site.

    2. Click OldCompanyWeb in the drop-down list box.

    3. Accept the default entries in the remaining text boxes in the section.

  7. On the Create New Web Application page, in the Security Configuration section, accept the default settings:

    1. In Authentication provider, click NTLM.

    2. In Allow Anonymous, click No.

    3. In Use Secure Sockets Layer (SSL), click No.

  8. On the Create New Web Application page, in the Load Balanced URL section, do the following:

    1. Verify that the URL text box contains https://OldCompanyWeb:80/.

    2. Accept Default in the Zone text box.

  9. On the Create New Web Application page, in the Application Pool section, do the following:

    1. Click Use existing application pool.

    2. Select OldCompanyWeb or the name of the application pool that you created in Step 4 of the “To create a new Web site to host the new version of CompanyWeb” procedure.

  10. On the Create New Web Application page, in the Reset Internet Information Services section, accept the default settings.

  11. On the Create New Web Application page, in the Database Name and Authentication section, do the following:

    1. In Database Server, accept the default <DestinationServerName>\Microsoft##SSEE.

    2. In Database Name, type STS_<SourceServerName>_1.

    3. In Database authentication, click Windows authentication (recommended).

  12. On the Create New Web Application page, in the Search Server section, in Windows SharePoint Services search server, click the Destination Server name in the drop-down list box.

  13. Click OK.

  14. If you receive a warning message, click OK.

  15. The Operation in Progress page is displayed. This operation takes approximately 30 minutes. The new Windows SharePoint Services Web application is created, and the Windows SharePoint Services 2.0 CompanyWeb database is upgraded to Windows SharePoint Services 3.0.

  16. The Application Created page is displayed. It notes that you need to reset IIS to finish creating the new Web site. You will do this in a later procedure. Close Central Administration for Windows SharePoint Services 3.0.

To set or confirm the Site Collection Administrator for the OldCompanyWeb Web site

  1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

  2. Click Continue in the User Account Control dialog box.

  3. On the Home page, in the navigation bar, click the Application Management tab.

  4. On the Application Management page, in the SharePoint Site Management section, click Site Collection Administrators.

  5. On the Site Collection Administrators page, in the Site Collection section, if https://OldCompanyWeb is not displayed in the Site Collection box, do the following:

    1. Click the Site Collection drop-down arrow, and then click Change Site Collection.

    2. On the Select Site Collection page, in the tool bar, click the Web Application drop-down arrow, and then click Change Web Application.

    3. On the Select Web Application page, in the Name column, click OldCompanyWeb, and then click OK.

  6. On the Site Collection Administrators page, confirm that the Primary site collection administrator text box contains a valid user account name in your Windows SBS 2008 domain. If it does not, type a valid user account name.

Important

The built-in Administrator account is not a valid user account name in your Windows SBS 2008 domain.

  1. You can also enter a user account name in the Secondary site collection administrator text box.

  2. Click OK, and then close Central Administration for Windows SharePoint Services 3.0.

To reset IIS

  1. Click Start, right-click Command Prompt, and then click Run as administrator.

  2. Click Continue in the User Account Control dialog box.

  3. At the command prompt, type iisreset.

  4. When you see the message Internet services successfully restarted, close the Command Prompt window.

You now have a working Windows SharePoint Services 3.0 Web site that is named OldCompanyWeb and that contains the structure and documents of your old Windows SBS 2003 CompanyWeb Web site. Before you import the content of OldCompanyWeb into the Windows SBS 2008 internal Web site, review the content of the CompanyWeb Web site and reorganize or archive items, if appropriate.

To import the content of OldCompanyWeb into the Windows SBS 2008 internal Web site

  1. Click Start, right-click Command Prompt, and then click Run as administrator.

  2. In the User Account Control dialog box, click Continue. A Command Prompt window opens.

  3. At the command prompt, type cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN, and then press ENTER.

  4. To back up the existing CompanyWeb Web site, at the command prompt, type stsadm -o export -url https://companyweb -filename cweb.bak –includeusersecurity, and then press ENTER.

  5. To export content from OldCompanyWeb, when the Backup finishes, at the command prompt, type stsadm -o export -url https://Oldcompanyweb -filename oldcweb.bak –includeusersecurity, and then press ENTER.

  6. To import content into the new CompanyWeb, when the export operation finishes, at the command prompt, type stsadm -o import -url https://companyweb -filename oldcweb.bak –includeusersecurity, and then press ENTER.

All the content from https://OldCompanyWeb should now be imported into the Windows SBS 2008 internal Web site. You can delete the Web site, https://OldCompanyWeb, or mark the database in Microsoft SQL Server 2005 as Read-only to retain the site as an archive database.

Note

The Explorer view in Windows SharePoint Services depends on WebDAV. Typically, WebDAV is installed on client operating systems, but not on server operating systems. To use Internet Explorer to view the content on the Windows SBS 2008 internal Web site, access the site from a client computer on the network, or install the Desktop experience from Server Manager on your Destination Server.