THE OFFICIAL BLOG OF THE SBS DIVA

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

Restricted

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

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

RemoteSigned

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.

--Elin

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.

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.

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.

Pete,

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