You have two computers named Computer1 and Computer2. Computer1 runs Windows Vista. Computer2 runs Windows 7.

You attempt to migrate the user profiles and data from Computer1 to Computer2 by using User State Migration Tool (USMT) 4.0.

During the migration, you receive the following error message:

“Gather was aborted because of an EFS file.”

You need to ensure that you can successfully migrate the user state from Computer 1 to Computer 2.

What should you do?

A.
Add the /efs:copyraw switch to the Loadstate command.

B.
Add the /efs:copyraw switch to the Scanstate command.

C.
Generate a new Encrypting File System (EFS) certificate on Computer2.

D.
Export the Encrypting File System (EFS) certificate from Computer1 and import the certificate to Computer2.

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 \\fileserver\migration\mystore /i:migapp.xml /i:miguser.xml /o /config:config.xml /encrypt /key:”mykey”

Encrypted File Options

You can use the following options to migrate encrypted files. In all cases, by default, USMT 4.0 fails if an encrypted file is found unless you specify an /efs option. To migrate encrypted files, you must change the default behavior.

EFS certificates will be migrated automatically when migrating to Windows Vista or Windows 7. Therefore, you should specify the /efs:copyraw option with the ScanState command to migrate the encrypted files