Juste une update, concernant la migration.

Je viens de passer une à une les étapes de préparation du serveur, j' effectuerais la dernier demain soir: Migration Préparation Tool pour SBS2008.

pour rappel, la procédure complète telle que présentée dans les docs officiels Microsoft... je vais bien sur refaire mon backup et ma VM's avant de lancer la dernière étape :)

voila les étapes de ce soir:

Process steps

This Migration Guide includes the following steps:

1. Prepare your Source Server for migration You must ensure that your Source Server and network are ready for migration. This section guides you through backing up the Source Server, evaluating the Source Server system health, installing the most recent service packs and fixes, verifying the network configuration, and raising the functional level of the Microsoft® Active Directory® Domain Services (AD DS) domain and forest. You must also run the Migration Preparation Tool on the Source Server, which updates the AD DS schema, installs an update that extends the time limit for the migration, and configures Exchange Server to support migration.

2. Create a migration answer file An answer file is used by Windows SBS 2008 Setup to automate the installation and to run Setup in migration mode. This section introduces you to the migration answer file and guides you through using the Answer File Tool to create the migration answer file.

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

4. Migrate settings and data to the Destination Server [2003-2008 chm] The Migration Wizard helps you migrate settings and data from the Source Server to Windows SBS 2008. This section explains how to use the Migration Wizard and provides information about the settings and data that you can migrate.

5. 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, the Source Server must be demoted and physically removed from the network. This section explains how to remove the Source Server from the network.

6. Delete the old Folder Redirection Group Policy object This is the final task to re-home the redirected folders to the Destination Server. Perform this task only if you had folder redirection enabled on the Source Server.

7. Optional post-migration tasks After you finish migrating all settings and data to Windows SBS 2008, you may want to map permitted computers to user accounts, enable folder redirection, configure POP3 connectors, or update mailbox quotas on your new server.

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.

1. Back up the Source Server

2. Install the most recent service packs

3. Verify the network configuration

4. Raise the functional level of the Active Directory domain and forest

5. Evaluate the health of the Source Server

6. Optimize Exchange Server mailboxes

7. Run the Migration Preparation Tool

8. Plan to migrate line-of-business applications

Back up the Source Server

Before you begin the migration process, you should back up your Source Server. This helps protect your data from accidental loss if an unrecoverable error occurs during migration.

To back up the Source Server

1. Perform a virus scan of all the drives and files on the Source Server.

2. Perform a full backup of the Source Server. For more information about backing up Windows SBS 2003, see “Backing Up and Restoring Windows Small Business Server 2003” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=27140).

3. Verify that the backup ran successfully. To test the integrity of the backup, select random files from your backup, restore them to an alternate location, and then confirm that the backed-up files are the same as the original files.

Install the most recent service packs

It is highly recommended that you install the latest service packs on the Source Server. Before installing a service pack, back up your server.

To verify that your server is running Service Pack 1 for Windows Small Business Server 2003

1. Start the Registry Editor, and then locate the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinesServer\ServicePackNumber

If the value is 0x00000001, Service Pack 1 (SP1) for Windows SBS 2003 is installed. Close the Registry Editor.

2. If SP1 for Windows SBS 2003 is not installed, install it. You can download it from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=46690).

Important

You must install SP1 for Windows SBS 2003 before you install SP2 for the Windows Server® 2003 operating system, to ensure that the correct version of Microsoft .NET Framework is installed.

To verify that your server is running Service Pack 2 for Windows Server 2003

1. Click Start, right-click My Computer, and then click Properties.

2. The version of Windows SBS 2003 or Windows SBS 2003 R2 is displayed on the General tab, in the System section.

3. If Service Pack 2 is not displayed, you must install SP2 for Windows Server 2003 to avoid problems that may occur during migration. You can download SP2 for Windows Server 2003 from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=98932).

Note

