What should you do?

You have a computer named Computer1 that runs Windows Vista and a computer named Computer2 that runs Windows 7. You plan to migrate all profiles and user files from Computer1 to Computer2. You need to identify how much space is required to complete the migration. What should you do?

You have a computer named Computer1 that runs Windows Vista and a computer named Computer2 that runs Windows 7. You plan to migrate all profiles and user files from Computer1 to Computer2. You need to identify how much space is required to complete the migration. What should you do?

A.
On Computer1 run Loadstate c:store /nocompress

B.
On Computer1 run Scanstate c:store /nocompress /p

C.
On Computer2 run Loadstate computer1store /nocompress

D.
On Computer2 run Scanstate computer1store /nocompress /p

Explanation:
ScanState
You run ScanState on the source computer during the migration. You must run ScanState.exe on computers running Windows Vista and Windows 7 from an administrative command prompt. When running ScanState on a source computer that has Windows XP installed, you need to run it as a user that is a member of the local administrators group.
The following command creates an encrypted store named Mystore on the file share named Migration on the file server named Fileserver that uses the encryption key Mykey:
scanstate fileservermigrationmystore /i:migapp.xml /i:miguser.xml /o /config:config.xml /encrypt /key:”mykey”
Space Estimations for the Migration Store
When the ScanState command runs, it will create an .xml file in the path specified. This .xml file includes improved space estimations for the migration store. The following example shows how to create this .xml file:
Scanstate.exe C:MigrationLocation [additional parameters] /p:”C:MigrationStoreSize.xml”
To preserve the functionality of existing applications or scripts that require the previous behavior of USMT, you can use the /p option, without specifying “pathtoafile”, in USMT 4.0. If you specify only the /p option, the storage space estimations are created in the same manner as with USMT 3.x releases.
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.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


NINO GAMBINI

NINO GAMBINI

Answer is D

MigApp.xml. Specify this file on both command lines to migrate application settings to computers running both Windows XP and Windows Vista. You can modify MigApp.xml.

/i parameter Specifies an .xml file that contains rules that define what state to migrate. You can specify this option multiple times in order to specify all of your .xml files (MigApp.xml, MigSys.xml, MigUser.xml and any custom .xml files that you create). Path can be a relative or full path. If you do not specify Path, then FileName must be located in the current directory.

Miguser.xml – anything specific to user – user profile
Loadstate – you perform loadstate on a computer 2.

Full Posting

Full Posting

My brother recommended I may like this web site. He was totally right. This post truly made my day. You cann’t believe simply how a lot time I had spent for this information! Thank you!|