You are on page 1of 62

Migrate to Windows Small Business Server 2008 from Windows Small Business Server 2008

Microsoft Corporation Published: November 2009 Version: 4

Abstract
This guide helps you to install Windows SBS 2008 in Migration Mode on a new server, and then to migrate the settings and data from the old server that is running Windows SBS 2008 to the new server that is running Windows SBS 2008. This guide also helps you demote and remove your old server from the network after you finish the migration process. For the most up-to-date product documentation, see the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=92482.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Your right to copy this documentation is limited by copyright law and the terms of the software license agreement. As the software licensee, you may make a reasonable number of copies or printouts for your own use. Making unauthorized copies, adaptations, compilations, or derivative works for commercial distribution is prohibited and constitutes a punishable violation of the law. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Outlook, SharePoint, SQL Server, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. UPnP is a certification mark of the UPnP Implementers Corporation. All other trademarks are property of their respective owners.

Contents
Migrate to Windows Small Business Server 2008 from Windows Small Business Server 2008.....5 Prepare your Source Server for migration...................................................................................6 Back up the Source Server......................................................................................................6 Verify the network configuration...............................................................................................7 Evaluate the health of the Source Server.................................................................................7 Optimize Exchange Server 2003 mailbox sizes for Windows SBS 2008 Migration..................8 Run the Migration Preparation Tool for Windows SBS 2008 migration.....................................9 Plan to migrate line-of-business applications for Windows SBS 2008 migration....................11 Create a migration answer file for Windows SBS 2008 migration..............................................12 Install Windows Small Business Server 2008 in Migration Mode..............................................16 Migrate Settings and Data to the Destination Server.................................................................20 Change where to store data on the Destination Server for Windows SBS 2008 migration....24 Configure the network for Windows SBS 2008 migration.......................................................24 Configure the Internet address...............................................................................................24 Move network settings for Windows SBS 2008 migration......................................................25 Move certificates for Windows SBS 2008 migration............................................................26 Migrate Exchange mailboxes and settings.............................................................................28 Migrate Internet connectors................................................................................................29 Migrate POP3 connectors...................................................................................................31 Migrate CompanyWeb connector........................................................................................31 Move Exchange Server public folders.................................................................................32 Move Exchange Offline Address Book for Windows SBS 2008 migration...........................35 Move mailboxes..................................................................................................................35 Enable circular logging on storage groups for Windows SBS 2008 migration.....................36 Migrate users' shared data.....................................................................................................37 Configure a new shared volume on the Destination Server................................................37 Copy users' shared folders to the Destination Server.........................................................38 Copy additional shared folders to the Destination Server...................................................39 Migrate the SharePoint Web site............................................................................................40 Migrate fax data......................................................................................................................41 Migrate Windows Server Update Services Data and Settings................................................43 Run the Server Cleanup Wizard.........................................................................................43 Set up the Update Services replica server..........................................................................44 Replicate the Update Services database............................................................................45 Verify that the replication is successful...............................................................................46 Make the Destination Server the stand-alone Update Services server...............................46 Verify Update Services Computer Groups..........................................................................46 Migrate SQL Server data........................................................................................................47

...................................................................................62 ..........54 Finish migration.........................61 Share line-of-business and other application data folders for Windows SBS 2008 migration 61 Run the Windows SBS 2008 Best Practices Analyzer...........................................................50 Specify SQL Server collation settings for Windows SBS 2008 migration..................................Install a new instance of SQL Server 2008 for Windows SBS 2008 for Windows SBS 2008 migration..................................................60 Configure Exchange POP3 connectors for Windows SBS 2008 migration.........................................................................................................................59 Delete DNS entries of the Source Server for Windows SBS 2008 migration.......................48 Move a SQL Server 2000 instance or SQL Server 2005 instance to SQL Server 2008 for Windows SBS 2008 migration...........................................................50 MoveTerminal Service licensing server for Windows SBS 2008 migration..................................... ....................................................................59 Move natively joined Active Directory computer objects for Windows SBS 2008 migration..................................................................................51 Migrate Remote Web Workplace configuration file.........................56 Optional post migration tasks.........................................55 Demote and remove the Source Server from the network............................................60 Change Exchange Server 2007 mailbox sizes for Windows SBS 2008 migration............................................................................... ......54 Migrate Gadgets..........

