You have two computers named Computer1 and Computer2. Computer1 runs Windows Vista. Computer2 runs Windows 7. Computer1 has a custom application installed. You create a custom XML file named app1.xml that contains the migration settings for the application. You need to migrate the configuration and application data for the custom application from Computer1 to Computer2.
What should you do?
A . On Computer1, run Loadstate.exe /l:app1. On Computer2, run Scanstate.exe /l:app1.xml.
B . On Computer1, run Scanstate.exe /i:app1.xml. On Computer2, run Loadstate.exe /i:app1.xml.
C . On Computer1, run Loadstate.exe /keyfile:app1.xml. On Computer2, run Loadstate.exe /keyfile:app1.xml.
D . On Computer1, run Scanstate.exe /genconfig:app1.xml. On Computer2, run Loadstate.exe /config:app1.xml.
Answer: B
Explanation:
User State Migration Tool
USMT 4.0 is a command-line utility that allows you to automate the process of user profile migration. The USMT is part of the Windows Automated Installation Kit (WAIK) and is a better tool for performing a large number of profile migrations than Windows Easy Transfer. The USMT can write data to a removable USB storage device or a network share but cannot perform a direct side-by-side migration over the network from the source to the destination computer. The USMT does not support user profile migration using the Windows Easy Transfer cable. USMT migration occurs in two phases, exporting profile data from the source computer using ScanState and importing profile data on the destination computer using LoadState.
(include) /i:[Path]FileName
Specifies an .xml file that contains rules that define what user, application or system state to migrate. You can specify this option multiple times to include all of your .xml files (MigApp.xml, MigUser.xml and any custom .xml files that you create). Path can be either a relative or full path. If you do not specify the Path variable, then FileName must be located in the current directory.