Select the product you need help with

A migration installation of SBS 2011 Standard May Stop With The Message The Source Server Does Not Meet Minimum Requirements For Migration

Article ID: 2612862 - View products that this article applies to.

SYMPTOMS

A migration installation of SBS 2011 Standard may stop with the following error message:

Collapse this imageExpand this image

Source Server does not meet minimum requirements for migration

The error message appears even though you have successfuly ran the Migration Preparation Tool on the Source Server.

You can press Shift F10 on the SBS 2011 Server and it will open a command prompt. The SBS setup is located at c:\program files\windows small business server\logs

Examine the log to see if it has the following highlighted errors:

4224] 110812.132120.6630: Setup: Getting OS version for SERVER
[4224] 110812.132121.4580: Setup: Caught exception when getting source OS Version: System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.SchemaUpdatePagePresenter.PopulateSourceServerOS(String sourceServer, String username, String password)

[4224] 110812.132125.0703: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObjectSearcher.Initialize()
at System.Management.ManagementObjectSearcher.Get()
at Microsoft.WindowsServerSolutions.Setup.SBSSetup.SchemaUpdatePagePresenter.PopulateSourceServerOS(String sourceServer, String username, String password)

Back to the top | Give Feedback

CAUSE

The setup process makes a WMI connection to the source server to determine the source server operating system. The WMI connection attempt is failing to successfully connect. Usually there is either something misconfigured on the source server or something blocking the WMI connection.

Back to the top | Give Feedback

RESOLUTION

You can use the following steps to help troublehsoot the issue.

1. Verify that DCOM is properly configured on the source server.

a. On the source server, run dcomcnfg
. Expand component servicesc. Expand Computers
d. Right click on My Computer and go to properties
e. Verify that the settings on the Default Properties tab match those in the following screenshot:

Collapse this imageExpand this image

2. Verify that WMI is working on the source server.

a. On the source server, run WBEMTEST

b. Click connect

c. Change the namespace to root\cimv2

d. If it fails to connect you will receive an error popup dialog. If you get an error in the connection you should examine the application event log on the source server and look for WMI related events that can aid in troubleshooting the failure.

3. If WMI connects locally then we need to test remote connectvity to WMI.You can press shift F10 on the SBS 2011 and a command prompt should open. You can use WBEMTEST to test WMI connectivity from the new server to the source server.

a. At the command prompt, type WBEMTEST

b. Click connect

c. In the Namespace field, enter \\soureservername\root\cimv2

(file://soureservername/root/cimv2)

(where soureservername is the name of the source server)

d. In the User Field enter the account name you specified in the SBS Answer File

e. Enter the password for the account in the password Field

Example:

Collapse this imageExpand this image

f. Press the Connect button

g. If it fails to connect, typically you will receive one of two errors:

Collapse this imageExpand this image

If you get either error message, then we need to examine the source server and disable any firewall, antivirus, antispyware programs or anything that could interfere with RPC network connections from the SBS 2011 Server. The first steps would be to use msconfig and disable any start up items and any third party services and then reboot the SBS 2003 Server. After the reboot, use wbemtest on the SBS 2011 server or hit the check again option on the error message to see if the issue is resolved. If you are still getting a failure, there may be a permission problem on the SBS 2003 server. Since the SBS 2003 server is going to be decommissioned once the migration is complete, you can change the startup account for the RPC service on the SBS 2003 server to local system. We do not recommend permanently changing the RPC service logon account on a server that is going to remain in production. If the source server is not SBS 2003, you can temporally change the RPC service to run under the Local System account. Once the SBS 2011 server is completely installed, you can change the service back to network service. If the RPC service runs under the context of the local system account, it can often bypass any security problems on the SBS 2003 server. Use the following steps to change the RPC server to run under the local system account:

a. On the SBS 2003 server open the Services MMC

b. Open the properties of the service named Remote Procedure Call (RPC)

c. Click on the Log On Tab:

d. Change the Log on account to Local System Account and check the box to allow the service to interact with the desktop.

Collapse this imageExpand this image

e. Reboot the SBS 2003 Server

f. Once the SBS 2003 Server reboots, click on the check again box to recheck the connection.

Back to the top | Give Feedback

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Back to the top | Give Feedback