which updates the AD DS schema. the Windows® Small Business Server 2008 server software (Windows SBS) requires a 64-bit server. Important To avoid problems while migrating your existing server to Windows SBS 2008. and verifying the network configuration. You must also run the Migration Preparation Tool on the Source Server. see the Microsoft Web site (http://go. see the Microsoft Web site (http://go.Migrate to Windows Small Business Server 2008 from Windows Small Business Server 2008 Note This is Version 4 of this article. and configures Exchange Server to support migration. Important Unlike previous versions. This guide also tells you how to remove your existing server from the Windows SBS 2008 network after you finish the migration. Source Server: The existing server that you are migrating your settings and data from. This section guides you through backing up the Source Server. This guide tells you how to migrate an existing Windows SBS 2008 domain to Windows SBS 2008 and then to migrate the settings and data. evaluating the Source Server system health. it is recommended that you read this document before you begin the migration. Windows SBS 2008 does not support a 32-bit processor architecture.com/fwlink/?LinkId=120093).microsoft. For the latest online version. 5 .com/fwlink/?LinkId=120545). installs an update that extends the time limit for the migration. To download the most recent printable version. Prepare your Source Server for migration You must ensure that your Source Server and network are ready for migration. installing the most recent service packs and fixes. Process steps This Migration Guide includes the following steps: 1.microsoft. Terms and definitions Destination server: The new server where you are installing Windows SBS 2008 and migrating your settings and data to.

Create a migration answer file for Windows SBS 2008 migration An answer file is used by Windows SBS 2008 Setup to automate the installation and to run Setup in Migration Mode. see “Backing Up and Restoring Server Data” at the Microsoft Web site (http://go. Install Windows Small Business Server 2008 in Migration Mode This section explains how to use the migration answer file to install Windows SBS 2008 on the Destination Server in Migration Mode. select 6 . Perform a virus scan of all the drives and files on the Source Server. Optional post migration tasks After you finish migrating all settings and data to Windows SBS 2008. This section explains how to remove the Source Server from the network. To back up the Source Server 1. 2. Perform a full backup of the Source Server. This section explains how to use the Migration Wizard and provides information about the settings and data that you can migrate. 3. 5. the Source Server must be demoted and physically removed from the network. This helps protect your data from accidental loss if an unrecoverable error occurs during migration. Verify that the backup ran successfully. 3. enable folder redirection. 4. you should back up your Source Server. you may want to map permitted computers to user accounts. Prepare your Source Server for migration Complete the following steps to ensure that the settings and data on your Source Server migrate successfully to the Destination Server. To test the integrity of the backup. configure POP3 connectors. or update mailbox quotas on your new server. • • • • • • Back up the Source Server Verify the network configuration Evaluate the health of the Source Server Optimize Exchange Server 2003 mailbox sizes for Windows SBS 2008 Migration Run the Migration Preparation Tool for Windows SBS 2008 migration Plan to migrate line-of-business applications for Windows SBS 2008 migration Back up the Source Server Before you begin the migration process. For more information about backing up Windows SBS 2008. Demote and remove the Source Server from the network After Windows SBS 2008 is installed and all of the settings and data are successfully migrated. Migrate Settings and Data to the Destination Server The Migration Wizard helps you migrate settings and data from the Source Server to Windows SBS 2008. 6.com/fwlink/?LinkId=104285).microsoft. This section introduces you to the migration answer file and guides you through using the Answer File Tool to create the migration answer file.2.

Because the router is the gateway to the Internet. the Windows SBS Console collects and displays information about your router on the Networking tab. • The installation wizard configures port-forwarding exceptions on the router.random files from your backup. 7 . in Internet Connection. and then confirm that the backed-up files are the same as the original files. Evaluate the health of the Source Server Download and install critical and security updates Installing critical and security updates on the Source Server can help protect your network while you are migrating to an updated version of Windows SBS 2008 and can help assure a successful migration. Verify the network configuration Reconfigure your existing network If you have a broadband connection to the Internet but you do not have a router on your local area network (LAN). Figure 1. Local area network with broadband connection If your router supports the UPnP™ framework and is set up properly. restore them to an alternate location. you must add a router to your network. either the router must provide a firewall service or you must add a firewall device to help protect your LAN from unauthorized access. the following are true: • The installation wizard automatically configures the Internet connection in Windows SBS 2008. • After Windows SBS 2008 is installed.

Optimize Exchange Server 2003 mailbox sizes for Windows SBS 2008 Migration It can take a long time to migrate large Exchange Server mailboxes. and then click Synchronize now to synchronize with the Microsoft Updates Web site. In the navigation bar. On the navigation bar.microsoft. In the Microsoft Office Outlook® messaging client. and then click Empty "Deleted Items" Folder. Open the Windows SBS Console. 3. To generate a system health report 1. Click Yes on the warning dialog box. It will take less time if you reduce the size of the mailboxes before the migration. click File in the toolbar. 2. and then click Updates. After the synchronization finishes. 5. To empty the Deleted Items folder 1. 2. 4. click the Security tab. In Outlook. Open the Windows SBS Console. In the Archive dialog box. To archive older mail 1. To help reduce the size of the mailboxes. and then click Archive.com/fwlink/?LinkID=101795). ask each of the users to do the following: • • Empty the Deleted Items folder Archive older mail For additional information about optimizing Exchange Server. click the Reports tab. Verify that all updates are installed without errors. In the Tasks pane. click Generate report.To synchronize the server with the latest updates 1. approve any updates for the Source Server if Update Services is not configured to automatically approve updates for the server. 3. click Tools in the toolbar. Check the System Health reports for critical errors You can generate System Health Reports from the Windows SBS Console. see the Exchange Best Practices Analyzer at the Microsoft Web site (http://go. click the down arrow in the Archive items older than text 8 . 2. Verify that there are no updates with errors. 2.

4. which extends the AD DS schema and updates permissions as necessary to prepare a forest and domain for a domain controller that runs Windows SBS 2008. the older mail is moved to the archive. 5. you must update the AD DS schema on the Source Server if it is running Windows SBS 2003 or Windows Server 2003. only one server running Windows SBS 2008 or Windows SBS 2003 is allowed to be a domain controller on your network. Normally. The AD DS schema in Windows SBS 2008 is not the same as the AD DS schema in Windows SBS 2003 or in Windows Server 2003. In the Windows Vista® operating system. • Installs an update that extends the time limit for finishing the migration. Note You must tell the users what date to select in the calendar that appears. In Windows XP. Click Archive all folders according to the AutoArchive settings at the top of the dialog box.exe. the older mail is moved to the archive. the only way to return the Source Server to the state before you ran the Migration Preparation Tool is to restore the system backup. To successfully complete the migration process. but there is a limited exception for a migration. All changes that the Migration Preparation Tool makes to the schema are irreversible. Click OK.box. If you want to make sure that all the older mail is included. The update extends the time limit for the exception to 21 days. select the Include items with "do not AutoArchive" checked check box. • Runs Adprep. 9 . 3. If you experience issues during the migration.pst file in C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Outlook folder. Run the Migration Preparation Tool for Windows SBS 2008 migration The Migration Preparation Tool prepares the Source Server for the migration process by performing the following tasks: Note These tasks apply only if you are migrating to Windows SBS 2008 from Windows SBS 2003.pst file in C:\Users\<user name>\AppData\Local\Microsoft\Outlook folder. Important You should back up your Source Server before you run the Migration Preparation Tool.

Microsoft . and then click Properties. and Domain Admins are listed in the Member of text box. see “How to obtain the latest version of the Windows Update Agent to help manage updates on a computer” in the Microsoft Knowledge Base (http://go. Right-click the administrator account that you are using for the migration. For more information about converting from mixed mode to native mode. 10 .NET Framework 2. and then verify that Enterprise Admins. To download and install .NET Framework 2. For more information. Notes • To run the migration tools. click Add. the Schema Admins group. In the navigation pane. and the Domain Admins group. Schema Admins. Click the Member Of tab. and then add each group that is not listed. • To ensure that the server update process works properly. • Prepares the server to migrate from Exchange Server 2003. For the migration to succeed. go to http://update.0 or later must be installed on the Source Server. click Users. Step 1: Verify that you have the appropriate permissions to run the tool on Windows SBS 2003 1.microsoft. see “How to convert from mixed mode to native mode in Exchange” at the Microsoft Web Site (http://go.microsoft. you must be a member of the Enterprise Admins group.com/fwlink/?LinkId=150342). Be sure to install Service Pack 2 for Windows SBS 2003 on the source server before you run the Migration Preparation Tool. not mixed mode. click Start.microsoft.Important This task might not succeed if the source server is running Windows SBS 2003 with Service Pack 1. 2. see the Microsoft Web site (http://go.microsoft. 5. and then click Server Management.com to automatically install the latest version of the Windows Update Agent. If the groups are not listed. On the Source Server.com/fwlink/?LinkId=81886). Exchange Server must be in native mode. Important To run the Migration Preparation Tool.com/fwlink/? LinkId=104943). Step 2: Prepare the Source Server for migration 1. Note You must log off and log back on the server for the changes to take effect. 4. Insert Windows SBS 2008 DVD1 in the DVD drive on the Source Server. 3.0.

Microsoft recommends that you always choose to install the most recent update. When the installation is complete. supply-chain management. When the Windows SBS 2008 installation wizard starts.2. see Create a migration answer file for Windows SBS 2008 migration. click Tools. The wizard installs the Migration Preparation Tool on the Source Server. In the Source Server Migration Tool. the Migration Preparation Tool runs automatically and installs the latest updates. follow the instructions in “Method 3: Rename the Catroot2 Folder” in the article “You cannot install some updates or programs” in the Microsoft Knowledge Base (http://go. either copy sourcetool. click Create an Answer File and follow the instructions that appear. 5. Notes • If the Migration Preparation Tool is already installed on the server. Click Finish. Note If you try to repair the Migration Preparation Tool installation by double-clicking the file sourcetool. 4. Plan to migrate line-of-business applications for Windows SBS 2008 migration A line-of-business (LOB) application is a critical computer application that is vital to running a business. run the tool from the Start menu. 11 . When the Migration Preparation Tool finishes. “Please insert the disk. or uninstall and then reinstall the Migration Preparation Tool.com/FWLink/?LinkID=118672). you must restart the Source Server before you begin migrating to Windows SBS 2008. These include accounting. and then click Next. click I have a backup and am ready to proceed. 3. Note If you receive an error message relating to hotfix installation. Note For more information about creating a migration answer file. 6.msi to your local hard disk drive and then run the file from there. • To ensure that you are prepared for the best possible migration experience.” To work around this issue.msi on the DVD. and then doubleclick SourceTool. If you have not created a migration answer file. a dialog box may appear that says.microsoft. and resource-planning applications.

xml. 12 . it is important that you consult with the LOBapplication provider to determine the appropriate method for migrating the application.microsoft. To fully automate a clean installation in migration mode. Windows SBS 2008 can be installed successfully only on the C drive. Note You must be at the customer site to install Windows SBS 2008 in Migration Mode and to finish the Getting Started tasks. You can also use an answer file for an unattended installation.xml answer file for the operating system phase of the installation. You also must locate the media that is used to reinstall the LOB applications on the Destination Server. Important To fully automate an installation in migration mode on a server that has a preinstalled operating system.xml answer file. Application or general data folder name Path to data Notes Create a migration answer file for Windows SBS 2008 migration An answer file serves the following purposes when you are installing Windows SBS 2008: • Starts the migration process during the installation of Windows SBS 2008. you must specify the C drive. • Helps value-add professionals build servers before taking them to the customer site for final configuration. For information about creating an answer file by using the Automated Installation Kit (AIK). • Provides information that is automatically entered into the Windows SBS 2008 installation pages. you must also use the autounattend. you must also use the OOBE. You can fill in the following table as you collect LOB-application information. Note You must use an answer file if you are migrating to Windows SBS 2008.com/fwlink/?linkid=115680). see “Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008” at the Microsoft Web site (http://go. When you use autounattend.When you plan to migrate your LOB applications.

3. the migration stops. Contoso-NewServer). Collect the information for the migration answer file The following tables list the information that you need for the answer file. You can edit the company information later. Windows SBS 2008 uses the internal domain name and the server name (syntax: <InternalDomainName>-<Windows SBS 2008 ServerName>) to generate a self-signed certificate (for example. Copy the migration answer file to the root partition of a USB flash drive or other removable media. Step 1. you must manually set the clock in the server BIOS to the correct time. complete the following steps: 1. The system clock cannot be set automatically by using the answer file. Clock and time zone settings Information to provide Description Clock and time zone settings If you choose to manually set the clock and time zone. and then it prompts you to set the clock and time zone. If you leave this field blank. 2. in the Windows SBS Console. Certificate authority name (optional) The name of the certificate authority that you want to use. If you choose to automatically set the time zone. Collect the information for the migration answer file. click the Help list menu.To create a migration answer file. This information is used for settings on your server and is not sent to Microsoft. Run the Answer File Tool. To edit it. 13 . and then click Edit Company Information. Company information Information to provide Description Company information (optional) Name and address of the business.

However. Source Server name Source domain name Source Server IP address Default gateway DHCP is running on the Source Server The name of the server from which you are migrating settings and data. you must either change the password for migration or create a new domain administrator account that has a password. Important This account must be a member of the Domain Admins. contoso. The IP address that is assigned to the router on your network. Password The password that corresponds to the domain administrator account name. Note The domain administrator account password cannot be blank. If it is. Select this box if the DHCP service is running on the Source Server. it is moved automatically for 14 . The IP address that is assigned to the Source Server.local. It is recommended that you run the DHCP service on the Destination Server. Note It is recommended that you create a new administrator account on the Source Server for migration instead of using the built-in Administrator account. If you are running the DHCP service on the Source Server. The full DNS name of your organization's internal domain—for example. Enterprise Admins.Source Server (existing) information Information to provide Description Domain administrator account name The user account name of a domain administrator in the existing domain. and Schema Admins groups. the default security group for the account cannot be one of these three groups.

To create the migration answer file 1. Type the information that you collected in Step 1.exe. you must have . 3.com/fwlink/? LinkId=81886). so if you change the password for your administrator account on Windows SBS 2008. If the DHCP service is running on another server or device. These passwords do not synchronize. Destination Server IP address Step 2. Run the Answer File Tool Next. The IP address that you want to assign to the Destination Server. insert Windows SBS 2008 DVD1. Destination Server information Information to provide Description Destination Server name The name of the server to which you are migrating. You will install Windows SBS 2008 on this server. Note The domain administrator user name and password that you supply in the answer file are also set as the Directory Services Restore Mode (DSRM) password. The Answer File Tool opens. Note To run the Answer File Tool. 2. On a client computer or a server. you must manually disable it on that server or device. run the Answer File Tool to create the migration answer file.NET Framework 2. see the Microsoft Web site (http://go. 4. To download and install .Information to provide Description you.NET Framework 2.xml. Save the answer file as sbsanswerfile. navigate to the Tools folders.microsoft. you must use the same user name and password that you specified during migration. and then double-click SBSAfg. 15 . The Source Server name and the Destination Server name must be different. Click Migration from existing server (Join existing domain). you must continue to use the old password to log on to the server in DSRM. If for any reason you need to log on to the server in DSRM.0 or later installed on the computer that you are using to create the answer file.0.

This server will be automatically shut down if the issue is not corrected in %1 days from the time this condition was first detected. Note An error message is added to the event log each day during the 28 day grace period until you remove the Source Server from your network. The Management Server must hold the primary domain controller and domain naming master Active Directory roles. Install Windows Small Business Server 2008 in Migration Mode You can have only one server on your network that is running Windows SBS 2008. If the Windows SBS 2008 installation wizard detects a migration answer file. "The FSMO Role Check detected a condition in your environment that is out of compliance with the licensing policy.Step 3. After the migration is finished. Windows SBS 2008 does not support a 32-bit processor architecture. When you install Windows SBS 2008 in Migration Mode. and that server must be a domain controller for the network. Please move the Active Directory roles to the Management Server now. the following tasks are accomplished: • Windows SBS 2008 is installed and configured on the Destination Server. Windows SBS 2008 requires a 64-bit server. Both the Source Server and the Destination Server can be members of the Active Directory® Domain Services (AD DS) domain until the migration process is finished. Important The answer file contains logon and password information that can be used to log on to your server. • The Destination Server is joined to the existing domain. The error message says. Then. the migration starts automatically. delete the answer file. insert it into a USB port on the Destination Server before you start migrating to Windows SBS 2008. the Source Server will shut down. you must remove the Source Server from the network within 21 days." After the 28 day grace period. Copy the migration answer file to the root partition of a USB flash drive or other removable media. when you finish migrating to Windows SBS 2008. To help protect your server. 16 . Copy the migration answer file to removable media Important You cannot start the migration without completing this step. Important Unlike previous versions.

4. Note Before you start the migration. Note The migration answer file is automatically detected on the root of any drive. you should enable the DHCP Server service on the Source Server. • The DHCP Server service is installed and configured on the Destination Server. Operations master roles in AD DS are specialized domain-controller tasks. If you see a message asking if you want to boot from a CD or DVD. The installation wizard starts loading files into memory. not on the router. partial representation of every object in every domain in the AD DS forest. • The Destination Server becomes the site licensing server. If the migration answer file is configured to run the installation in unattended mode. and then click Next. it must hold the operations master roles. When the Destination Server becomes a domain controller. you must change the boot order in the BIOS Setup to assure that the server does not attempt to boot to the USB device. the migration uses values from the file and you are not prompted for 17 . Insert the USB device or other removable media that contains the migration answer file in the Destination Server. Turn on the Destination Server and insert Windows SBS 2008 DVD1 in the DVD drive. For more information about how to change the BIOS Setup boot sequence. restart the computer and check the BIOS Setup to ensure that DVD-ROM is listed first in the boot sequence. Only one DHCP Server service can be active in the Windows SBS 2008 network. Note If the removable media that contains the answer file is a USB device. The global catalog server is a domain controller that manages a distributed data repository. which are used when standard data-transfer and update methods are inadequate. Note If the Destination Server does not boot from the DVD. press any key to do so. It contains a searchable. and then click Install Now. 2.• The operations master (also called flexible single master operations or FSMO) roles are transferred from the Source Server to the Destination Server. 3. The responsibility for managing the DHCP Server service is transferred from the Source Server to the Destination Server. see your hardware manufacturer's documentation. Verify your language and regional preferences. To install Windows Small Business Server 2008 on the Destination Server 1. • The Destination Server becomes a global catalog server.

select the I accept the license terms check box. click New. You are returned to the Where do you want to install Windows? page. 5. 8. c. 6. The partition is formatted before continuing. c. click Next. and then click Load Driver. on the Select the driver to be installed page. the Start the migration page is 18 . and then click Apply to accept the default partition size. Read the license terms. click Next. 9. which takes a few minutes. type 60000. and then click Browse on the Load driver dialog box. If the hard disk drive that you want to use is not listed. To create a partition from unpartitioned space. If the migration answer file is successfully detected. such as a Serial Advanced Technology Attachment (SATA) drive. The operating system is installed on the partition that you selected. on the Where do you want to install Windows? page. click the hard disk drive that you want to partition. Obtain the driver from the manufacturer. the installation does not continue. click Drive options (advanced). and then click Load Driver. if you use the recommended partition size of 60 gigabytes (GB). a. For example. 11. b. such as a USB drive. After the operating system is installed. and then type the partition size in the text box. 7. b. and then click Next. On the Where do you want to install Windows? page. click Next. type your product key in the text box. After the driver is loaded and the hard disk drive is listed. If you accept them. click Custom (advanced). Important After you finish this step. To create a partition that uses all of the unpartitioned space. click the hard disk drive that you want to partition. click New. Insert the removable media in your server. click Drive options (advanced). After the partition is created. create and then select the partition where you want to install the operating system. the Destination Server restarts. you cannot change the partition that you install the operating system on. click Drive options (advanced). Insert the media that contains the drivers. and then click Next. and then save it to removable media. 10. On the Type your product key for activation page. you must download the driver for the hard disk drive. and then click Apply. complete step c or d. click Drive options (advanced). Note If you do not choose to accept the license terms. Browse to the location of the drivers. and then click OK. The partition is formatted before continuing. On the Which type of installation do you want page.them unless they are invalid or missing from the answer file. When you finish installing the drivers. If you need to install drivers for your server hardware. After the partition is created. a.

Note If the migration answer file is configured for unattended mode. verify that the IP addresses of the Source and Destination Servers and the default gateway IP address are correct. click Do not get the most recent installation updates. It is also important that you read the Migration Guide before you start the migration. you can change it before you click Next. you must restore the backup.displayed. On the Get important updates page. validated backup of the Source Server because the migration makes permanent changes to the Source Server. click Go online and get the most recent installation updates (recommended). the text boxes on the following installation pages are populated with the information that you provided in the migration answer file. If it is not connected to the Internet. After the installation finishes and you configure Internet access. 12. If you selected this option. click Open Date and Time to verify the clock and time zone settings to check the date. On the Source and Destination Server information page. steps 11 through 15 are completed automatically. click the DHCP is running on the Source Server check box. On the Source and Destination Server networking information page. 16. you can go online and get the most recent updates. and then click Next. When you are finished. If the information is not correct. If appropriate. click Next. 13. verify that the information about the Source Server. If you encounter an issue during the migration and you need to return the Source Server to its original state. unless information in the migration answer file is invalid or missing. if the Destination Server is connected to the Internet. and certification authority are correct. the Connecting your server page is displayed and the most recent installation updates are downloaded. domain administrator account. On the Verify the clock and time zone settings page. The Migration Guide helps assure a successful migration to Windows SBS 2008. You must click the I have a current backup check box and the I have read the most recent version of the Migration Guide check box before you can click Next. 15. Note If the migration answer file is configured for attended mode. time. Important It is important that you have a current. Then click Next. because the process is complex and requires some preparation of the Source Server. Note You cannot change the Destination Server name or the internal domain name after you finish this step. 14. and time zone settings. 19 . Destination Server.

20 . review the migration process for information about which data you should migrate and use the instructions that apply to your environment. If the installation finishes with issues. you can unlock the desktop by using the built-in administrator account and leaving the password blank. the Installation finished page is displayed.17. ensure that the 64-bit drivers for your shared printers are available on the network. After the server restarts. • To avoid issues when users add printers on their client computers. On the Company information page. you must run the Migration Wizard to migrate settings and data from the Source Server to the Destination Server. you must migrate settings and data from the Source Server to the Destination Server by using the Migration Wizard. Migrate Settings and Data to the Destination Server After Windows SBS 2008 is installed. 19. The information is used to configure server tools so that you do not have to supply the same information multiple times. the Windows SBS Console displays the Home page with the Getting Started Tasks. however. 18. such as when no users are logged on to the network. and then click Next. You may either skip optional tasks or complete them at a more convenient time. and some are optional. Click View installation issues to close the page and to review the issues. You must complete the required tasks in the order that they are listed in the Migration Wizard. When you close the page. The Expanding and installing files page displays the progress of the final installation process. When the Windows SBS 2008 installation finishes. You can use the Migration Wizard only if the Source Server is running Windows SBS 2003 or Windows SBS 2008. you can unlock the desktop by using the administrator user account and the password that you provided in the migration answer file. you are automatically logged on using the administrator user account and password that you provided in the migration answer file. the Installation finished page is displayed. the server restarts. You may. Some tasks in the Migration Wizard are required. • After the installation finishes. Click Start the Migration Wizard to close the page and to start using the Windows SBS Console. • If the desktop is locked while Windows SBS 2008 is being installed and before the Destination Server is promoted to a domain controller. 20. where you can start using the Destination Server and resolving the issues. • If the desktop is locked while Windows SBS 2008 is being installed and after the Destination Server is promoted to a domain controller. The Home page of the Windows SBS Console displays the Getting Started Tasks. For information about running the Migration Wizard. verify that the information is correct. see Migrate Settings and Data to the Destination Server. To complete the migration process.

you should edit the Folder Redirection Group Policy object on the Destination Server to change the location of the users’ redirected data from the Source Server to the Destination Server. and then expand Group Policy Objects. click Start. In the Root Path text box. click Administrative Tools. 9. you will enable folder redirection on the Destination Server. click Cancel. Click Yes on the warning dialog box. 4. Right-click Documents. On the User Account Control dialog box. such as the command prompt. click Basic – Redirect everyone’s folder to the same location. the user may receive a security warning dialog box when starting some system programs from the Start Menu. If you use folder redirection on the Source Server or if you plan to start using folder redirection when you finish migrating to Windows SBS 2008. In the Setting dropdown menu. In the Group Policy Management navigation pane. type \\<Destination ServerName>\RedirectedFolders. click Continue. expand Windows Settings. see Change where to store data on the Destination Server for Windows SBS 2008 migration. b. and then click Edit. On the Target tab. To edit the Folder Redirection Group Policy object 1. On the Destination Server. expand Policies. Repeat steps 6-8 for Desktop and Start Menu. expand Domains. Configure folder redirection on the Destination Server When the Windows SBS 2008 installation finishes. expand <DomainName>. expand Forest:<DomainName>. and then click Group Policy Management. You may exit the wizard at any time and return later to finish it. 2. and then expand Folder Redirection. After you move the users’ redirected data. To exit the Migration Wizard. it opens to the Migration Wizard Home page. and then click Properties. 7. After you finish migrating user accounts and groups. In the Group Policy Management Editor navigation pane. 3. expand User Configuration. 6. selecting the same options on the Target tab. do the following: a. When you restart the wizard. where you can start the next available migration task. Right-click Small Business Server Folder Redirection. and then click OK. you should move the users’ redirected data to another partition or hard disk drive. 21 . Note When the Start Menu is redirected to the server. the users’ folder redirection data on the Destination Server is on drive C. 5.You have 21 days from the time that you finish installing Windows SBS 2008 to complete the migration. 8. For instructions.

10. Close the Group Policy Management Editor, and then close the Group Policy Management Console. Important Both the Source Server and the Destination Server must be connected to the network while the Group Policy changes are updated on the client computers. If you are about to demote and disconnect the Source Server from the network, ensure that Group Policy settings are applied to all client computers.

Start the Migration Wizard
To start the Migration Wizard 1. On the Home page for the Windows SBS Console, in Getting Started Tasks, click Migrate to Windows SBS. 2. On the Welcome page, read the information about the Migration Wizard, and then click Next. 3. On the Welcome page, read the information, and then click Next to start migrating data and settings from the Source Server to the Destination Server. The Migration Wizard Home page is displayed. 4. Click Next to start the first migration task. Instructions for completing each migration task are in the following sections: • Change where to store data on the Destination Server for Windows SBS 2008 migration • • Configure the network for Windows SBS 2008 migration Configure the Internet address Important Outlook Web Access (OWA) is not available for mobile users after you finish the Internet Address Management Wizard and before you finish migrating Exchange Server mailboxes and settings to the Destination Server. The Internet Address Management Wizard changes the OWA URL from https://domain.com/exchange to https://domain.com/owa, and the Source Server can no longer serve requests to https://domain.com/exchange. It is recommended that you notify your users before this change occurs and that you finish the steps in “Migrate Exchange Mailboxes and Settings” as soon as possible. • • • • Move network settings for Windows SBS 2008 migration Migrate Exchange mailboxes and settings Migrate users' shared data Migrate the SharePoint Web site 22

• • •

Migrate fax data Migrate Windows Server Update Services Data and Settings Migrate SQL Server data Important The Migration Wizard does not include a task for migrating SQL Server data. If you want to migrate SQL Server data, you must migrate the data before you decommission the Source Server. It is recommended that you migrate the SQL Server data before you finish the Migration Wizard to ensure that the SQL Server data is migrated within the 21 day grace period.

MoveTerminal Service licensing server for Windows SBS 2008 migration Important The Migration Wizard does not include a task for migrating a Terminal Service licensing server. If the Source Server is acting as a Terminal Services (TS) licensing server, you must migrate the TS licensing server role before you decommission the Source Server. It is recommended that you migrate the TS licensing server role before you finish the Migration Wizard to ensure that it is migrated within the 21 day grace period.

Migrate Remote Web Workplace configuration file Note The Migration Wizard does not include a task for migrating your Remote Web Workplace (RWW) configuration to the Destination Server. If you want to use the same RWW configuration, you must manually copy the configuration file to the Destination Server.

Migrate Gadgets Note The Migration Wizard does not include a task for migrating gadgets to the Destination Server. If you added gadgets to the Source Server, you must manually copy the gadgets the Destination Server.

• Important

Finish migration

Although data for line-of-business (LOB) applications is not migrated by using the Migration Wizard, you must use the procedures provided by your LOB-application provider to migrate the data within the 21 day grace period that you have to complete the migration process.

23

Change where to store data on the Destination Server for Windows SBS 2008 migration
Note This task is optional. If you plan to store data on a different partition on the Destination Server or on a separate data server, you should perform this task before you migrate data from the Source Server. When you choose a new location for the data, consider the storage requirements for the mailboxes and the shared folders that you want to migrate. To change where to store data on the Destination Server 1. On the Migration Wizard Home page, click Change where to store data on the Destination Server, and then click Next. 2. If you do not want to change where to store data at this time, click Skip this task, and then click Next. 3. If you want to change where to store data, click each data type to start the Move Data Folders Wizard, and then follow the instructions in the wizard. 4. When you finish changing where to store data, return to the Migration Wizard, click Task Complete, and then click Next.

Configure the network for Windows SBS 2008 migration
Note This is a required task. To configure the network 1. In the Migration Wizard, on the Migration Wizard Home page, click Next. 2. Click Start the Connect to the Internet Wizard. For information about how to complete the Connect to the Internet Wizard, see the "Connect to the Internet" section in "Managing Your Windows Small Business Server 2008 Network" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=104283). 3. When the wizard finishes, you are returned to the Migration Wizard Home page, and the task is marked Completed.

Configure the Internet address
Note Outlook Web Access (OWA) is not available for mobile users after you finish the Internet Important 24

on the Migration Wizard Home page. On the Migration Wizard Home page. Complete the Connect to the Internet Wizard. there may be a yellow warning icon next to the router name. click Start the Internet Address Management Wizard. and the Source Server can no longer serve requests to https://domain. and then click Next.com/fwlink/?LinkId=104283). click Migrate network settings. Click Configure the Internet address. For information about how to complete the wizard. do the following: a. The Internet Address Management Wizard changes the OWA URL from https://domain. b. and then click Next.com/exchange to https://domain. click Task Complete on the Configure the Internet address page. In the Migration Wizard. When the wizard finishes. 2. On the Configure Internet address page. see the "Setting up your Internet address" section in "Managing Your Windows Small Business Server 2008 Network" at the Microsoft Web site (http://go. and then click Next.mailboxes and settings to the Destination Server.microsoft. Ensure that the following ports are open and are directed to the IP address of the Destination Server: • • • Port 25 – SMTP e-mail Port 80 – HTTP Web traffic Port 443 – HTTPS Web traffic • Port 987 – HTTPS Web traffic for Windows SharePoint Services through Remote Web Workplace • Port 1723 – VPN if you plan to enable VPN on the Destination Server. The task is marked Completed on the Migration Wizard Home page. To configure the Internet address 1.com/exchange. Move network settings for Windows SBS 2008 migration Note This is an optional task. You may also need to enable the point-to-point tunneling protocol (PPTP) pass-through on your router. To migrate network settings 1.com/owa. or if the UPnP framework is disabled. If you do not want to migrate the network settings to the Destination Server or you 25 . c. 2. If your router does not support the UPnP framework. It is recommended that you notify your users before this change occurs and that you finish the steps in Migrate Exchange mailboxes and settings as soon as possible.

Expand Certificates. and then click Next. On the Migrate network settings page. If you want to migrate the network settings to the Destination Server. click File. 4. a message is displayed. click Computer Account. click Task Complete on the Migrate network settings page. and then click All Tasks. click Add again. do the following: a. 3. c. The task is marked Skipped on the Migration Wizard Home page. type mmc. and then they must re-install the self-issued certificates on the remote computers that are not joined to the domain. on the Migrate network settings page. you can move the certificate to Windows SBS 2008.exe. To migrate certificates. When the DNS forwarders are successfully migrated. On the Source Server. and then run the Add a Trusted Certificate Wizard to connect the certificate to Remote Web Workplace. Move certificates for Windows SBS 2008 migration Self-issued certificates Migrating self-issued certificates is not supported. click Launch the Mobile Users Group Migration Task. import it to the Destination Server. Click Add. and then click Add/Remove Snap-in. click Run. and then press ENTER. click Finish. expand Personal. b. You are returned to the Migrate network settings page. on the Migrate network settings page. Right-click the certificate that is issued to your Web site (for example: remote. Trusted certificates If you purchased a trusted certificate. export the certificate from the Source Server. and then click Certificates. To do this. You are returned to the Migrate network settings page. Click OK. The task is marked Completed on the Migration Wizard Home page. and then click OK. 2. 3. On the pop-up window. and then click OK. Users must transfer the Certificate Distribution Package to removable media. see Move certificates for Windows SBS 2008 migration for instructions. d.want to skip the task for now.contoso. a message is displayed. On the console. click Start. and then click Next. To export a trusted certificate from the Source Server 1. When you finish migrating the network settings. click Skip Task. Note 26 . and it is available to export. and then click Export. 4.com). When the Mobile Users group is successfully migrated. Click OK. e. choose Certificates from the list. 5. 6. If you want to migrate the Mobile Users group. click Launch the DNS Forwarders Migration Task.

Move the trustedcert. and then choose that certificate. Do not select Delete the private key if the export is successful. click All Tasks. To ensure that the Destination Server is using the newly imported certificate. and then click Connectivity. 7. On the pop-up. run the Add a Trusted Certificate Wizard. 12. Expand Certificates. To import the trusted certificate to the Destination Server 1. Browse to the location of the saved . and then click Add/Remove Snap-in. Type a password to protect the certificate file. C:\trustedcert. Choose Certificates from the list.pfx).pfx file to the Destination Server by using either the network or a USB drive. and then click Next. Ensure Include all certificates in the certificate path if possible and Export all extended properties are selected. If you are not sure which one to use. 10. Right-click Certificates. select Computer Account. 2. type mmc. Choose a location to save the . export the private key is selected. 8. Ensure that you choose a certificate that has a valid expiration date and that was issued by a trusted authority. and then click Next. On the Destination Server. 4. Open the Windows SBS Console. 12. 11. 2.pfx file (for example. 9. On the navigation bar. To run the Add a Trusted Certificate Wizard 1. 5. and then click OK. 11. and then click Add. Finish the wizard.There may be multiple certificates with the same name. In the task pane. and then click Next. 3. click Next. click Finish. and then click Next. In the Certificate Export Wizard. 10. click Add a trusted certificate. 9. open Internet Information Services (IIS). 27 . expand Personal. Finish the wizard.pfx file. 6. click File. 8. Ensure that the certificate will be imported to the Personal folder. and then click Next. and then click Certificates. click Next. 7. and then click Next.exe. click the Network tab. and then press ENTER. and then click Next. On the console. Ensure Yes. and then click Import. Type the password that you typed in the Export procedure. ensure that Mark this key as exportable and Include all extended properties are selected. click Start. determine which certificate IIS is using on the Source Server. On the Certificate Import Wizard Welcome page. 3.

For more information about creating a . you should clean up the Exchange Server database and verify its integrity by doing the following: • Ask each user to do the following: • Delete unneeded mail from their mailbox. see "Using Backup to Back Up and Restore Exchange Data" at the Microsoft Web site (http://go. In the toolbar. click File. On the Welcome page. On the Choose an installed certificate page. • Review and delete unneeded personal documents from the user’s folders. you should make the same configuration changes on the Destination Server before migrating Exchange Server data. 6. click the certificate that you just imported. see Outlook Help on the client computer. the Company Shared folder. click Microsoft Forefront Server Security.com/fwlink/?LinkId=120968). and then click Next. Before you migrate Exchange Server mailboxes and settings to the Destination Server. • Archive older mail to a . • Back up the database.4. For information about backing up an Exchange Server 2007 database.pst file.microsoft.com/fwlink/?LinkId=120967). On the Get the certificate page. 3. click I want to use a certificate that is already installed on the server. 5. and then click Next. see the "Disaster Recovery Tools and Wizards" at the Microsoft Web site(http://go. Change the configuration to match the configuration of Forefront Protection 2010 for 28 . click Templates. if appropriate. click All Programs. and then click Next. • If the Microsoft Forefront Protection 2010 for Exchange Server configuration was modified on the Source Server.pst file. To change the configuration of Forefront Protection 2010 for Exchange Server on the Destination Server 1. and other shared folders on the server. Migrate Exchange mailboxes and settings Note If Exchange Server is installed on the Source Server. 7. click Finish. On the Destination Server.microsoft. click Exchange Server. When the wizard finishes. including mail in the Deleted Items and Sent Items folders. and then ensure that View Templates is selected. For more information. this is a required task. 2. • Use the Exchange Server tools to help you determine the status of the Exchange Server 2007 database. click Start. and then click Forefront Server Security Administration. read the information.

click Task Complete on the Migrate Exchange mailboxes and settings page. Enable circular logging on storage groups for Windows SBS 2008 migration on the Destination Server (optional). e. You must move the mailboxes to the Destination Server for all user accounts added during this time frame. On the Migration Wizard Home page. 29 . f. Migrate Internet connectors from the Source Server. the mailboxes are added on the Source Server. return to the Migration Wizard. 3. Repeat the instructions in this section before you uninstall Exchange Server 2007 in the final migration steps to decommission the Source Server. g. Migrate Internet connectors Remove Internet connectors on the Source Server E-mail is automatically enabled between the Source Server and the Destination Server when Windows SBS 2008 is installed in Migration Mode. the Destination Server becomes responsible for inbound and outbound Internet e-mail. Move Exchange Offline Address Book for Windows SBS 2008 migration from the Source Server to the Destination Server. click Migrate Exchange mailboxes and settings. This is by design. To migrate Exchange Server mailboxes and public folders 1. Migrate POP3 connectors (optional) from the Source Server.Exchange Server on the Source Server. When you remove the Internet send connector from the Source Server. Migrate CompanyWeb connector from the Source Server to the Destination Server. and then click Next. When you finish migrating the mailboxes and public folders. Perform each of the following tasks (click each link for instructions): a. and then click Next. b. Note If you add user accounts after moving mailboxes to the Destination Server and before uninstalling Exchange Server 2007 from the Source Server at the end of migration. Move mailboxes from the Source Server to the Destination Server. c. 2. d. Move Exchange Server public folders from the Source Server to the Destination Server.

On the Before you begin page. click All Programs. click Microsoft Exchange Server 2007. Right click Smart host for Internet e-mail. In the navigation pane. and then click Exchange Management Console. The Internet Address Management Wizard creates Internet send and receive connectors on the Destination Server. 4. In the navigation bar. right-click Windows SBS Internet Send <SourceServerName>. you must configure the Internet Mail on the Destination Server with the settings that you documented on the Source Server. and then expand Hub Transport. click the Network tab. click Next. Click Start. open the Windows SBS Console. Click the Send Connectors tab. In the navigation bar. 5. proceed to the next task to migrate Exchange mailboxes and settings. 8. 7.Important Before you remove the Exchange Server Internet connectors from the Source Server. and then click Connectivity 3. 2. When you finish configuring the Internet mail. 10. The Configure Internet Mail Wizard starts. open the Windows SBS Console. 4. 9. Click Yes to confirm that you want to delete the connector. Configure Internet connectors on the Destination Server After you remove the Internet connectors on the Source Server. Right-click Smart Host for Internet e-mail. This is a required task in the Migration Wizard. On the User Account Control dialog box. 3. To remove the Exchange Server 2007 Internet connectors from the Source Server 1. 2. and then clickView outbound Internet e-mail properties. 6. click Continue. To configure Internet Mail 1. 30 . and then click Cancel to exit the wizard without finishing. and then clickView outbound Internet email properties. ensure that you ran the Internet Address Management Wizard on the Destination Server. On the Source Server. The Configure Internet Mail Wizard starts. and then click Connectivity. Document the settings on each page of the wizard. expand Organization Configuration. Follow the instructions in the wizard. and then click Remove. click the Network tab. On the Destination Server. Note All e-mail to the Internet starts flowing through the Destination Server.

click Edit. On the navigation bar. Right-click POP3 Connector. Remove each user account that is listed. 3. To add POP3 connectors in Windows Small Business Server 2008 1. 2. 3. In the navigation bar.Migrate POP3 connectors Note This is an optional step. and then click View POP3 Connector properties. Right-click POP3 Connector. right-click Exchange Management Shell. and then click Run as administrator. Note Global mailboxes are not supported in Windows SBS 2008. To remove POP3 connectors from the Source Server 1. 2. click Continue. type Exchange Management Shell. open the Windows SBS Console. you can map a POP3 account to an e-mail enabled group in Windows SBS 2008. and then press ENTER: set-transportserver –identity <DestinationServerName> -RootDropDirectorypath 31 . 5. On the Mail Accounts tab. On the Source Server. 4. 5. On the Destination Server. Then. in the search field. Migrate CompanyWeb connector The CompanyWeb connector moves e-mail from Exchange Server to the internal Windows SharePoint Services Web site. Click each user account. Follow these steps to move the CompanyWeb connector from the Source Server to the Destination Server. and then click OK. click the Network tab. and then write down the POP3 Mailbox to Exchange settings. If you did not configure the POP3 connectors on the Source Server. 3. When you finish adding the POP3 mailboxes. type the following. 2. and then add each of the accounts that were on the Source Server. and then click View POP3 Connector properties. on the Destination Server. In the User Account Control window. skip this step. Instead. At the command prompt. open the Windows SBS Console. click the Network tab. 4. and then click Connectivity. To migrate the CompanyWeb connector to the Destination Server 1. To start the Exchange Management Shell. and then click Connectivity. click OK. click Start. click Add.

type Second Storage Group. 32 . 5. Before you move the public folders to the Destination Server. On the Destination Server. To create an Exchange Server storage group and a Public Folder database 1. and then click Finish. 4. At the command prompt. 4. click Start. 2. Perform step 6 only if you are a Technical Adoption Program (TAP) customer.C:\inetpub\mailroot. 3. and then press ENTER. In the work pane. click Second Storage Group. type get-foreignConnector | fl and then press ENTER. Ensure that SourceTranportServers lists the name of the Destination Server. At the command prompt. 6. and then click Finish. Before moving the public folder database from the Source Server. 6. click New Storage Group. and then press ENTER: set-ForeignConnector –identity “Windows SBS Company Web Connector <SourceServerName>” Note -SourceTransportServers <DestinationServerName>. you must create a storage group and a Public Folder database on the Destination Server. The Get-PublicFolderStatistics command lists all the data that is contained in the public folder store. set-ForeignConnector –identity “Windows Server \”Cougar”\ Company Web Connector <SourceServerName>” –name <DestinationServerName>” “Windows SBS Company Web Connector 7. click New. At the command prompt. Move Exchange Server public folders Exchange Server 2007 does not create a Public Folder database when a server on the network already has a Public Folder database. | fl. click New. On the New Public Folder Database page. in the text box for the name of the storage group. At the command prompt. in the Public folder database name text box. In the navigation pane. run the GetPublicFolderStatistics command. click Microsoft Exchange Server 2007. and then press ENTER. expand Server Configuration. On the New Storage Group page. type the following. and then click Exchange Management Console. and then in the Actions pane click New Public Folder Database. 5. click All Programs. In the Actions pane. type get-transportserver Ensure that RootDropDirectorypath is set. type Public Folder Database. Click Continue on the User Account Control dialog box. and then click Mailbox. type the following. 7.

2. click Exchange Server 2007. 3. Note Include the single quotation marks when you type the command. On the Destination Server. click All Programs. ‘C:\Program Files\Microsoft\Exchange 33 . click All Programs. 2. click Exchange Server 2007. Note Include the single quotation mark when you type the command. You can use the MoveAllReplicas. type cd Server\Scripts’ and then press ENTER. click Start. On the Destination Server. 2. click Exchange Server 2007. At the Windows PowerShell prompt. and then click Exchange Management Shell. Type the following. At the Windows PowerShell prompt. You can verify the status by using the Get-PublicFolderStatistics command. click All Programs. To move Exchange Server public folders to the Destination Server 1. type cd Server\Scripts’ and then press ENTER. Type the following. and then click Exchange Management Shell. You must wait for the next instance of public folder replication to finish before the public folder replicas are removed. click Start. 3. Open the text file to verify that all of the public folders on the Source Server are listed. and then click Exchange Management Shell. and then press ENTER: MoveAllReplicas.txt 4. On the Destination Server.ps1 script to move all Exchange Server public folders from the Source Server to the Destination Server. click Start. type cd Server\Scripts’ and then press ENTER. To run the GetPublicFolderStatistics command 1. and then press ENTER: Get-PublicFolderStatistics –server ‘C:\Program Files\Microsoft\Exchange <SourceServerName> | fl | out-file C:\Users\<YourUserName>\Documents\PF<SourceServerName>stat. At the Windows PowerShell prompt.To run the GetPublicFolderStatistics command 1.ps1 –Server ‘C:\Program Files\Microsoft\Exchange <SourceServerName> –NewServer <DestinationServerName> Note It can take up to 24 hours to move all public folders to the Destination Server.

and then click Mailbox. Note Include the single quotation marks when you type the command. type cd Server\Scripts’. 3. and then press ENTER. type the command: Remove–PublicFolderDatabase –Identity "MyServer\Second Storage Group\Public Folder Database” 34 . click Continue. On the Client Settings tab. right-click Mailbox Database. and then click Exchange Management Shell. do the following: a. and then click Properties. 2. Type the following. expand Server Configuration. Click Browse on Default public folder database. click Start. On the Destination Server. 3. click Exchange Server 2007. In the results pane. you must set the default Public Folder database on the Destination Server. and then click Exchange Management Console. click All Programs. type the following. click Start. 3. and then press ENTER: Remove–PublicFolderDatabase –Identity "<Server Name>\<Storage Group Name>\<Public Folder Database Name>” ‘C:\Program Files\Microsoft\Exchange For example. To run the Remove-PublicFolderDatabase command 1. to remove a database named "MyServer\Second Storage Group\Public Folder Database". click Microsoft Exchange Server 2007. Click OK. under First Storage Group. and then press ENTER: Get-PublicFolderStatistics –server <DestinationServerName> | fl | out-file C:\Users\<YourUserName>\Documents\PF<DestinationServerName>stat. In the User Account Control dialog box. At the Windows PowerShell prompt. To set the default Public Folder database on the Destination Server 1. open the text file that you just generated and compare it to the text file that contains the public folder data on the Source Server.txt 4. and then click OK. click All Programs. In the navigation pane.Note Include the single quotation marks when you type the command. b. 2. At the command prompt. On the Destination Server. 4. In the Select Public Folder Database dialog box. To verify that the public folder replication is complete. After the public folders are moved to the Destination Server. select the Destination Server. 6. 5.

In the action pane. see the Microsoft Web site (http://go. expand Organization Configuration. 4. 9. On the Completion page. 6. right-click Default Offline Address List. Click Finish. Click Add. confirm that the OAB was moved successfully. click the name of the Destination Server. ensure that the Destination Server is selected.microsoft. ensure that all users open Outlook after their mailboxes are moved to the Destination Server. If it was not. Click the Distribution tab and do the following: a. 11. you must update the profiles manually to point to the Destination Server. If both servers are running. and then click Back to correct the problem. click All Programs. review the summary for an explanation. 2. and then click Exchange Management Console. click Microsoft Exchange Server 2007. On the Move Offline Address Book page. Delete the Source Server as a distribution server. To move the OAB and to change the server that generates it 1. while both servers are running. and then you must change the server that generates the OAB. In the Exchange Management Console navigation pane.com/fwlink/?LinkID=123793). 10. Click Continue on the User Account Control dialog box. click Start. and then click Mailbox. Click Move to move the OAB to the Destination Server. Move mailboxes Important To make it easier to manually update the Outlook profiles. Outlook automatically updates the profiles to point to the Destination Server. Otherwise. click Browse. In the results pane. 7. In the results pane. b. click the Offline Address Book tab. 12.For more information about migrating public folders and for detailed troubleshooting steps. and then in the Select OAB Virtual Directory dialog box. click Move. Click OK twice. The Move Offline Address Book Wizard starts. 3. 35 . Move Exchange Offline Address Book for Windows SBS 2008 migration You must move the offline address book (OAB) from the Source Server to the Destination Server. On the Destination Server. and then click Properties. and then click the OAB that you want to move to the Destination Server. and then click OK. 8. 5.

you can manually enable it. and then click Exchange Management Console. To enable circular logging 1. and then click Mailbox. 7. The Move Mailbox Wizard starts. and then click OK. and then click Move. Note It is recommended that you click Skip the corrupted messages on the Move Options page of the wizard and that you set the maximum number of messages to skip. Enable circular logging on storage groups for Windows SBS 2008 migration Circular logging helps keep the Exchange Server storage logs from growing. click the Database Management tab. On the Destination Server. and then proceed to the next task to migrate Exchange Server mailboxes and settings. 6. click Continue. Verify that no more mailboxes on the Source Server are listed in the details pane of the Exchange Management Console. expand Server Configuration. In the User Account Control dialog box. 2. You may need to scroll to the right until the Server field is displayed. 4. provide the requested information. click Start. click the Database Management tab. 6. 5. In the First Storage Group dialog box. 5. and then click Mailbox. click Microsoft Exchange Server 2007. Click Move Mailbox in the task pane. 4. If circular logging is not enabled after migration. select the Enable Circular Logging check box. In the Exchange Management Console navigation pane. and then click Properties. and then click Exchange Management Console. click All Programs. In the Exchange Management Console navigation pane. In the results pane. or you must run the Move Mailbox Wizard again. expand the Recipient Configuration node. In the Move Mailbox Wizard. select all of the mailboxes that are listed and that are on the Source Server. click Microsoft Exchange Server 2007. right-click First Storage Group. In the results pane. 3. In the results pane. On the Destination Server. If mailboxes are skipped because the maximum number of corrupted messages is exceeded. 2. click Start. you must delete those mailboxes before you uninstall Exchange Server 2007 from the Source Server later in the migration process. right-click Second 36 .To migrate Exchange Server 2007 mailboxes 1. 3. Click Continue on the User Account Control dialog box. click All Programs.

click Migrate users’ shared data. In the Second Storage Group dialog box. After you set the permissions. Follow these instructions to migrate users’ shared data: a. When you finish migrating shared data. Copy users' shared folders to the Destination Server c. and then click Next. and then in the Tasks pane click Change folder permissions. Copy additional shared folders to the Destination Server Note You must set the shared folder permissions and the NTFS permissions for the shared folders on the Destination Server by using the information that you collected in step 2 in Configure a new shared volume on the Destination Server. Close the Exchange Management Console. in the Migration Wizard. and then click OK. Document the shared folder permissions. Configure a new shared volume on the Destination Server b. Migrate users' shared data Note This is an optional task. Repeat steps 3 and 4 until the permissions are documented for all shared folders that 37 . In the navigation bar. 8. Configure a new shared volume on the Destination Server To document shared folder properties on the Source Server 1. 7. and then click Cancel. 2. click Shared Folders and Web Sites. On the Destination Server. and then click Properties. 3. On the Source Server. 5.Storage Group. return to the Migration Wizard on the Destination Server. 3. 4. Click a shared folder. select the Enable Circular Logging check box. and then click Next. To migrate users’ shared data 1. 2. click Task Complete on the Migrate shared data page. the shared folders are displayed in the Windows SBS Console on the Shared Folders tab. open the Windows SBS Console.

navigate to the drive and local folder on the Destination Server where you want to migrate the data. on the Destination Server. you must ensure that disk quotas on the Destination Server match or exceed the disk quotas that were set on the Source Server. Copy users' shared folders to the Destination Server Copy the users’ shared folders to the Destination Server by using the RoboCopy command. Type the groups and user accounts in the text box. 6. 3. 2. On the Shared Folder Location page. and then click Permissions. click each group or user account in the list. click Users and groups have custom share permissions. and then click Next. click Next. Review the settings that you chose in the Share folder settings text box. On the NTFS Permissions page. b. 4. If the folder does not exist on the Destination Server. and then assign the shared folder permission that you documented in step 2. Click the Shared Folders and Web Sites tab. click Make New Folder to create the folder. Click OK to save the changes and to return to the wizard. click Browse. On the SMB Settings page. open the Windows SBS Console. To configure a new shared volume 1. click OK. On the Share Protocols page. and then search for “set disk space quotas for all users. click Close. 8. click Next. Click Next until you reach the Review Settings and Create Share page. On the Permissions dialog box. and then click Create. Note Disk quotas are enabled on the Destination Server for the partition where the user’s shared folder is located. When you finish adding groups and user accounts. click Add. a. click Shared Folders. click Help and Support. click Start. and then in the Tasks pane click Add a new shared folder. click OK to add them to the Group or user names list. 5.you plan to migrate to the Destination Server. 9. click Next. On the Confirmation page. In the Group or user names list. On the Destination Server. 7. or click Advanced to select the groups and user accounts. For more information about modifying the default quotas for all users.” 38 . On the SMB Permissions page. d. c. 10. If you have modified the disk quotas on the Source Server. e.

you must update the script to map to the drives on the Destination Server. After you migrate any additional shared folders. you must share the folders and set permissions.microsoft. Notes When you copy additional shared folders. click Start. line-of-business application folders.com/fwlink/?LinkId=120040). and then click Run as administrator.com/fwlink/?LinkID=121010.To copy users’ shared folders 1. 2. right-click Command Prompt. On the Destination Server. type the following: robocopy \\<SourceServerName>\UserShares \\<DestinationServerName>\UserShares /E /COPY:DATSOU /LOG:C:\Copyresults. click Start. At the command prompt. You can also compare the number and size of the files that were in the users’ shared folders on the Source Server with the number of files that are now on the Destination Server. you are not sharing them.txt to verify that the files were copied correctly. You can view C:\Copyresults. On the User Account Control page.microsoft. On the Destination Server. For information about sharing folders and setting permissions. and then click Run as administrator. click Continue. and general user data folders to the Destination Server. you are only copying the folders. see Managing Files and Folders in Windows Small Business Server 2008 at the Microsoft Web site http://go. click Continue. see the Microsoft Web site (http://go. At the command prompt. right-click Command Prompt. To copy folders to the Destination Server 1. type the following: \\<SourceServerName>\<ShareName>\<FolderName> \\<DestinationServerName>\<ShareName>\<FolderName /E /COPY:DATSOU robocopy 39 .txt Note RoboCopy is an alternative to Xcopy and is a standard feature in Windows Server 2008. If you are using a logon script to map drives to the shared folders. On the User Account Control page. Copy additional shared folders to the Destination Server Important Neither Xcopy nor RoboCopy support migration of encrypted files. For information about RoboCopy. 2. 3. 4. 3.

If you want to migrate your internal Web site. expand <ServerName>.bak -overwrite -includeusersecurity 40 . and then verify that the internal Web site is displayed properly. Click Start. perform the steps in the following procedures. 3. 6. on the Destination Server. 3. and then click Next. 2. 5. If necessary. browse to http://companyweb. Steps performed on the Source Server 1. expand Forward Lookup Zones. 4. For more information about modifying the default quotas for all users. At the command prompt. and then verify that the Alias (CNAME) record for the internal Web site points to the fully qualified domain name (FQDN) of the Source Server. Repeat step 3 for additional folders that you want to migrate to the Destination Server. In Internet Explorer. Note If you copy a folder to the same partition as the users’ shared folders. At the command prompt.” Migrate the SharePoint Web site Note This is an optional task. and then click Next. click Start.txt 4. click Help and Support. and then click DNS. and then search for “Set disk space quotas for all users. type the following: stsadm –o export –url http://companyweb –filename C:\cwebexport. update the properties of the internal Web site. expand <DomainName>. and then click Run as administrator. 2. If you do not want to migrate your internal Web site. click Migrate SharePoint Web site. click Administrative Tools. If the internal Web site is not displayed properly or if you are unsure. In the Migration Wizard. click Start. type the following: cd \ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\ 7. disk quotas also apply. Click Continue in the User Account Control dialog box. on the Migration Wizard Home page. click Skip Task. right-click Command Prompt. In the DNS Manager console./LOG:C:\Copyresults. To migrate the internal Web site 1.

8. When the import command finishes. In the DNS Manager console. When the export command finishes.bak -includeusersecurity 10. 12.bak to a shared location on your network or to removable storage media.8. and then change the properties of the Alias (CNAME) record for the internal Web site to point to the fully qualified domain name (FQDN) of the Destination Server.bak from the shared location on your network or removable storage media to the C drive on the Destination Server 2. expand Forward Lookup Zones. right-click Command Prompt. 11. browse to http://companyweb to verify that content from the old internal Web site is imported into the new internal Web site. 4. return to the Migration Wizard. When you finish migrating your internal Web site to the Destination Server. 3. and then click Next. and then click DNS. click Task Complete on the Migrate your internal Web site page. 9. Copy the file cwebexport. In Internet Explorer. Note You must install and configure the Fax service on the Destination Server before you start 41 . Copy the file cwebexport. Migrate fax data Note This is an optional task. such as a USB drive. In Internet Explorer. type the following: ipconfig /flushdns 7. Click Start. click Administrative Tools. browse to http://companyweb to verify that the new internal Web site is displayed. Click Continue in the User Account Control dialog box. type the following: cd \ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\ 9. At the command prompt. expand <DomainName>. check the logs for errors. Click Start. and then click Run as administrator. 6. At the command prompt. type the following: stsadm –o import –url http://companyweb –filename C:\cwebexport. 5. Steps performed on the Destination Server 1. expand <ServerName>. At the command prompt. check the logs for errors.

click the Administrators (WSSGUA\Administrators) account. click Start. Note The files in the Common Coverpages folder already have the correct permissions. To change the permissions of the fax cover pages on the Destination Server 1. Right-click confident. the folder on the Destination Server is overwritten when you migrate the fax data. click the Security tab. 5. click Migrate fax data. click Skip this task. 2.cov Language-CountryCodegeneric. Note 42 . and then navigate to the C:\ProgramData\Microsoft\Windows NT\MSFax\Common Coverpages\LanguageCountryCode folder. You should back up your fax data on the Destination Server before you migrate the Fax data. on the Migration Wizard Home page.cov To migrate fax data 1. Select a check box to choose where you want the fax data to be saved on the Destination Server. select the Full control check box. If you customized the fax cover pages on the Source Server and want to migrate the cover pages to the default location on the Destination Server. and then click Next. 4. 7. Click OK twice. do the following: a. click Computer.Important If you have fax folders on both the Source and Destination Servers that share the same name. you must change the permissions for the existing fax cover page files on the Destination Server. In the Properties dialog box. You need to change the permissions for the files in the Language-CountryCode folder. if you want to skip this task. and then click Edit. and then click Next. On the Migrate fax data page.cov in the Language-CountryCode folder. 6. On the Destination Server. If you want to complete this task. and then click Properties. In the User Account Control dialog box. click Continue. In the Migration Wizard. Repeat steps 2-6 for the following files: • • • Language-CountryCodefyi. 2. and then click Click to start migrating your fax data.cov Language-CountryCodeurgent. 3. in the Allow column. In the Permissions dialog box. and then.

The following message is displayed: An error occurred while migrating fax data is displayed. 43 . click Start. see “Managing Software Updates in Windows Small Business Server 2008” at the Microsoft Web site http://go. update approvals. b. To migrate Windows Server Update Services. If you do not want to migrate the fax cover pages. Migrate Windows Server Update Services Data and Settings Note This is an optional task. 1. Run the Server Cleanup Wizard 2. When the task finishes. Run the Server Cleanup Wizard When you run the Server Cleanup Wizard on the Source Server. and then import them to the Destination Server.microsoft. click Administrative Tools. and computer group membership as the Source Server. Click Task complete. Replicate the Update Services database 4. you are returned to the Migrate fax data page. it deletes duplicate. To run the Server Cleanup Wizard 1. It also deletes updates for computers that have not contacted the server. Make the Destination Server the stand-alone Update Services server 6. Note You can migrate Update Services data only if the source and destination versions are the same. over time. Verify Update Services Computer Groups For more information about configuring and using Update Services. and then click Next. On the Source Server.If you chose the default location for the files and did not change the permissions of the files on the Destination Server. click OK. reach the same level of update compliance. Set up the Update Services replica server 3. Update Services on the Destination Server will. Verify that the replication is successful 5. the Migration Wizard cannot overwrite the files. SP1. and expired updates. unused.com/fwlink/?LinkID=130661.0. you must export software updates and metadata from the Source Server. If you did not change the Windows Server Update Services default settings on the Source Server. and then click Microsoft Windows Server Update Services 3.

0 SP1. This makes the Source Server the upstream server for Update Services on the Destination Server. To determine the port number that Update Services is using on the Source Server 1. 3. On the Source Server. see To determine the port number that Update Services is using on the Source Server. In the Update Services navigation pane. In the Update Services navigation pane. click Administrative Tools. 4. On the Update Source tab. 5. 5. expand SourceServerName. 6. 2. ensure that all options are selected. type the port number that WSUS is using on the Source Server. click Update Source and Proxy Server. 4. and then click Microsoft Windows Server Update Services 3. and then click Options. On the User Account Control dialog box. 2. In the Update Services navigation pane. and then. click Continue. click Start. Note If you do not know the port number that Update Services is using on the Source Server. 6. and then click Options. On the User Account Control dialog box. 4. note the port number listed in the Overview section and 44 . click ServerName. type the name of the Source Server in the Server name text box. In the results pane. Select the This server is a replica of the upstream server check box. 3. and then click Next. In the results pane. In the results pane. and then click OK. expand DestinationServerName. In the WSUS Server Cleanup Wizard. On the User Account Control dialog box. click Start. click Administrative Tools. click Continue. in the Port number text box. 3. On the Destination Server. click Server Cleanup Wizard. and then click Microsoft Windows Server Update Services 3. When the wizard completes. click Finish. click Synchronize from another Windows Server Update Services server. To set up Update Services on the Destination Server as a replica 1.0 SP1. Set up the Update Services replica server Set up Update Services on the Destination Server to replicate the Update Services database on the Source Server.2. click Continue.

Replicate the Update Services database Update Services on the Destination Server synchronizes with Update Services on the Source Server. On the Destination Server. and then click Microsoft Windows Server Update Services 3. On the Destination Server. and then it downloads the database. click Continue. click DestinationServerName. Updates Needing Files counts down to zero when the download is complete. where xx is the percent complete. in the Overview section and Synchronization Status subsection. click Start. 2. 4. The synchronization process starts and provides tracking information by changing Synchronize Now to Synchronization: xx%. click Administrative Tools. 2. In the Update Services navigation pane. 4. To verify that the download finishes successfully 1. 3. click Synchronize Now. click DestinationServerName. click Continue. click Administrative Tools. the Update Services database starts downloading from the Source Server to the Destination Server. There may be a delay of several minutes before the download begins. 3. If the synchronization and download do not finish successfully. click Start. In the results pane. In the Update Services navigation pane. 5. In the results pane. SP1. Note Do not begin monitoring the database download until the synchronization finishes successfully. in the Overview section and Download Status sub-section. 45 . On the User Account Control dialog box. Last Synchronization is updated with the date and time that is finishes. After the synchronization finishes. You can find details about the download on the Synchronizations node on the Update Services navigation pane. Verify that the download finishes successfully.Connection sub-section. To replicate the Update Services database to the Destination Server 1. do the following: • Verify that the server name and the port number are correct on the Update Source and Proxy Server page.0 SP1.0. and then click Microsoft Windows Server Update Services 3. • Analyze the details of the failure. When the synchronization finishes. On the User Account Control dialog box.

click Start. If the folder contents do not match. 3. On the User Account Control dialog box. On the User Account Control dialog box. Make the Destination Server the stand-alone Update Services server In this step. clear the This server is a replica of the upstream server check box. click Update Source and Proxy Server. The number of files in the %SYSTEMDRIVE%\WSUS\WSUSContent folder on the Destination Server should match the number of files in the %SYSTEMDRIVE%\WSUS\WSUSContent folder on the Source Server. and then click Microsoft Windows Server Update Services 3. Verify Update Services Computer Groups The Computer Groups that are set up in Update Services are used by Windows SBS 2008 to determine which computers on your network receive updates. Examine the number of files in the WSUSContent folder. you should verify that the replica on the Destination Server matches the database on the Source Server.0 SP1. On the Destination Server. expand DestinationServerName.Verify that the replication is successful When the database replication finishes. and then click Options. On the Update Source tab. click Continue. click Continue. 3. 6. wait until the file download does finish. In the Update Services navigation pane. expand 46 . you set the Destination Server as the stand-alone Update Services server. 5. If not. To verify the definitions of the Update Services Computer Groups 1. 2. 4. make sure that the file download is finished. 2. click DestinationServerName. In the results pane. click Administrative Tools. so that it can start receiving updates directly from Microsoft Updates. and then click Microsoft Windows Server Update Services 3. click Administrative Tools. You can specify in the Windows SBS Console which computers belong to the Included and Excluded Computer Groups. and then check again. In the Update Services navigation pane. click Start. Note Do not attempt to verify the replication until you verify that the Update Services database download finished. On the Destination Server. To set the stand-alone server 1. Select the Synchronize from Microsoft Update check box. and then click OK.0 SP1.

Update Services Server Computers 5. and then click Add. You can install SQL Server 2008 Standard for Small Business as your database for a business application.htm or D:\SQL2008\x32\Servers\ReadMeSQL2008.Computers. Verify that the following Computer Groups are listed: a. use the Premium Technologies disc to install the Windows Server® 2008 operating system and SQL Server 2008 Standard for Small Business.htm (where D is the letter of your DVD drive). Before you begin. After you finish installing Windows SBS 2008. Right-click All Computers. review the following: • Do not migrate the instance of SQL Server 2005 Express that is installed on the Source Server for monitoring (SBSMONITORING). do the following to create it: a. Note You must be a network administrator to complete this procedure. Update Services Excluded Computers c. To do this. open either D:\SQL2008\x64\Servers\ReadMeSQL2008. Unassigned Computers b. • To review the release notes for SQL Server 2008. 4. • Do not migrate the instance of Windows Internal Database (SQL Server 2005 Embedded Edition) that is installed for Windows Server Update Services and for Windows SharePoint® Services (MICROSOFT##SSEE). and then expand All Computers. Migrate SQL Server data Note This is an optional task. which comes with Windows SBS 2008 Premium Edition. But you can install SQL Server 2008 Standard Edition instead. and then click Add Computer Group. because this is not supported. purchase a copy of SQL Server 2008 Standard Edition. Update Services Client Computers d. If the Update Services Excluded Computers group does not exist. Note These instructions explain how to install SQL Server 2008 for Small Business. because this is not supported. on the Premium Technologies disc. 47 . type Update Services Excluded Computers in the Name text box. b. In the Add Computer Group dialog box. and then follow these instructions.

exe. verify that you have no potential installation problems.NET Framework 2. you must accept the agreement.NET Framework 2. The Install SQL Server 2008 window opens. review the licensing agreement. Move a SQL Server 2000 instance or SQL Server 2005 instance to SQL Server 2008 for Windows SBS 2008 migration. After the prerequisites are installed. 5. 6. 4. You can also click any of 48 . 2. Click New Installation in the task list. Note If you are installing SQL Server 2008 to use with a line-of-business (LOB) application. you must use D:\SQL2008\x86\Servers\setup. on the End User License Agreement page. where D is the letter of your DVD drive. 2. click Finish.exe. review the licensing agreement. Insert the Microsoft SQL Server 2008 Standard Edition for Small Business disc into your DVD drive.0 installation dialog box appears. On the System Configuration Check page.To migrate the SQL Server data 1. 7. click the Database Engine Services check box. and then run either D:\SQL2008\x64\Servers\setup. you must accept the agreement. Install a new instance of SQL Server 2008 for Windows SBS 2008 for Windows SBS 2008 migration. On the End User License Agreement page. and then click Next. Specify SQL Server collation settings for Windows SBS 2008 migration. and then click Next. click the Reporting Services check box. Install a new instance of SQL Server 2008 for Windows SBS 2008 for Windows SBS 2008 migration To install a new instance of SQL Server 2008 1. Important If you are installing SQL Server 2008 in a 32-bit version of Windows Server 2008. To continue. When . If your LOB application requires that you install the Microsoft SQL Server 2008 Reporting Services component. To continue. 3. the SQL Server Installation Center is opened in a new window. click Install. On the Feature Selection page. 3.0 is installed. On the Installation Prerequisites page. see the documentation for that application to ensure that it is compatible with SQL Server 2008 and to determine if there are specific configuration requirements. If the .exe or D:\SQL2008\x86\Servers\setup. 8.

Click Windows Authentication Mode. 12. c. choose the Default instance. click Add or Remove to select the user accounts. On the Server Configuration page. 14. click Install the Native mode default configuration. b. Important If you are installing SQL Server 2008 as part of your LOB installation. On the Instance Configuration page. On the Error and Usage Reporting page. You can also click Add Current User to add the current user account to the administrators list. see Specify SQL Server collation settings for Windows SBS 2008 migration. If you use a domain user account. c. You can also click Add Current User to add the current user account to the administrators list. On the Reporting Services Configuration page. 13. specify non-default collations for the Database Engine and Analysis Services. b. Do the following: a. In Specify SQL Server administrators. For more information. Important You can use either a local user account or a domain user account as the service accounts. consult the documentation for the LOB application in order to determine whether you need to create a named instance of SQL Server 2008 other than the Default instance. Click Windows Authentication Mode. d. the Analysis Services Configuration page is displayed. Click Next. do the following: a. Click Next. You can also choose 49 .the other check boxes to install additional features. the server that you are installing SQL Server 2008 on must be connected to the domain. c. On the Collation tab. d. Click Next. 9. If you are installing the Analysis Services feature. Or type a shared account and password in Use the same account for all fields. click Add or Remove to select the user accounts. you can choose to automatically send error reports to Microsoft or to your corporate error-reporting server. b. On the Database Engine Configuration page. Click Next 11. and then click Next. and then click Next. and then click Apply to all. do the following: a. In Specify SQL Server administrators. 10. Type the service account and password for each service.

unless you need to specify a collation setting. A dialog box appears. Move a SQL Server 2000 instance or SQL Server 2005 instance to SQL Server 2008 for Windows SBS 2008 migration If you are using an existing SQL Server 2000 or SQL Server 2005 instance with your LOB application and you want to move the instance to SQL Server 2008. • For more information about which collation settings to use.microsoft. See the documentation for your LOB application to verify which collation settings are required. To verify the Windows locale of another computer 1. see the documentation for your LOB application. If SQL Server is in a language that is different from that of the client computers that connect to the database.microsoft. For more information about how to perform this migration. 15. See the documentation for your LOB application to determine the specific configuration settings. 17. 2. On the Ready to Install page. Click Next.to send data about feature usage for SQL Server 2008 to Microsoft.com/fwlink/?LinkId=120782). and then select the name of a specific Windows collation from the list. You can then specify a Sort Order to use with the Collation Designator. You must specify a collation setting if at least one of the following is true: • You are using a line-of-business (LOB) application that depends on settings from a previous version of SQL Server. see “SQL Server Configuration – Collation” on the Microsoft Web site (http://go. • You must match the Windows locale of another computer. and then type Control to open Control Panel. click Start. click Close. click Install. Important When you finish installing Reporting Services. On the Complete page. On the Source Server. Click Next when it becomes available on the Setup Progress page. For more information about SQL Server 2008 Standard Edition for Small Business. you must run the Reporting Services Configuration Manager to fully configure and enable Reporting Services. you must specify a Collation Designator. see the Microsoft Web site (http://go. 16. or you must match the collation settings of another instance of SQL Server. Specify SQL Server collation settings for Windows SBS 2008 migration It is recommended that you use the default settings for installing SQL Server. 50 .com/fwlink/? LinkId=120785). click Run. you must to perform a migration. Double-click Regional Options (also called Regional Settings or Regional and Language Options).

The default setting for the locale of your operating system is in the Collation Settings list box. you must rebuild the databases and reload the data. and then click New Query. In Object Explorer. select Database Engine as the Server type. In the Connect to Server dialog box. you must migrate the TS Licensing role before you decommission the Source Server. 3. To verify collation settings 1. and then click SQL Server Management Studio Express). On the Source Server. 5. Note whether the locale of the Source Server is different from the locale of Destination Server. type sp_helpsort. MoveTerminal Service licensing server for Windows SBS 2008 migration Note This is an optional task. right-click the SQL Server instance. 4. point to Microsoft SQL Server 2005. and then specify the authentication information for the connection. and then click Execute in the toolbar. In the query pane. if you do so. use the table in the "Windows Collation Designators" Help topic to find the corresponding Collation Designator. Many server-to-server activities can fail if the collation settings are not consistent across servers. open the SQL Server Management Studio Express (click Start. You can migrate the TS Licensing role from the Source Server to any of the following: • • • • The Destination Server The second server in the Windows SBS 2008 Premium Edition domain Any additional server in the domain that is running Windows Server 2008 A server in the domain that is running Windows Server 2003 51 . point to All Programs. Although you can change collation settings after you finish migration. 2. To match an earlier version of SQL Server. If the Source Server is running the Terminal Services (TS) Licensing service. select the name of the SQL Server instance for which you want to verify the collation settings. The default collation settings of your server appear in the results pane of the query window. The collation settings must match those of another SQL Server installation. select SQL Collations (used for backward compatibility with previous versions of SQL Server). If it is. To avoid issues later. it is recommended that you verify the necessary selections for Collation Designator and Sort Order with the collation settings for the installation of SQL Server on the Source Server.3.

and then click Terminal Services Configuration. By default.microsoft. see “Locate the Microsoft Clearinghouse Telephone Number for Your Country or Region” at the Microsoft Web site (http://go. ensure that you have your TS CAL purchase agreement documentation available to facilitate reissuing the TS CALs. you must call the Microsoft Clearinghouse. 52 . For more information. The number and type of TS client access licenses (TS CALs) that are installed b. see “Checklist: TS Licensing Installation Prerequisites” at the Microsoft Web site (http://go. When you call the Microsoft Clearinghouse. Because of this. Install the same number and type of TS CALs on the new license server that were installed on the Source Server.com/fwlink/? LinkId=120173). RWW in Windows SBS 2008 does not automatically display the terminal server on your network. Note The instructions for migrating the TS Licensing role are slightly different when you are migrating to Windows Server 2003. see “Activate a Terminal Services License Server” at the Microsoft Web site (http://go. Document the configuration of the TS Licensing role service on the Source Server and the TS licensing environment. The TS CAL purchase agreement documentation 2. You must configure Windows SBS 2008 to display the terminal server in RWW. 5.microsoft.microsoft.com/fwlink/? LinkId=120175). For more information.microsoft. open the Server Management console.com/fwlink/?LinkID=131600). in the navigation pane click Advanced Management. Determine which server that you want to migrate the TS Licensing role to. 4.com/fwlink/? LinkId=120174). For more information. Activate the new license server.microsoft. For more information.Note A terminal server that is running on Windows Server 2008 can communicate only with a license server that is running on Windows Server 2008. 3. How the terminal server discovers (contacts) the licensing server c.com/fwlink/?LinkId=120172). see “Install the TS Licensing Role Service” at the Microsoft Web site (http://go. To do this. For more information. users do not see the terminal server when they connect using RWW. To migrate the TS Licensing role to a server that is running Windows Server 2008 1. including the following information: a. Install the TS Licensing role on the server. Follow the instructions in To migrate the TS Licensing role to Windows Server 2003. On the Source Server. see “To add a Terminal Services server in Application mode to the Select Computer drop-down list in Remote Web Workplace” in the “Advanced Settings” section in Managing Windows Small Business Server 2008 Remote Web Workplace at the Microsoft Web site (http://go.

microsoft. Determine which server that you want to migrate the TS Licensing role to. For more information. the terminal server requests a new TS CAL from the new license server. see “Verify Whether the Terminal Server Can Discover the License Server" in “The terminal server cannot locate the license server” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=62995). For more information. 3. Install the TS Licensing role on the server. For more information. To migrate the TS Licensing role to Windows Server 2003 1. For more information.microsoft. Note A client computer that receives a TS CAL from the previous license server continues to operate as normal until the TS CAL expires. the terminal server requests a new TS CAL from the new license server.6.microsoft. see “Recovering client access licenses on a Terminal Server license server” at the Microsoft Web site 53 . you must call the Microsoft Clearinghouse. see “Locate the Microsoft Clearinghouse telephone number for your country or region” at the Microsoft Web site (http://go. Ensure that the terminal servers in your environment can discover the new license server. For more information.microsoft. When the TS CAL expires. For information about Licensing Diagnosis.com/fwlink/?LinkId=62981). deactivate the previous license server. 2. When the TS CAL expires. ensure that you have your TS CAL purchase agreement documentation available to facilitate reissuing the TS CALs. Note A client computer that receives a TS CAL from the previous license server continues to operate as normal until the TS CAL expires. see “Install Terminal Server Licensing” at the Microsoft Web site (http://go.com/fwlink/? LinkId=62988). When you call the Microsoft Clearinghouse. Ensure that the terminal servers in your environment can discover the new license server. For more information. see the topic "Identify Possible Licensing Problems for the Terminal Server" in the Windows Server 2008 Terminal Services Configuration Help. see “Terminal Server license server roles” at the Microsoft Web site (http://go.com/fwlink/?LinkId=120176). 7. 4. For more information. see “Activate a Terminal Server License Server” at the Microsoft Web site (http://go. To do this.com/fwlink/?LinkId=62994). To see which license servers a terminal server can discover. Activate the new license server. After you confirm that the terminal servers in your environment can discover the new license server. Install the same number and type of TS CALs on the new license server that were installed on the Source Server. 5. use the Licensing Diagnosis in the Terminal Services Configuration tool.microsoft. see “Deactivate a Terminal Server license server” at the Microsoft Web site (http://go.com/fwlink/? LinkId=62991).

overwriting the existing file.xml file. see “Deactivate a Terminal Server license server” at the Microsoft Web site (http://go. paste the RWWConfig. you must manually copy the RWW configuration file to the Destination Server. Migrate Remote Web Workplace configuration file Note This is an optional task. click Licensing Service Discovery in “Windows Server 2003 Terminal Server Licensing” at the Microsoft Web site (http://go.com/fwlink/?LinkId=62996). click Set a preferred license server in “The terminal server cannot locate the license server” at the Microsoft Web site (http://go. On the Destination Server. copy the IWorkerGadgetInfo. 6. Deactivate the previous license server. copy the RWWConfig. To migrate the RWW configuration file to the Destination Server 1. You must copy the gadgets to the Destination Server manually. For more information. If you configured Remote Web Workplace (RWW) on the Source Server. On the Source Server. Migrate Gadgets Note This is an optional task. and you want to use the same configuration on your new server. For more information about the license server discovery process. you must configure the terminal server to use the new license server.xml file. 54 .microsoft. 7.microsoft. On the Source Server. 2. To be discoverable in a domain. a license server must be a domain controller. which is in the %ProgramFiles%\Windows Small Business Server\Bin\ folder. which is in the %ProgramFiles %\Windows Small Business Server\Data folder.microsoft. If you did not install the TS Licensing role on a domain controller.xml file in the %ProgramFiles %\Windows Small Business Server\Data folder.com/fwlink/? LinkId=62998). The Migration Wizard does not include a task for migrating gadgets from the Source Server to the Destination Server.(http://go. For more information. To migrate gadgets to the Destination Server 1.com/fwlink/?LinkId=26220).microsoft.com/fwlink/?LinkId=62995).

Rerun the Connect to the Internet Wizard to reconfigure the DNS entries on the Destination Server network adapter. This removes any references to the Source Server in the DNS entries.2. finish the migration process. click Next. In the navigation bar on the Windows SBS Console. 55 . see the instructions for that task. On the Finish the migration page. To finish the Migration Wizard 1. 6. Continue to step 3. Remove the Source Server from the network. and then follow the instructions in the wizard. If you want to finish the skipped tasks. click Finish the migration. Finish migration Important Although the Migration Wizard does not migrate data for line-of-business (LOB) applications. To finish the skipped tasks. When you restart the wizard. click The source server is no longer a domain controller. click Do not finish the migration yet. you must use the procedures that are provided by your LOB-application provider to migrate the data within the 21-day grace period that you have to complete the migration process and before you decommission the Source Server. click the Network tab. and then click Finish. a. Return to the Finish the migration page. In the Tasks pane. b. If you want to stop the Migration Wizard and return later to finish. and then click Cancel.xml file in the %ProgramFiles%\Windows Small Business Server\Bin\ folder. On the Destination Server. and then click Next. it returns to this page. Important This is required. On the Finish the migration page. On the Migration Wizard Home page. follow the instructions in Demote and remove the Source Server from the network. click Finish Migration. c. and then click Connectivity. click Connect to the Internet. If you want to finish the migration process. overwriting the existing file. you can choose to finish any skipped tasks. paste the IWorkerGadgetInfo. 5. click Skip this task. and then click Next. 2. b. 3. and then click Next. a. or skip the tasks and return to the Migration Wizard later. where you can choose to finish the skipped tasks or finish the migration process. 4.

Clear the Active Directory Certificate Services check box. You can use the following procedure to uninstall an AD CS role service and to retain other AD CS role services. you might experience a problem the first time that you create a user account on the Destination Server. 6. For information about uninstalling Exchange Server 2007. 2. 3. review the information. If you are uninstalling an enterprise CA. membership in Enterprise Admins or its equivalent is the minimum required to complete this procedure. click Administrative Tools. To complete this procedure. Demote and remove the Source Server from the network After you finish installing Windows SBS 2008 and finish the tasks in the Migration Wizard. you must log on with the same permissions as the user who installed the CA. In the Roles Summary section. see the Knowledge Base article “How to Completely Remove Exchange 2007 from a Server” at the Microsoft Web site (http://go. Click Start. 7. On the Confirm Removal Options page. and then create it again. Log on to the Source Server as a domain administrator. 5. In the Remove Roles Wizard.microsoft. and then click Next. Click Continue on the User Account Control dialog box. 56 .com/fwlink/?LinkId=120071). If this occurs. remove the user account that you added. and then click Remove. To remove AD CS 1. 4. click Next. Remove Active Directory Certificate Services The procedure is slightly different if you have multiple Active Directory Certificate Services (AD CS) role services installed on a single server. and then click Server Manager.Note After finishing the migration. click Remove Roles. you must do the following: • • • • • • • Uninstall Exchange Server 2007 Remove Active Directory Certificate Services Physically disconnect printers that are directly connected to the Source Server Demote the Source Server Remove the Source Server from the network Edit the Software Updates Group Policy Object on the Destination Server Repurpose the Source Server Uninstall Exchange Server 2007 You must uninstall Exchange Server 2007 from the Source Server before you demote it.

Physically disconnect printers that are directly connected to the Source Server Before demoting the Source Server. 3. When the Remove Roles Wizard finishes. type gpupdate /force. The process may require you to log off and log on again to finish. right-click Command Prompt. you are told that AD DS will be removed from the computer and that the server will become a member of the domain. click Run. Click Start. To force a Group Policy update on a client computer 1. 3. ensure that Group Policy settings are applied to all client computers. click All Programs. In the Summary dialog box. and then click Run as administrator. Ensure that no Active Directory objects remain for the printers that were directly connected to the Source Server. Click Next twice. and then press ENTER. On the Source Server. physically disconnect any printers that are directly connected to the Source Server and shared through it. To demote the Source Server 1. Demote the Source Server You must demote the Source Server from the role of an AD DS domain controller to the role of a domain member server. At the command prompt. type dcpromo. Important Restart the server even if you are not prompted to do so. Important Both the Source Server and the Destination Server must be connected to the network while the Group Policy changes are updated on the client computers. Important Do not select This server is the last domain controller in the domain. 57 . Click Next. click Accessories. Click Yes to confirm. click Start. 2. Log on the client computer as an administrator. Click OK. 8. 4. and then click OK. you are prompted to stop the service before proceeding. The printers can then be directly connected to the Destination Server and shared from Windows SBS 2008. If you are about to demote and disconnect the Source Server from the network. restart the server to complete the uninstallation process.Note If Internet Information Services (IIS) is running. 2.

click the object that begins with S-1-5. To update the Software Updates GPO 1. In the Security Filtering section. click Continue. expand Domains. click Administrative Tools. 6. and then close Active Directory Users and Computers. and then expand Group Policy Objects. you must remove the Source Server from AD DS on the Destination Server.4. and then click Group Policy Management. Verify that the Source Server is not listed. click Start. Click Finish. This is the Source Server SID. and then expand SBSComputers. 7. This is now an unresolvable security identifier (SID). Click Update Services Server Computers Policy. expand MyBusiness. In the results pane. 3. click Continue. In the Group Policy Management console. 2. Finally. expand the domain name. The Source Server restarts. expand DomainName. click Administrative Tools. and then disconnect it from the network. Click Remove. 2. In the User Account Control window. and then click Active Directory Users and Computers. and you should remove it in the Group Policy Management Console on the Destination Server. and then click OK. and then click Yes. it is still included in the scope for the Update Services Group Policy object (GPO) on the Destination Server. click Start. click the Scope tab. 5. After the Source Server restarts. In the Active Directory Users and Computers navigation pane. 4. Edit the Software Updates Group Policy object on the Destination Server After demoting and removing the Source Server. 58 . expand Forest: DomainName. Remove the Source Server from the network Remove the Source Server from the network and keep it available for at least one week in case some necessary data was not migrated. 4. On the Destination Server. expand Computers. 5. To remove the Source Server from AD DS 1. in the navigation pane. click Delete. 5. 3. On the User Account Control dialog box. On the Destination Server. Right-click the Source Server name if it still exists in the list of servers. make it a member of a workgroup.

Or they are optional configuration steps that you may want to perform. For more information. click Start. You may have disabled some of these settings on your Source Server during the migration process. see "Implementing a Second Server on Your Windows Small Business Server 2008 Network" at the Microsoft Web site (http://go. so they were not migrated to the Destination Server. 4. and then set it up for use as an additional server. expand <DomainName>. click Administrative Tools. and then expand the SBSComputers container. you must move the computer objects into the default OU. 6. If you want to manage computer objects that were natively joined to the domain. 3. To move computer objects to the default OU for Windows Small Business Server 2008 1. Optional post migration tasks The following tasks help you finish setting up your Destination Server with some of the same settings that were on the Source Server.Repurpose the Source Server After you uninstall Exchange Server and demote the Source Server. install a server operating system. and then click Yes in the warning dialog box. click Continue. OU=<DomainName>\MyBusiness\Computers\SBSComputers. and then click Active Directory Users and Computers. In the Users Account Control dialog box. expand the Computers container. In the navigation pane.microsoft. When you finish moving the computer objects. The Windows SBS Console displays Active Directory Domain Service (AD DS) computer objects that are in or nested in the Windows SBS 2008 default Organizational Unit (OU). close Active Directory Users and 59 . 2. If you want to repurpose the Source Server. Drag and drop the computer objects from their current location to the SBSComputers container. and then expand the Computers container or the container where the computer objects are located. it is not in a healthy state. the simplest way is to reformat it.com/fwlink/?LinkId=104875). Expand the MyBusiness container. On the Destination Server. • • • • Move natively joined Active Directory computer objects for Windows SBS 2008 migration Delete DNS entries of the Source Server for Windows SBS 2008 migration Configure Exchange POP3 connectors for Windows SBS 2008 migration Change Exchange Server 2007 mailbox sizes for Windows SBS 2008 migration • Share line-of-business and other application data folders for Windows SBS 2008 migration Move natively joined Active Directory computer objects for Windows SBS 2008 migration This is an optional task. 5.

click Administrative Tools. In the DNS Manager console.Computer. 2. open the Windows SBS Console. Repeat step 5 until all pointers to the Source Server are removed. To configure POP3 Connectors on the Destination Server 1. Click OK to close the Properties window. the DNS server still contains entries that point to the Source Server. click Properties. In the navigation bar. and then click View POP3 Connector properties. On the Destination Server. expand Reverse Lookup Zones. These DNS entries should be deleted. click Start. Verify that all of the computers on your network are displayed. Delete DNS entries of the Source Server for Windows SBS 2008 migration After you decommission the Source Server. expand the server name. and then expand Forward Lookup Zones. 8. Click Add. and then click Connectivity. Open the Windows SBS Console. and then click OK. 8. On the navigation bar. 2. and then add each of the user accounts from the Source Server POP3 60 . 7. On the Destination Server. In the DNS Manager console. 5. 6. and then click DNS. Right-click POP3 Connector. and then click Computers. 7. 4. Right-click the first zone. click the Network tab. 3. 9. Click Continue in the User Account Control dialog box. Repeat steps 4 through 7 to remove all Reverse Lookup Zones that point to the Source Server. To delete DNS entries that point to the Source Server 1. Configure Exchange POP3 connectors for Windows SBS 2008 migration If you had POP3 Connectors on the Source Server. 3. 4. and then click the Name Servers tab. click the Network tab. Click an entry in the Name servers text box that points to the Source Server. you may want to configure them on the Destination Server. click Remove. 9.

3. Change Exchange Server 2007 mailbox sizes for Windows SBS 2008 migration In Windows SBS 2008. Click Continue in the User Account Control dialog box.Connector. 3. On the Destination Server. Share line-of-business and other application data folders for Windows SBS 2008 migration You must set the shared folder permissions and the NTFS permissions for the line-of-business and other application data folders that you copied to the Destination Server. 61 . In the work pane. Click the E-Mail tab. and then click OK. Click the Limits tab. 4. and then click Mailbox. click the Users and Groups tab. In the navigation bar. and then click Users. 6. 5. the mailbox database and the individual mailboxes have a size limit of 2 GB. right-click Mailbox Database. you must update the script to map to the drives on the Destination Server. and then click Exchange Management Console. click Microsoft Exchange Server 2007. specify the mailbox database limits. you must manually change the size limits on the Destination Server To change the size limit of the mailbox database 1. update the maximum mailbox size information. and then click OK. the shared folders are displayed in the Windows SBS Console on the Shared Folders tab. In the result pane. 4. click Start. click All Programs. 5. To change the size limit of the individual mailboxes 1. 2. and then click Properties. 5. If the size limit of the mailbox database or the individual mailboxes on the Source Server is more than 2 GB. On the Destination Server. 2. open the Windows SBS Console. If you are using a logon script to map drives to the shared folders. and then click Edit user account properties. In the Exchange Management Console navigation pane. click the Destination Server name. Repeat steps 3 and 4 until all user accounts are updated. After you set the permissions. Click a user account. Click OK. expand the Server Configuration node.

To download the Windows Small Business Server 2008 Best Practices Analyzer. which are sorted by severity.Run the Windows SBS 2008 Best Practices Analyzer When you finish migrating your settings and data to Windows SBS 2008. that you should review.com/fwlink/?LinkID=129232).com/fwlink/?LinkID=130639). you should run the Windows Small Business Server 2008 Best Practices Analyzer (BPA). and it provides a recommendation about what you should do to resolve the issue. see the Microsoft Web site (http://go. The list describes each issue.microsoft. The recommendations are developed by the product support organization for Windows SBS 2008.microsoft. For more information about the Windows Small Business Server 2008 Best Practices Analyzer. errors. and then it presents a list of issues. 62 . and other information. see “Introducing the Windows Small Business Server 2008 Best Practices Analyzer” at the Microsoft Web site (http://go. The BPA examines a server that is running Windows SBS 2008.