Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
SBS Migration - 2003 to 2011 - Run the Migration Preparation Tool on the Source Server

Answered SBS Migration - 2003 to 2011 - Run the Migration Preparation Tool on the Source Server

  • Saturday, January 28, 2012 10:23 AM
     
     
    Sign In to Vote
    0

    Hi, I have run into another issue whilst attempting to migrate from server 2003 to 2011.

    The SBS 2011 installation advises it does not meet the minimum requirements with error message:

    'SBS Migration - 2003 to 2011 - Run the Migration Preparation Tool on the Source Server'

    When running the migration tool again on the source server - it advises completed. 

    My Log file shows:

    1472] 110514.081040.4566: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

       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)

    [1472] 110514.081043.7708: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

       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)

    [1472] 110514.081047.1220: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

       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)

    [1472] 110514.081050.4842: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

       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)

    [1472] 110514.081053.7994: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

       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)

    [1472] 110514.081056.7996: Setup: Setting source OS to Other

    [1472] 110514.081056.7996: Setup: Running requirement check: MigrationReadyRequirement

    [1472] 110514.081057.1446: Setup: Caught exception: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

       at System.Management.ManagementScope.Initialize()

       at System.Management.ManagementObject.Initialize(Boolean getObject)

       at System.Management.ManagementObject.GetMethodParameters(String methodName, ManagementBaseObject& inParameters, IWbemClassObjectFreeThreaded& inParametersClass, IWbemClassObjectFreeThreaded& outParametersClass)

       at System.Management.ManagementObject.GetMethodParameters(String methodName)

       at Microsoft.WindowsServerSolutions.Setup.SBSSetup.RegistrykeyCheck.DoCheck(SourceServerType sourceType, Boolean isRemote, String domainName, String sourceServerName, String userName, String password)

       at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MigrationRequirement.CheckRequirement(SourceServerType sourceType, Boolean isRemote, String domainName, String sourceServerName, String userName, String password)

     

    I have attempted the fixes:

    RESOLUTION
    To resolve this issue, follow these steps:

    Method 1:

    Make sure DCOM is enabled and is working correctly.

    1.) Launch Component Services (DCOMCNFG) 
    2.) Expand Component Services -> Computers -> My Computer 
    3.) Bring up the Properties dialog box for My Computer 
    4.) Click on Default Properties tab 
    5.) Check the box 'Enable Distributed COM on this computer' 
    6.) Make sure Default Authentication Level is set to 'Connect' and Default Impersonation Level to 'Impersonate' 
    7.) Click Apply, click Ok. 
    8.) Close the Component Services window.

    Make sure the group policy 'Impersonate a client after authentication' has SERVICE account added to the list.

    1.) Launch Local Computer Policy (GPEDIT.msc) 
    2.) Expand Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment 
    3.) Make sure the Group Policy 'Impersonate a client after authentication' has Administrators group and SERVICE account added to the list. 
    4.) Reboot the Source server


    Method 2:

    If the above steps does not fix the issue for you, as a workaround, you can change the Log On type for RPC to Local System. To do this, follow these steps on the source server.

    1.) Open Services console 
    2.) Open the Properties dialog box for Remote Procedure Call (RPC) service. 
    3.) Go to Log On tab 
    4.) Select the radio button for 'Local System Account' 
    5.) Check the box 'Allow service to interact with desktop' 
    6.) Click Apply, click OK. 
    7.) Reboot the Source server

    But to no avail. 

    Is there anything else I should be looking for?

     