If you experience network-related issues after installing this service pack, search for article 936594 at the Microsoft Web Site (http://go.microsoft.com/fwlink/?LinkId=20167).

Note

To learn more about the best practices and known issues related to SP2 for Windows Server 2003, search for article 939421 at the Microsoft Web Site (http://go.microsoft.com/fwlink/?LinkId=20167).

To verify that your server is running Service Pack 2 for Exchange Server 2003

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

2. In the Server Management navigation pane, expand Advanced Management, expand <DomainName> (Exchange), and then expand Administrative Groups.

Note

If Administrative Groups is not displayed, right-click <DomainName> (Exchange), and then click Properties. On the General tab, select Display administrative groups, and then click OK. You may need to restart the Server Management console to apply the changes.

3. Expand Exchange Administrative Group, expand First administrative group, expand Servers, right-click the server name, and then click Properties. The version is listed on the General tab.

4. If it is not installed, install SP2 for Exchange Server 2003. You can download SP2 for Exchange Server 2003 from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=98933).

Note

Windows SBS 2008 does not directly support migrating Windows SharePoint® Services 3.0 or Windows Server Update Services 3.0 from Windows SBS 2003 to Windows SBS 2008. For information about migrating Windows SharePoint Services 3.0, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=115335).

To verify that your server is running Service Pack 3 for Windows SharePoint Services 2.0

1. Click Start, click Control Panel, and then click Add or Remove Programs.

2. Click Microsoft Windows SharePoint Services 2.0, and then click Click here for support information. If the version number is 11.0.8173.0, SP3 for Windows SharePoint Services 2.0 is installed.

3. If it is not installed, install SP3 for Windows SharePoint Services 2.0. You can download it from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=101615).

4. Verify that the CompanyWeb site is updated correctly, by doing the following:

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

b. On the Central Administration page, click Configure virtual server settings in the Virtual Server Configuration section.

c. On the Virtual Server List page, verify that the version for the CompanyWeb site is 6.0.2.8165

5. If the version number of the CompanyWeb site is not correct, use the Stsadm.exe command-line tool to force an upgrade of the content database and the configuration database. To do this follow these steps:

a. Click Start, click Run, type cmd in the Open box, and then click OK.

b. At the command prompt, type the following lines, pressing ENTER after each line:

cd /d \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin

stsadm -o upgrade -forceupgrade -url http://companyweb

c. Type exit, and then press ENTER to close the Command Prompt window.

To verify that Service Pack 1 for Microsoft Core XML Services (MSXML) 6.0 is installed

1. On the Source Server, verify that MSXML6.dll is version 6.10.1129.0 or higher. MSXML6.dll is in the %SystemDrive%:\Windows\System32 folder.

2. If required, you can download MSXML 6.0 from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=87548).

To verify that .NET Framework 2.0 is installed

1. On the Source Server, click Start, and then click Control Panel.

2. Double-click Add or Remove Programs.

3. Check whether .NET Framework 2.0 is in the list of programs. If it is not, you can download it from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=104397).

To install Service Pack 2 for Microsoft SQL Server Management Studio Express

· Download and install the 32-bit version of Service Pack 2 for Microsoft SQL Server® Management Studio Express (MSSMSE) onto the Source Server. You can download the service pack at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=104395).

· If your Windows SharePoint Services databases have been migrated to SQL Server 2000, you can also use the native SQL Server 2000 Enterprise Manager in Windows SBS 2003 to install the service pack.

Verify the network configuration

Reconfigure your existing network

Before you can migrate your network to Windows SBS 2008, you must install and configure a router on your network, and then you must configure the Source Server to use one network adapter. When you are done, your network will look like Figure 1.

Figure 1. Local area network with broadband connection

To configure the Source Server to use one network adapter

1. Unplug the network adapter from the broadband connection.

Note

For more information, see the "Connect Computers on Your Network" section in "Planning Your Windows Small Business Server 2008 Network" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=104282).

2. Install a router on your network as shown in Figure 1.

Note

For more information about installing a router, see the "Verify Your Router Setup" section in "Planning Your Windows Small Business Server 2008 Network" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=104282).

