Migrate Settings and Data

Applies To: Windows Essential Business Server

After you install Windows EBS, you can migrate settings and data for the following features:

• Shared folders and data

• Fax Service

• DHCP Server

• Domain Name System (DNS)

• Exchange Server

• Trusted certificates

• Windows SharePoint Services

Shared folders and data

You can use the Microsoft File Server Migration Toolkit to help you migrate data. For more information about using the toolkit, see “Microsoft File Server Migration Toolkit” (https://go.microsoft.com/fwlink/?LinkId=156840).

You can also use a command such as Xcopy.exe to move data folders. For more information about moving data folders, see “Moving Data Folders in Windows Small Business Server 2003” (https://go.microsoft.com/fwlink/?LinkId=157080).

Scripts and data folders related to Active Directory Domain Services should also be migrated. For more information about migrating data related to Active Directory Domain Services, see “Migrating Active Directory Domain Services Scripts, Roaming Profiles, Redirected Folders, and Home Directories to Windows Essential Business Server” (https://go.microsoft.com/fwlink/?LinkId=157082).

Fax Service

If you are using the Fax service with Windows SBS 2003, you should migrate your fax settings and data to Windows EBS. To use the Fax service on a server, you must install the Fax Server role. For more information about installing the Fax Server role, see “Installing Fax Components” (https://go.microsoft.com/fwlink/?LinkId=157087).

To collect the information that you need to configure the Fax service on a server, you can use the information and worksheets in “Step-by-Step Guide to Configuring and Using Fax on Windows Small Business Server 2003” (https://go.microsoft.com/fwlink/?LinkId=157088).

DHCP Server

If you use a DHCP Server, you should migrate the DHCP Server service from your existing DHCP server to the Management Server of Windows EBS. For more information about migrating the DHCP Server service, see “Migrating DHCP Server Service to Windows Essential Business Server” (https://go.microsoft.com/fwlink/?LinkId=157095).

Domain Name System (DNS)

To promote optimal performance and reliability of your servers that are running Windows EBS, you need to migrate the Domain Name System (DNS) to Windows EBS when you finish the server installation process.

For more information about migrating DNS settings, see “Migrating the DNS role to Windows Essential Business Server” (https://go.microsoft.com/fwlink/?LinkId=95814).

Exchange Server

To ensure that your users benefit from all of the features that are provided in Microsoft® Exchange Server 2007, you must migrate the existing configuration settings and information to Windows EBS. For more information about how to migrate the configuration settings, see “Migrating Microsoft Exchange Server to Windows Essential Business Server” (https://go.microsoft.com/fwlink/?LinkId=157089).

To finish migrating Exchange Server, you must remove Exchange Server from an administrative group. For more information about removing Exchange Server, see “How to remove the first Exchange Server 2003 computer from the administrative group” (https://go.microsoft.com/fwlink/?LinkId=164666).

Trusted certificates

If you purchased a trusted certificate, and it is available to export, you can move the certificate to the Security Server of Windows EBS. To do this, export the certificate from the server that is running Windows SBS 2003 (Source Server), import it to the Security Server of Windows EBS, and then configure the external Web listener for Remote Web Workplace to use the certificate.

To export the certificate

1. On the Source Server, click Start, click Run, type mmc.exe, and then click OK.

2. Click File, and then click Add/Remove Snap-in.

3. Click Add, select Certificates, and then click Add again.

4. In the Certificates Snap-in dialog box, click Computer Account, and then click Next.

5. Click Local computer: (the computer this console is running on), click Finish, and then click Close.

6. Click OK.

7. Expand Certificates, expand Personal, and then click Certificates.

8. Right-click the certificate that is issued to your Web site (for example: remote.adventure-works.com), click All Tasks, and then click Export.

   Note

   Multiple certificates might exist with the same name. Ensure that you choose a certificate that has a valid expiration date and that was issued by a trusted authority. If you are not sure which one to use, open Internet Information Services (IIS), determine which certificate IIS is using on the server, and then choose that certificate.

9. In the Certificate Export Wizard, click Next.

10. Click Yes, export the private key, and then click Next.

11. Click Include all certificates in the certificate path if possible and click Export all extended properties, and then click Next. Do not click Delete the private key if the export is successful.

12. Type a password to protect the certificate file, and then click Next.

13. Choose a location to save the .pfx file (for example, C:\trustedcert.pfx), and then click Next.

14. Finish the wizard.

After you export the certificate from the Source Server, you must import the certificate to the Security Server.

To import the certificate

1. On the Security Server, click Start, click Run, type mmc.exe, and then click OK.

2. Click File, and then click Add/Remove Snap-in.

3. In the Add or Remove Snap-ins dialog box, select Certificates, and then click Add.

4. On the Certificates snap-in page, click Computer Account, and click Next.

5. On the Select Computer page, click Local computer: (the computer this console is running on), and then click Finish.

6. In the Add or Remove Snap-ins dialog box, click OK.

7. In the console tree, expand Certificates (Local Computer), right-click Personal, click All Tasks, and then click Import.

8. On the Welcome to the Certificate Import Wizard page, click Next.

9. On the File to Import page, browse to the file that you previously created when you exported the certificate, and then click Next.

10. On the Password page, type the password for this file, and then click Next.

    Important

    The Password page provides the option Mark this key as exportable. If you want to prevent exporting of the key from the Security Server, do not select this option.

11. On the Certificate Store page, click Place all certificates in the following store, ensure that Certificate Store is set to Personal (the default settings), and then click Next.

12. On the Completing the Certificate Import Wizard page, click Finish.

After you import the certificate, you must configure the external Web listener for Remote Web Workplace to use the certificate.

To configure the external Web listener for Remote Web Workplace

1. On the Management Server, click Start, click All Programs, click Windows Essential Business Server, and then click Windows Essential Business Server Administration Console.

2. Click the Security tab, click Network firewall, and then in the tasks pane, click Start Forefront Threat Management Gateway console. The Forefront TMG console starts.

3. In the console tree, expand the name of your Security Server, and then click Firewall Policy.

4. In the results pane, double-click Remote Web Workplace Publishing Rule.

5. In Remote Web Workplace Publishing Rule Properties, click the Listener tab.

6. Select External Web Listener from the list, and then click Properties.

7. In External Web Listener Properties, click the Certificates tab.

8. Select Use a single certificate for this Web listener or Assign a certificate for each IP address, and then click Select Certificate.

9. In the Select Certificate dialog box, click a certificate in the list of available certificates, and then click Select. Click OK twice to close the Properties dialog boxes.

10. To save changes and update the configuration, in the results pane, click Apply.

Windows SharePoint Services

You can migrate Windows SharePoint Services databases from Windows SBS 2003 to Windows EBS by completing the following tasks:

1. Install the Windows SharePoint Services Add-in for Windows Essential Business Server on the Management Server

2. Run the Windows SharePoint Services 3.0 Prescan tool on the Source Server

3. Stop the internal Web site (CompanyWeb) on the Source Server

4. Detach the database on the Source Server

5. Copy the database files to the Management Server

6. Attach the content database on the Management Server

7. Create a new Web site to host the new internal Web site

8. Create an alias (CNAME) record

9. Create a new Windows SharePoint Services Web application

10. Set or confirm the Site Collection Administrator

11. Reset IIS

To install the Windows SharePoint Services Add-in for Windows Essential Business Server

1. Download the Windows SharePoint Services Add-in for Windows Essential Business Server from the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=116107).

2. Double-click EBS-Sharepoint-Addin.msi on your hard drive to start the Setup program.

3. Follow the instructions on the screen to complete the installation.

To run the Windows SharePoint Services 3.0 Prescan tool

1. On the Management Server, copy the Windows SharePoint Services 3.0 prescan.exe utility from %Program Files%\Common Files\Microsoft Shared\Web Server Extensions\12\Bin to a folder on the Source Server.

2. On the Source Server, click Start, click Run, type cmd in the text box, and then press ENTER.

3. In the Command Prompt window, switch to the folder where you saved prescan.exe, type prescan.exe /V https://companyweb at the command prompt, and then press ENTER.

4. Note any messages about errors, and review the log files that are created by prescan.exe. If there are errors, make the necessary corrections, and then run prescan.exe again.

To stop the internal Web site (CompanyWeb)

1. On the Source Server, click Start, and then click Server Management.

2. In the navigation pane, expand Advanced Management, expand Internet Information Services, expand <ServerName> (local computer), and then click Web Sites.

3. Right-click the internal Web site, and then click Stop.

To detach the database

1. Click Start, click Run, type cmd, and then click OK.

   Note

   You must be logged on as a member of the Administrators group on the Source Server.

2. Type the following command and then press ENTER:

   Osql –S ServerName\sharepoint -E

   This connects the OSQL database management tool to the SharePoint database instance.

3. Detach the configuration database. To do this, type the following command and then press ENTER:

   EXEC sp_detach_db ‘Configurationdb’

   where Configurationdb is the name of the MSDE configuration database. For example, type EXEC sp_detach_db ‘STS_Config’.

4. Detach the content database. To do this, type the following command and then press ENTER:

   EXEC sp_detach_db ‘Contentdb’

   where Contentdb is the name of the MSDE content database. For example, type EXEC sp_detach_db ‘STS_ServerName_1'

5. If you get an error message such as "Database is in use and cannot be detached," use the following commands on the command line to pause and restart the database engine:

   net pause mssql$sharepoint

   net continue mssql$sharepoint

To copy the database files from the Source Server to the Management Server

1. On the Source Server, locate the two database files STS_Config.mdf and STS_ServerName_1.mdf, where ServerName is the name of the Source Server. By default, these files are located in the following folder:

   C:\Program Files\Microsoft SQL Server\MSSQL$Sharepoint\Data

2. Copy the files to a new folder on the Management Server.

   Note

   You may need to stop the MSSQL$SHAREPOINT service to copy the database files.

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. To connect to the content database that the Management Server uses, do the following:

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

   2. Click Connect.

3. 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 Management 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.

4. 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. In the navigation pane, expand the node for the Management Server, right-click Sites, and then click Add Web Site.

3. 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.

4. Close IIS Manager.

Create an alias (CNAME) resource record

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

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

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

4. 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> (for example, NewServer.contoso.com).

   3. Click OK.

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

6. Close DNS Manager.

To create a new Windows SharePoint Services Web application

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

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

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

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

5. 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.

6. 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.

7. 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.

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

   1. Click Use existing application pool.

   2. Select OldCompanyWeb.

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

10. 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).

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

12. Click OK.

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

14. 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.

15. 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

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

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

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

4. On the Site Collections 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.

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

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

7. 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. At the command prompt, type iisreset.

3. 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.