All Replies

  • Saturday, January 28, 2012 12:15 PM
     
     
    Sign In to Vote
    0

    According to:

    http://blogs.technet.com/b/sbs/archive/2011/07/08/sbs-2011-standard-migrations-keys-to-success-part-2-the-setup-phase.aspx

    We have:

    F. If you encounter this message during setup: Source Server does not meet the minimum requirements for migration

    Most Common Cause: 

    The new server makes a WMI connection back to the source server to verify that the source tool has been successfully run.  

     

    Resolution Summary:  

    You can use the steps in the following Microsoft Knowledge Base article to troubleshoot the issue:  http://support.microsoft.com/kb/2612862

    I know u have already attempted the fix,but, what about the WMI query [mentioned in KB]....does that work?

     
  • Saturday, January 28, 2012 12:23 PM
     
     
    Sign In to Vote
    0

    Hi, yes, already tried this fix. Rebooted server and still get the above from the logs - and still get the same error messages. 

    I have disabled Symantec Endpoint (as others have found this to be the cause) but still, cannot proceed. 

    Any ideas on this would be greatly appreciated.

     
  • Saturday, January 28, 2012 12:28 PM
     
     
    Sign In to Vote
    0

    not the fix...does the wmi query run successfully as mentioned in the kb?

     

    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  (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:

    WBEMtest


    f. Press the Connect button

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




    • Edited by Jkazama Saturday, January 28, 2012 12:28 PM
    •  
     
  • Saturday, January 28, 2012 1:25 PM
     
     
    Sign In to Vote
    0

    No, it runs without success. 

    The consequent fix, I have run: 

    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.

    Tried WMI again - fails. 

    There is no ISA server - firewall is on the router. I have disabled Symantec Endpoint protection


    • Edited by PIPBOY78 Saturday, January 28, 2012 1:25 PM
    •  
     
  • Saturday, January 28, 2012 11:26 PM
     
     
    Sign In to Vote
    0
    I am now able to perform the above WMI test - but still cannot get through error message. 
     
  • Sunday, January 29, 2012 2:10 AM
     
     
    Sign In to Vote
    0

    And you still get:

    1472] 110514.081040.4566: Setup: Caught exception when getting source OS Version: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

     

    Is WMI running properly on source?
    Can you successfully open wmimgmt.msc->properties?

     
  • Sunday, January 29, 2012 3:43 AM
     
     
    Sign In to Vote
    0

    yes, still getting that same error. 

    I can successfully connect to WMI on the source server. 

    'Successfully connected to: <local computer>'

    I have now rerun the Migration preparation tool and re-installed SBS 2011 - and still have the same error. 

    I have performed all of the proposed fixes. Checked re-checked. 

    Are there instances of SBS 2003 > 2011 migrations that just cannot be performed?

     

     
  • Sunday, January 29, 2012 4:00 AM
     
     
    Sign In to Vote
    0

    I can successfully connect to WMI on the destination server as well. 

    I have checked the info.xml file, it has picked up all the relevant answer file information. 

    I can ping the domain name by DNS name, but still get these errors. 

    I have rechecked, double checked permissions on the domain account, it is member of all the correct groups. 

    One thing I could add is this is a virtual machine that I am migrating the current 2003 SBS install too. 

    This is the error I am getting from the SBSsetup.log

    'Microsoft.WindowsServerSolutions.Setup.SBSSetup.SchemaUpdatePagePresenter.PopulateSourceServerOS(String sourceServer, String username, String password)

    [2620] 110515.014031.6838: 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)'

     
  • Sunday, January 29, 2012 9:34 AM
     
     Answered
    Sign In to Vote
    0

    Oops.....sbs 2003 in Virtual Machine!

    "Are there instances of SBS 2003 > 2011 migrations that just cannot be performed?"....yes more then likely if ur running sbs 2003 in a virtual env.SBS 2003 is not supported in virtual env and is known to cause issues during migration as well.

     

    You can check following thred ,but, I doubt that will help...I think ur stuck due to sbs 203 being virtual

    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/899372b4-1f91-46db-9af2-398a3af7902b/


     
  • Sunday, January 29, 2012 9:45 AM
     
     
    Sign In to Vote
    0
    No sorry, the SBS 2003 box is physical, the server migrating too is virtual. 
     
  • Sunday, January 29, 2012 5:59 PM
     
     
    Sign In to Vote
    1

    Then it should work....Time zones are correct on both?If you press shift+f10 on new box and type timedate.cpl it matches that of source?

     

    It's still failing to get the OS version.You say you can connect to WMI.I assume this also includes a connection using wbemtest fom destination to the source?

    If there is some correction that u have made to get the WMI working,I suggest you restore source from the backup u took before installing sbs 2011,then make the correction and try again.

     
  • Sunday, January 29, 2012 8:12 PM
     
     
    Sign In to Vote
    1

    Unbelievable. The time was out by over a minute. 

    It has gone through. 

    Thankyou very much for your help!!!!!!!!

     
  • Friday, March 09, 2012 1:53 AM
     
     
    Sign In to Vote
    0

    In my case, the server was not resolving the netbios name of the source server.  I had to use Shift +F10 to open a command prompt and then edit the hosts file - then it worked.  I consider this a bug.  

    Another note, some postings out there suggest that you should edit 'Impersonate a client after authentication" in the Domain Controller Group Policy settings.  In my case, this rendered my server nearly inoperable causing my server to hang on "Applying computer settings" for 3 hours after reboot - it messed up SQL, BES, and god knows what else.  Grueling gut wrenching experience to say the least.  

    If you have this problem, check that DCOM is enabled - check the timezone settings (see post above) - then try to ping the source server using netbios name.  If it fails, then what worked for me might work for you.  Here is how I edited the hosts file -

    1. Shift +F10 to open command prompt
    2. Navigate to hosts file in c:\windows\system32\drivers\etc
    3. Rename hosts to hosts.txt.  Command to do this is "ren hosts host.txt".  In my case I first copied the host file to the root of the C drive where I renamed it.  Windows sometimes will give you problems attempting to rename hosts while in the \etc directory.
    4. Open hosts.txt and add an entry for your server.  This is easy.  If you don't know how, look it up.
    5. Rename hosts.txt back to hosts and place it back into the \etc directory.
    6. Ping the netbios name of your server and it should resolve - then should then be able to continue with your migration.
     
  • Thursday, June 28, 2012 6:14 PM
     
     
    Sign In to Vote
    0

    I had the same problem, where the destination server did not recognize that the migration wizard had been run on the source server.

    I had forgot that I had earlier assigned an IP address to the MAC address of the destination server in the router, and that IP address was in use by some other device. I had set the IP address of the destination server correctly using the control panel (on the destination server) to get to this point, but then the router reassigned the IP address and caused the migration to get stuck.

    When the IP address was incorrect, I could not ping anything, including the source server or the router. Once I fixed the IP address the setup proceeded normally.

    Suggestion: If you are having this problem try to ping the source server or router.

    At the command prompt: ping 192.168.1.1