3. To make sure that the Windows SBS 2008 installation wizard can find the router on your network, ensure that the IP address on the network adapter that is in the router and that connects to your LAN is set to either 192.168.x.1 or 192.168.x.254, where x is a number from 1 to 254. This IP address is the default gateway address for your network.

Note

For information about installing and configuring a router, see the documentation from your router manufacturer.

4. On the Source Server, run the Configure E-mail and Internet Connection Wizard to configure the Source Server for one network adapter, as follows:

a. Click Start, and then click Server Management.

b. In the console pane, click To Do List.

c. In the details pane, click Connect to the Internet.

d. Complete the wizard.

5. If you are using virtual private networking (VPN) on the Source Server, disable it. To disable VPN on the Source Server, run the Remote Access Wizard, as follows:

a. Click Start, and then click Server Management.

b. In the console pane, click Internet and E-mail.

c. In the details pane, click Configure Remote Access.

d. Complete the wizard, making sure that you click Disable remote access on the Remote Access Method page.

The router is the gateway to the Internet. Because of this, either the router must provide a firewall service or you must add a firewall device to help protect your LAN from unauthorized access.

If your router supports the UPnPTM framework, the following are also true:

· The installation wizard automatically configures the Internet connection on Windows SBS 2008.

· The installation wizard configures port-forwarding exceptions on the router.

· After Windows SBS 2008 is installed, the Windows SBS Console collects and displays information about your router on the Networking tab, in Internet Connection.

Using Internet Security and Acceleration Server 2004 during migration

You cannot directly migrate Microsoft Internet Security and Acceleration (ISA) Server 2004 from Windows SBS 2003 Premium Edition to Windows SBS 2008 Premium Edition. However, you can continue to use ISA Server 2004 on Windows SBS 2003 during the migration. Verify that ISA Server 2004 with Service Pack 3 (SP3) is installed and configured before you proceed. You can download ISA Server 2004 with SP3 from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=104551).

After you install and configure ISA Server 2004 with SP3, configure remote procedure call (RPC) filtering.

To configure remote procedure call (RPC) filtering

1. To open ISA Server Management, click Start, point to All Programs, point to Microsoft ISA Server, and then click ISA Server Management.

2. In the ISA Server Management console tree, expand Microsoft Internet Security and Acceleration Server 2004, expand ServerName, and then click Firewall Policy.

3. In the details pane, click the SBS Protected Networks Access Rule.

4. On the Tasks tab, click Edit Selected Rule.

5. On the Protocols tab (for an access rule), click Filtering, and then click Configure RPC protocol.

6. On the Protocol tab, clear the Enforce strict RPC compliance check box, and then click Apply.

Note

When you clear the Enforce strict RPC compliance check box, DCOM traffic and other RPC protocols are allowed.

Note

When you publish an RPC interface where there is a route:network relationship between networks, port overriding is ignored. The publishing rule uses the original IP address or port.

Raise the functional level of the Active Directory domain and forest

When Windows SBS 2003 is installed on a server, the functional level of the AD DS domain and forest is set to Microsoft Windows 2000. In order to finish the migration successfully, you must raise the level of the domain and forest to Windows Server 2003.

Important

If you have domain controllers that are running the Windows NT® 4.0 operating system or earlier, or Windows 2000 Server, you must demote them before you can raise the domain functional level to Windows Server 2003. Also, after you raise the domain functional level to Windows Server 2003, you cannot change it back to Windows 2000 mixed mode or to Windows 2000 native mode

Important

You must be a member of either the Domain Admins group in the domain for which you want to raise functionality or the Enterprise Admins group in Active Directory Domain Services (AD DS), or you must be delegated the appropriate authority. As a security best practice, you should use Run as to perform this procedure.

To raise the functional level of the domain

1. On the Source Server, click Start, point to Administrative Tools, and then click Active Directory Domains and Trust.

2. In the console pane, right-click the domain for which you want to raise the functional level, and then click Raise Domain Functional Level.

Note

