The appliance captures user states if the Scan User States Offline pre-installation task is assigned to a scripted installation or system image deployment, then loads the captured user states using the Deploy User States post-installation task.
◦ |
On the left navigation pane, choose Deployments > System Images to display the System Images page. Then click a system image name to display the System Image Detail page. |
◦ |
On the left navigation pane, choose Deployments > Scripted Installations to display the Scripted Installation page. Then click a scripted installation name to display the Scripted Installation Detail page. |
◦ |
On the left navigation pane, choose Deployments > Custom Deployments to display the Custom Deployments page. Then click a custom deployment name to display the Custom Deployments Detail page. |
3. |
Under Installation Plan, move the Deploy User States Post-installation Task from the Available Post-installation Tasks column to the Run Post-installation Tasks column. |
4. |
When you scan a device and capture the user states to the appliance, the USMT creates a .mig file, which contains the user states of the device. You can download and copy the .mig file from the appliance to any location on a target device that you want to update with the new user states.
The USMT ScanState utility performs the backup and generates the .mig file. The USMT LoadState utility performs the restore process using the .mig file. Running the LoadState utility in Administrator mode loads the user states to a target device.
1. |
On the left navigation pane, click Library to expand the section, then click User States to display the User States page. |
2. |
3. |
4. |
5. |
a. |
On the target device, create a local store, such as MyUserStates, with a subfolder named USMT, and copy the .mig file to the USMT folder. |
b. |
Use the following command-line options to deploy the user states:
▪ |
Local account: loadstate.exe StorePath /i:miguser.xml /i:migapp.xml /lac /lae |
▪ |
Domain account: loadstate.exe StorePath /i:miguser.xml /i:migapp.xml |
You can upload an existing answer file (Windows) or preseed/kickstart file (Linux), or perform a server-based attended setup (Windows or Linux).
Prepare for a scripted installation:
The Create a Scripted Installation wizard guides you through the steps to define the scripted installation. The settings that you specify in the config.xml file must be compatible with the hardware. Windows only: If the hardware cannot handle the settings, the Windows installer causes the unattended scripted installation to fail.
1. |
On the left navigation pane, click Deployments, then click Scripted Installations to display the Scripted Installations page. |
2. |
NOTE: Scripted installation deployments to UEFI-enabled devices require creating a UEFI partition using the Create UEFI Partitions pre-installation task and booting from a UEFI bootable FAT32 formatted USB flash device. |
Next, using the wizard, upload an existing answer file (Windows) or preseed/kickstart file (Linux), or perform a server-based attended setup (Windows or Linux).
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center