Jump to content
DeployCentral

Migration Stuck/Paused


engmanredbeard
 Share

Recommended Posts

Update:

It's now 12:38p and the USMT.MIG file has finally progressed to the expected value of 3.9GB. The client computer has also progressed to the "cleaning volume 1 of 1" stage. So, does anyone have any input on what caused the delay?

 

Hi,

I've been testing the Deployment and migration parts of SDE on a few computers and one seems to be stuck uploading the backup data. The computer began the deployment process just fine, rebooted into Smart Deploy, and began "migrating user". I watched as the USMT.MIG file on the server climbed to 2.4GB at 11:05am. Now, at 12PM, the file has not increased and the computer has not progressed to the next stage.

 

Is there something I can do to force the machine to progress? Would this introduce a chance of data loss?

Can I restart the machine with no ill effects? If yes, what do I need to delete to re-run the deployment? I assume the server's copy of the MIG as well as the local client copy?

 

There are no log files pertaining to the old or new computer name.

 

Answer file snippet regarding Migration settings is below:

<migration>
        <protected_folder>Backup</protected_folder>
        <virtualization_platform />
        <create_desktop_shortcut>false</create_desktop_shortcut>
        <files_to_exclude />
        <usmt_migration>true</usmt_migration>
        <migrate_user_settings>true</migrate_user_settings>
        <migrate_application_settings>true</migrate_application_settings>
        <migrate_documents>true</migrate_documents>
        <hardlink_migration />
        <network_migration>true</network_migration>
        <hardlink_migration_path />
        <network_migration_path>\\[SERVER_NAME]\c$\_smartdeploybackupspace</network_migration_path>
      </migration>

Link to comment
Share on other sites

Glad to hear it completed the copy. That stage of the deployment is using the normal Windows copy commands. There's no standard time to copy regardless of size since given all the factors that can affect the copy time. 

If there's an error, or it doesn't progress you can cancel to return to the SmartDeploy boot menu, open a command prompt and locate the X:\Windows\Temp\Scanstate.log file. This can shed some light on what's happening. (Alternatively, you can click the Collect Logs button on the SD boot menu and this log will be included in the zip file.)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...