The current domain functional level is displayed in Current domain functional level, in the Raise Domain Functional Level dialog box.

3. In Select an available domain functional level, click Windows Server 2003, click Raise, and then click OK in the warning dialog box.

To raise the functional level of the forest

1. On the Source Server, click Start, point to Administrative Tools, and then click Active Directory Domains and Trust.

2. In the console pane, right-click Active Directory Domains and Trusts, and then click Raise Forest Functional Level.

Note

The current forest functional level is displayed in Current forest functional level, in the Raise Forest Functional Level dialog box.

3. In Select an available forest functional level, click Windows Server 2003, click Raise, and then click OK in the warning dialog box.

If you receive a warning about having a Windows 2000 Server domain controller and you want to continue with the migration, you should demote the server that is running Windows 2000 Server to avoid problems during migration.

To demote a domain controller

1. On the server that you want to demote, click Start, click Run, type dcpromo, and then click OK.

2. Click Next twice. Do not select This server is the last domain controller in the domain.

3. In the Summary dialog box, you are informed that Active Directory will be removed from the computer and that the server will become a member of the domain. Click Next.

4. Click Finish.

If you cannot demote a domain controller that is running Windows 2000 Server, you can still migrate to Windows SBS 2008 without raising the domain and forest functional level. However, Group Policy settings are not applied correctly. Later, when you can demote the domain controller that is running Windows 2000 Server, you must restore Windows SBS 2008 to its proper state, by redirecting the CN=Users and the CN=Computers containers to an administrator-specified organizational unit.

To redirect the CN=Users container to an administrator-specified organizational unit

1. Log on to Windows SBS 2008 as a domain administrator in the domain where the "CN=Users" container is redirected.

2. Follow the instructions in the "To raise the functional level of the domain" procedure to raise the functional level of the domain to Windows Server 2003.

3. Open a Command Window, and then change the directory to %SystemRoot%\Windows\System32.

4. Run Redirusr.exe, using the following syntax and replacing Domain and DomainExtension with your domain name and extension:

redirusr OU=SBSUsers,OU=Users,OU=MyBusiness,DC=Domain,DC=DomainExtension

For example:

redirusr OU=SBSUsers,OU=Users,OU=MyBusiness,DC=contoso,DC=local

To redirect CN=Computers container to an administrator-specified organizational unit

1. Log on to Windows SBS 2008 as a domain administrator in the domain where the "CN=computers" container is redirected.

2. Follow the instructions in the "To raise the functional level of the domain" procedure to raise the functional level of the domain to Windows Server 2003.

3. Open a Command Window, and then change the directory to %SystemRoot%\Windows\System32.

4. Run Redircmp.exe, using the following syntax and replacing Domain and DomainExtension with your domain name and extension:

redircmp OU=SBSComputers,OU=Computers,OU=MyBusiness,DC=Domain,DC=DomainExtension

For example:

redircmp OU=SBSComputers,OU=Computers,OU=MyBusiness,DC=contoso,DC=local

For more information about raising the functional level of the AD DS domain and forest, search for article 322692, “How to raise domain and forest functional levels in Windows Server 2003,” at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=119928).

Evaluate the health of the Source Server

If your Source Server is running Windows SBS 2003, you can run the Best Practices Analyzer to verify that there are no issues on your server, network, or domain before you start the migration process. If your Source Server is running Windows Server 2003 Standard Edition, you can use the Windows Support Tools to accomplish this task.

Run the Best Practices Analyzer

Note

Your Source Server must be running Windows SBS 2003 to run the Best Practices Analyzer.

The Best Practices Analyzer collects configuration information from the following sources:

· Active Directory Windows Management Instrumentation (WMI)

· The registry

· The Internet Information Services (IIS) metabase

The Best Practice Analyzer checks the following components of Windows SBS 2003:

· Exchange Server

· Update Services

· Network configuration

· Windows SharePoint Services

· SQL Server

To use the Best Practices Analyzer to analyze your Source Server

