Documentation for SCCM task sequence deployment orchestrator

Migrating EFS files

Choose from the following options to migrate encrypted files. In all cases, by default, USMT fails if an encrypted file is found unless you use one of the following options.

Abort : Causes the process to fail with an error code, if an Encrypting File System (EFS) file is found on the source computer.

Skip : Ignore EFS files.

Decryptcopy : Directs the process to decrypt the file, if possible, before saving it to the migration store, and to fail if the file cannot be decrypted. If the process succeeds, the file will be unencrypted in the migration store, and when you run the restore procedure, the file will be copied to the destination computer.

Copyraw : Directs the process to copy the files in the encrypted format. The files will be inaccessible on the destination computer until the EFS certificates are migrated. EFS certificates will be automatically migrated; so when you run the restore procedure, the encrypted file and the EFS certificate will be automatically migrated.

Hard-link : Set this to True; if during hard-link capture scenarios you’d like Encrypting File System (EFS) files to be hard-linked and not copied.

Suggest Edit

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.