So now you are ready to run the migration prep tool

  1. Insert Windows SBS 2011 Standard DVD1 in the DVD drive on the Source Server.
  2. When the Windows SBS 2011 Standard installation wizard starts, click Install the Migration Preparation Tool. Choose the most recent version of the tool to install.

You need Powershell and the MS baseline config analyzer to install first.

  • Installation requires that you first install Microsoft PowerShell 2 0. You can download and install the software from Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0) ( ).
  • Installation requires that you install Microsoft Baseline Configuration Analyzer 2 0. You can download and install the software from Microsoft Baseline Configuration Analyzer 2.0 ( ).

    Put the SBS 2011 dvd in your SBS 2003 box.  What?  Don’t have a DVD drive in there?  No worries you can mount the ISO using magicdisc (a iso mounting software that makes a ‘pretend’ cdrom drive) or copy over the tools folder


    8 Responses to Migration step seven – Installing the migration prep tool

    1. Elin Flashman says:

      I ran through this recently and found that the migration wizard on SBS 2003 from the sbs 2011 RTM CD will fail due to the fact that powershell is set to restricted mode and hence the scripts will fail.

      I worked with MS on this and found the solution:

      PS C:\Documents and Settings\Administrator> Get-ExecutionPolicy
      PS C:\Documents and Settings\Administrator> Set-ExecutionPolicy remotesigned
      PS C:\Documents and Settings\Administrator> Get-ExecutionPolicy

      Also they explained you will need 2-7 GBs of space on the C: drive of 2003 server to avoid issues.

      Finally, for the answer file they recommend:
      While creating the answer file, please make sure that you do the following things:

      1. Uncheck – Get Installation Updates: (Reason: we can always update the server once the installation is done)
      2. Uncheck – Run Unattended: If unchecked, the setup fields will be pre-populated but you must click Next during setup.
      3. Time Zone: Please select the correct Time Zone (This is very critical in AD Replication)
      4. Also make sure that the time on the destination server should be synchronized with the source server.

      Hope this helps someone else going through this process.

    2. bradley says:

      Did you possibly not close the tool but kept it open while you downloaded the powershell update? As the tool does autoset the script level.

    3. Elin Flashman says:

      It is possible that was the issue, although memory does not server me to recall well enough if I had closed the tool or not.

      However I did run the migration tool from scratch afterwards (even after a reboot) and it didn’t correct the issue.

    4. bradley says:

      SBS 2003 or SBS 2008? I did this on SBS 2003 and did not need to do this change?

    5. Elin Flashman says:

      SBS 2003. I believe it doesn’t happen every time or I would have expected you to have this issue too. Just wanted to pass the info on in case anyone else encounters it.

    6. Pete Hagen says:

      On SBS 2003.

      When running the tool the scan fails. The SourceTool.log file shows the following:

      02/10/2011 15:37:01 Task finished successfully
      02/10/2011 15:37:08 Starting health scan using MBCA engine..
      02/10/2011 15:37:08 Health scan: MBCA model has been imported.
      02/10/2011 15:37:08 Health scan: Execution policy is set to remotesigned. THIS LINE SHOULD NOT APPEAR IN THE OFFICIAL BUILD.
      02/10/2011 15:37:08 Health scan: Execution policy is set to remotesigned. THIS LINE SHOULD NOT APPEAR IN THE OFFICIAL BUILD.
      02/10/2011 15:37:08 !Error! BPAEngine: Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.BPAException: Unexpected PSRuntime exception. —> System.Management.Automation.CommandNotFoundException: The term ‘get-mbcamodel’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

      at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandOrigin commandOrigin)

      at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)

      at System.Management.Automation.CommandFactory._CreateCommand(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)

      at System.Management.Automation.Runspaces.Command.CreateCommandProcessor(ExecutionContext executionContext, CommandFactory commandFactory, Boolean addToHistory)

      at System.Management.Automation.Runspaces.LocalPipeline.CreatePipelineProcessor()

      at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()

      at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

      — End of inner exception stack trace —

      at Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.MBCAEngine.Run()

      at Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.BPALauncher.Run()

      02/10/2011 20:11:04 Unexpected errors occurred during BPA scan.

    7. Derek says:


      I’m getting the same error; did you figure this one out?

    8. bradley says:

      Can you uninstall the Powershell and reinstall it?

      I’ve seen some folks say the powershell install didn’t take right.

      Also unisntall/reinstall the MBCA