1. Download and install the Best Practices Analyzer from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=113752).

2. Click Start, point to All Programs, and then click SBS Best Practices Analyzer Tool.

Note

You should check for updates before you scan the server.

3. In the navigation pane, click Start a scan.

4. In the details pane, type the scan label, and then click Start scanning. The scan label is the name of the scan report, for example “SBS BPA Scan 8Jun2008.”

5. After the scan finishes, click View a report of this Best Practices scan.

After the Best Practices Analyzer collects and analyzes the information, it presents a list of issues, which are sorted by severity. For each issue, the Analyzer describes the issue that it encountered and it suggests solutions. You can view any of the following three report types:

Report Type

Description

List Reports

Displays reports in a one-dimensional list.

Tree Reports

Displays reports in a hierarchical list.

Other Reports

Displays reports such as a Run-Time Log.

To view the description and the solutions for the issue, click the issue in the report. Not all of the issues reported by the Best Practices Analyzer affect the migration, but you should solve as many as of the issues as possible to ensure that the migration is successful.

Run the Windows Support Tools

If your server is running Windows Server 2003 Standard Edition, you cannot use the Best Practices Analyzer, but you can use the Windows Support Tools to accomplish the same task. The following table lists the tools that you can use to diagnose issues on your server, network, and domain:

Tool

Description

Netdiag.exe

Helps isolate networking and connectivity issues.

Dcdiag.exe

Analyzes the state of domain controllers in a forest or enterprise, and reports issues to assist you in troubleshooting.

Repadmin.exe

Assists you in diagnosing replication issues between domain controllers.

You should correct all the issues that these tools report before you proceed with the migration.

Optimize Exchange Server mailboxes

It can take a long time to migrate large Exchange Server mailboxes. It will take less time if you reduce the size of the mailboxes before the migration. To help reduce the size of the mailboxes, ask each of the users to do the following:

· Empty the Deleted Items folder

· Archive older mail

To empty the Deleted Items folder

1. In the Microsoft Office Outlook® messaging client, click Tools in the toolbar, and then click Empty "Deleted Items" Folder.

2. Click Yes on the warning dialog box.

To archive older mail

1. In Outlook, click File in the toolbar, and then click Archive.

2. In the Archive dialog box, click the down arrow in the Archive items older than text box.

Note

You must tell the users what date to select in the calendar that appears.

3. If you want to make sure that all the older mail is included, select the Include items with "do not AutoArchive" checked check box.

4. Click Archive all folders according to the AutoArchive settings at the top of the dialog box.

5. Click OK.

In Windows XP, the older mail is moved to the archive.pst file in C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Outlook folder.

In the Windows Vista® operating system, the older mail is moved to the archive.pst file in C:\Users\<user name>\AppData\Local\Microsoft\Outlook folder.

Synchronize the Source Server time with an external time source

The time on the Source Server must be within 5 minutes of the time on the Destination Server, and the date and time zone must be the same on both servers. If the Source Server is running in a virtual machine, the date, time, and time zone on the host server must match that of the Source Server and the Destination Server. To help ensure that Windows SBS 2008 is installed successfully, you must synchronize the Source Server time to the Network Time Protocol (NTP) server on the Internet.

To synchronize the Source Server time with the NTP server

1. Log on to the Source Server with a domain administrator account and password.

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

3. At the command prompt, type w32tm /config /syncfromflags:domhier /reliable:no /update, and then press ENTER.

4. At the command prompt, type net stop w32time, and then press ENTER.

5. At the command prompt, type net start w32time, and then press ENTER.

Important

During the Windows SBS 2008 installation, you have an opportunity to verify the time on the Destination Server and change it, if necessary. Ensure that the time is within 5 minutes of the time on the Source Server. When the installation finishes, the Destination Server synchronizes with the NTP. All domain joined computers, including the Source Server, synchronize to the Destination Server, which assumes the role of the primary domain controller (PDC) emulator master.

Bonne nuit à tous, et, à demain!

Pierre JOUBERT.