Application Command-Line Parameters

Introduction

This chapter describes the command-line parameters supported by Migration Manager. Using these command-line parameters it’s possible to fully automate Migration Manager. Do note, however, that an administrator will need to run Migration Manager at least once in order to define the configuration that should be used by Migration Manager.

You need at least one configuration file, but it’s also possible to have multiple configuration files to accommodate different needs for different sets of users, see the CONFIG parameter for information on how to define which configuration file to use for an operation.

When running Migration Manager from the command-line, it’s highly recommended that you use start /w to run the application since it ensures Windows will wait for Migration Manager to complete the operation before executing the next command.

Basic Command-Line Parameters

The basic command-line parameters are used to control basic Migration Manager operations and include:

  • AutoBackup – perform user state backup
  • AutoExtract – extract user state
  • AutoInject – inject user state
  • Config – specify the configuration file to use for an operation
  • Datastore – specify where user state data is located
  • PersonalityPath – specify an explicit path for where personality is stored
  • PersonalityNaming - specify naming personality folder based on computername or macid
  • Excludedisks – exclude disks when injecting data
  • Password – specify a password for AES256 encryption during an operation
  • Source – specify the name of the computer the data was extracted from, or MAC address when data was extracted from offline Windows
  • Overwrite - will overwrite an existing personality in the datastore during extraction instead of the creating an additional personality if one already exists for the specified personality name (typically the source computer name)
  • MostRecent - If more than one matching personality exists during injection, the most recent personality will be used instead of returning an exit code
  • MappingFile – define the source computer for automated zero-touch migrations

AUTOBACKUP

Syntax:   /AUTOBACKUP

Extraction use:   Backs up changes made to user state after an initial extraction has been performed for the user in question (note that a full extraction must be performed for a user before a backup can be performed).

If the personality to backup isn’t specified on the command-line, Migration Manager scans the user state data store location for an existing extraction for a computer with the same name where the backup is taking place.

If no matching user state can be found or if more than one match is found, Migration Manager exits with an appropriate exit code.

Note that you can only perform a backup on the same system where the original extraction took place. Backup is not supported from offline Windows systems.

Injection use:   N/A.

Must be used with:   N/A. ​
Cannot be used with:   AUTOEXTRACT, AUTOINJECT.

Example:   START /w MigrationManager.EXE /autobackup

AUTOEXTRACT

Syntax:   /AUTOEXTRACT

Extraction use:   The /AUTOEXTRACT command, if used without another supported extraction command switch will automatically perform a personality extraction of the user that is currently logged on to the computer.

Note that the default Migration Manager configuration will be used if a configuration file is not specified in the command-line (using the CONFIG command).

Administrators will have to configure Migration Manager with the desired settings, by selecting content and preferences within the Migration Manager User Interface and saving the configuration. See the "Migration Manager User's Guide" section on "Configuring Migration Manager" for details on creating and saving the configuration. To extract users other than the default currently logged in user, refer to User-Related Command-Line Parameters.

Injection use:   N/A.

Must be used with:   Can be used by itself, but typically at least the CONFIG switch is used as well.

Cannot be used with:   AUTOINJECT, AUTOBACKUP, SOURCE.

Example:   START /w MigrationManager.EXE /autoextract

AUTOINJECT

Syntax:   /AUTOINJECT

Extraction use:   N/A.

Injection use:   If this command is used without another supported injection command, the switch will automatically perform a personality injection for the user that is currently logged on to the computer.

Migration Manager searches the default data store for personalities with a user name that matches the user name of the currently logged on user. If only one matching personality containing that username is found the personality for that user is injected.

If more than one matching personality is found, or no matching personalities are found, Migration Manager will terminate and return an exit code.

Injection to offline Windows is not currently supported.

Must be used with:   Can be used by itself, but typically at least the CONFIG and SOURCE switches are used as well.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT.

Example:   START /w MigrationManager.EXE /autoinject /source MYCOMPUTER /allusers

CONFIG

Syntax:   /CONFIG <fully qualified path to configuration file>

Extraction use:   Specifies the configuration file to use when performing an automatic extraction or injection.

If the specified path to the configuration file is invalid Migration Manager will terminate and return an exit code.

Injection use:   Loading a configuration file during injection does NOT specify what content or specific application/windows settings are to be injected. All items that are extracted and present in the personality will be injected.

Must be used with:   Can be used by itself, but typically used with AUTOBACKUP, AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   N/A. ​ Example:   START /w MigrationManager.EXE /autoextract /config "\\MyServer\MigrationManager\configuration.xml"

DATASTORE

Syntax:   /DATASTORE <fully qualified path to data store>

Extraction use:   Specifies the location of where user state data from the extraction should be stored. This command overrides the data store information in the configuration file.

If the directory specified in the path doesn’t exist it will be created. If the creation fails, Migration Manager will terminate and return an appropriate exit code.

Note: By design, Migration Manager does not extract any files from any folder below the specified data store location. Please take this into account if you place the data store on a local drive.

Injection use:   Specifies the location where user state data can be found. This command overrides the data store information in the configuration file.

If the directory specified in the path doesn’t exist, Migration Manager will terminate with an appropriate exit code.

Must be used with:   AUTOBACKUP, AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   PERSONALITYPATH.

Example:   START /w MigrationManager.EXE /autoextract /datastore \\MyServer\MigrationManager\datastore

PERSONALITYNAMING

Syntax:   /PERSONALITYNAMING: <DEFAULT | MACID | COMPUTERNAME>

Extraction use:   Specifies the naming of the personality folder within the datastore. The default personality naming is computername when extracting from Windows, and MACID when extracting offline Windows using Windows PE.

This command overrides the personality naming information in the configuration file.

Injection use:   N/A.

Must be used with:   AUTOEXTRACT.

Cannot be used with:   AUTOINJECT, AUTOBACKUP, PERSONALITYPATH.

Example:   START /w MigrationManager.EXE /autoextract /PersonalityNaming:MACID

PERSONALITYPATH

Syntax:   /PERSONALITYPATH <fully qualified path to personality location>

Extraction use:   Specifies the fully qualified path of the directory where the extracted user state data should be stored. Unlike the DATASTORE parameter which defines the path of a directory where a unique directory for the user state data should be created, this parameter defines the complete path for the user state data.

If the directory specified in the path doesn’t exist it will be created. If the creation fails, Migration Manager will terminate and return an appropriate exit code.

If the specified directory already contains user state data, Migration Manager will terminate and return an appropriate exit code.

Injection use:   Specifies the fully qualified path of the directory where user state data to inject is located.

If the directory specified in the path doesn’t exist or doesn’t contain user state data, Migration Manager will terminate with an appropriate exit code.

Must be used with:   AUTOBACKUP, AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   DATASTORE, SOURCE.

Example:   START /w MigrationManager.EXE /autoextract /personalitypath \\MyServer\MigrationManager\datastore\%USERNAME%

Note
This parameter is for advanced scenarios only and should only be used when you need complete control over the entire directory path of where user state data is located for a particular user or system.

EXCLUDEDISKS

Syntax:   /EXCLUDEDISKS <drive letter>[;<drive letter>]

Extraction use:   N/A.

Injection use:   Specifies drive letters that Migration Manager shouldn’t inject data to. Files originally extracted from the designated drives will instead be placed in the directory C:\MIGRATED_<drive letter>_DRIVE. ​
In the example below, files originally extracted from the E drive would be placed in the directory C:\MIGRATED_E_DRIVE on injection.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT.

Example:   START /w MigrationManager.EXE /autoinject /EXCLUDEDISKS D;E

PASSWORD

Syntax:   /PASSWORD <password>

Extraction use:   Assigns a password with AES256 encryption to the extracted user state data during extraction. This password must be specified for any subsequent backup or injection.

The specified password must be 7 to 15 characters in length and is case sensitive.

Injection use:   When used for injection and the password is either missing or incorrect Migration Manager will terminate and return an appropriate exit code.

Injections will only occur if the specified password matches the password defined at the time of the original extraction.

Must be used with:   AUTOBACKUP, AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   N/A.

Example:   START /w MigrationManager.EXE /autoextract /PASSWORD password

SOURCE

Syntax:   /SOURCE <computer name | MAC address from offline Windows or :MACID for MAC address of current machine>

Extraction use:   N/A.

Injection use:   Specifies the name of the computer associated with the extracted user state data. If the extracted user state is from an offline Windows system, the MAC address is used instead of the computer name.

This command is typically used in combination with the ALLUSERS command-line switch and only on Injection. When used in conjunction with the ALLUSERS switch, all the users associated with the personality that matches the specified computer name following the SOURCE command will automatically inject.

If there are no matching personalities or if there is more than one matching personality then Migration Manager will by default terminate and return an appropriate exit code. When there are multiple matching personalities, MOSTRECENT can be used to inject the most recent matching personality.

Note that the computer name is defined as just the unique computer name (i.e. MYCOMPUTER as opposed to a fully qualified DNS name like MYCOMPUTER.MYDOMAIN.LOCAL).

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT.

Example:   START /w MigrationManager.EXE /autoinject /SOURCE MYCOMPUTER /ALLUSERS

OVERWRITE

Syntax:   /OVERWRITE

Extraction use:   Overwrites an existing personality folder in the datastore during extraction. The default personality folder name create by Migration Manager uses the source computername. If multiple extractions are performed from the same source computer, multiple folders will be created using that computername. Using /OVERWRITE will instead overwrite the existing computername folder.

NOTE
The personality will be overwritten regardless if the previous extraction included the same users.

Injection use: N/A.

Must be used with:   AUTOEXTRACT.

Cannot be used with:   AUTOBACKUP, AUTOINJECT.

Example:   START /w MigrationManager.EXE /autoextract /ALLUSERS /OVERWRITE

MOSTRECENT

Syntax:   /MOSTRECENT

Extraction use:   N/A.

Injection use: Specifies injecting the most recent matching personality (as determined by autoinject, includeuser, and source) when multiple matching personalities exist. The default behavior without mostrecent is for Migration manager to terminate and return an exit code that multiple matching personalities exist.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT.

Example:   START /w MigrationManager.EXE /autoinject /SOURCE MYCOMPUTER /ALLUSERS /MOSTRECENT

MAPPINGFILE

Syntax:   /MAPPINGFILE <mapping file path>

Extraction use:   N/A.

Injection use:   Specifies the path of a mapping file that defines the mappings between source and target computers to enable fully automatic, zero-touch, migrations.

This command is typically used in combination with the ALLUSERS command-line switch and only on Injection. When used in conjunction with the ALLUSERS switch, all the users associated with the personality that matches the source computer defined in the mapping file will automatically inject.

If there are no matching personalities or if there is more than one matching personality then Migration Manager will terminate and return an appropriate exit code.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT, SOURCE.

Example:   START /w MigrationManager.EXE /autoinject /mappingfile mappings.m7map /ALLUSERS

Note
See Injection Mapping Files for more information on how to create Mapping Files.

The user-related command-line parameters are used to define which users to include or exclude for an operation:

ALLUSERS

Syntax:   /ALLUSERS

Extraction use:   Extracts all existing user profiles on the computer.

It is strongly recommended that you exclude the local administrator account when using this command to avoid accidentally injecting that account on the target system.

Injection use:   Injects all users in a specified personality. The personality can be specified using the SOURCE command.

Must be used with:   AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoextract /ALLUSERS /EXCLUDEUSER %COMPUTERNAME%\Administrator

START /w MigrationManager.EXE /autoinject /SOURCE MYCOMPUTER /ALLUSERS

DOMAIN

Syntax:   /DOMAIN <source domain name>:<target domain name> [<source domain name>:<target domain name>]

Extraction use:   N/A.

Injection use:   Redirects users from a source domain to a different target domain.

This command is typically used in conjunction with the ALLUSERS when users are being moved from one domain to another.

Note: Domain names containing spaces must be enclosed in quotes.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT, INCLUDEUSER.

Example:   START /w MigrationManager.EXE /autoinject /SOURCE MYCOMPUTER /ALLUSERS /DOMAIN "MYDOMAIN:SOME DOMAIN"

Note
Migration Manager does not create domain user accounts. When migrating users between domains using the /DOMAIN command the user’s account must already exist in the target domain otherwise the injection will fail.

EXCLUDEDOMAIN

Syntax:   /EXCLUDEDOMAIN <domain name>

Extraction use:   Prevents user profiles from the specified domain from being extracted.

Injection use:   Prevents user state data belonging to users from the specified domain from being injected.

Must be used with:   ALLUSERS and one of AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoextract /allusers /EXCLUDEDOMAIN MYDOMAIN

START /w MigrationManager.EXE /autoinject /source MYCOMPUTER /allusers /EXCLUDEDOMAIN MYDOMAIN

EXCLUDELOCAL

Syntax:   /EXCLUDELOCAL

Extraction use:   Excludes all local users from being extracted.

This command is most commonly used in conjunction with the /ALLUSERS command.

If by using this switch it results in no personalities being extracted, Migration Manager will terminate and return an exit code.

Injection use:   Excludes local users from being injected.

This command is most commonly used in conjunction with the /ALLUSERS command.

If by using this switch it results in no personalities being injected, Migration Manager will terminate and return an exit code.

Must be used with:   ALLUSERS and one of AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoextract /ALLUSERS /EXCLUDELOCAL

START /w MigrationManager.EXE /autoinject /SOURCE MYCOMPUTER /ALLUSERS /EXCLUDELOCAL

EXCLUDENOTLOGGEDIN

Syntax:   /EXCLUDENOTLOGGEDIN <days>

Extraction use:   Excludes all users that have not logged in within the specified number of days from being extracted.

This command is most commonly used in conjunction with the /ALLUSERS command.

If by using this switch it results in no personalities being extracted, Migration Manager will terminate and return an exit code.

Injection use:   N/A.

Must be used with:   AUTOEXTRACT and one of ALLUSERS or INCLUDEUSER.

Cannot be used with:   AUTOBACKUP, AUTOINJECT.

Example:   START /w MigrationManager.EXE /autoextract /ALLUSERS /EXCLUDENOTLOGGEDIN 90

EXCLUDEUSER

Syntax:   /EXCLUDEUSER <domain name\user name> [<domain name>\<user name>]

Extraction use:   Allows you to exclude specified users from being extracted.

This command is most commonly used in conjunction with the ALLUSERS command.

If by using this switch it results in no personalities being extracted, Migration Manager will terminate and return an exit code.

Injection use:   Allows you to exclude specified users from being injected.

This command is most commonly used in conjunction with the ALLUSERS command.

If by using this switch it results in no personalities being injected, Migration Manager will terminate and return an exit code.

Must be used with:   ALLUSERS and one of AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoextract /ALLUSERS /EXCLUDEUSER MYDOMAIN\User1

START /w MigrationManager.EXE /autoinject /Source MYCOMPUTER /ALLUSERS /EXCLUDEUSER MYDOMAIN\User1

INCLUDEUSER

Syntax:   /INCLUDEUSER <domain name>\<user name> [<domain name>\<user name>]

/INCLUDEUSER <domain name>\<user name>[:<target domain name>\<target user name>]
<domain name>\<user name>[:<target domain name>\<target user name>]]

Extraction use:   The /INCLUDEUSER command extracts the personalities for each user that is specified following the command.

In domain environments, user names must be specified with the domain name in the form <DOMAIN>\<USER>.

If there are no usernames that match the users specified in the command-line then Migration Manager will terminate and return the appropriate exit code.

If at least one user specified matches a username on the computer where the extraction operation is being performed, but one or more other specified users don’t match any usernames on the computer, the extraction process will continue and extract the user state for the users that matched and the operation log that gets created following the operation displays the users that were not extracted.

Note: Usernames and Domain names with spaces must be contained in quotes when specified following the /INCLUDEUSER command.

Injection use:   This parameter is used to specify which users should be injected.

In domain environments, user names must be specified with the domain name in the form <DOMAIN>\<USER>. ​
It’s also possible to remap users using this command. The most common case for this is when users are being moved from one domain to another. To do this, specify the user names as <SOURCE DOMAIN>\<SOURCE USER>:<TARGET DOMAIN>\<TARGET USER>.

Migration Manager will only inject the matching users if all specified users exist within a single personality. Using the SOURCE command allows you to further limit the scope of possible personalities when comparing usernames.

If all users specified with INCLUDEUSER exists in more than one personality, Migration Manager will terminate and return the appropriate exit code.

Note: Usernames and Domain names with spaces must be contained in quotes when specified following the INCLUDEUSER command.

Must be used with:   AUTOEXTRACT, AUTOINJECT.

Cannot be used with:   ALLUSERS , AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoextract /INCLUDEUSER MYDOMAIN\User1 MYDOMAIN\User2

START /w MigrationManager.EXE /autoextract /INCLUDEUSER "SOME DOMAIN\User A" "SOME DOMAIN\User B"

START /w MigrationManager.EXE /autoinject /SOURCE MYCOMPUTER /INCLUDEUSER MYDOMAIN\User1 MYDOMAIN\User2

START /w MigrationManager.EXE /autoinject /SOURCE computername /INCLUDEUSER "MYDOMAIN\User1:SOME DOMAIN\User A"
"MYDOMAIN\User2:SOME DOMAIN\User B"

Note
Migration Manager does not create domain user accounts. When migrating a user between domains using the /INCLUDEUSER command the user’s account must already exist in the target domain otherwise the injection will fail.

INJECTTOLOGGEDINUSER

Syntax:   /INJECTTOLOGGEDINUSER

Extraction use:   N/A.

Injection use:   Forces data to be injected to the user that’s interactively logged on to the computer regardless of which user the data was extracted for.

Note: There are very few scenarios where this command is required, in most scenarios the INCLUDEUSER command will work better and also doesn’t require that a user is interactively logged on to the computer.

Note: There must be only a single user in the user state data being injected.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoinject /source MYCOMPUTER /INJECTTOLOGGEDINUSER

LOCALPROFILE

Syntax:   /LOCALPROFILE

Extraction use:   N/A.

Injection use:   The /LOCALPROFILE command-line argument is used to specify that profiles will be local on the injection system. Use this argument if roaming profiles were used on the extraction system, but roaming profiles will not be used on the injection system.

Note: You will need to configure Active Directory to stop using roaming profiles after the extraction and before the injection.

Do not use this argument if roaming profiles were used on the extraction system, and roaming profiles will continue to be used on the injection system.

If the profile being injected was not a roaming profile, this parameter has no effect.

If folders were redirected on the extraction system, they will continue to be redirected on the injection system. To change the location of the redirected folders, see /REDIRECTFOLDERS.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOEXTRACT, AUTOBACKUP.

Example:   START /w MigrationManager.EXE /autoinject /source MYCOMPUTER /LOCALPROFILE

REDIRECTFOLDERS

Syntax:   /REDIRECTFOLDERS <UNC path for root of redirect folders>
Extraction use:   N/A.

Injection use:   The /REDIRECTFOLDERS command-line argument is used to specify a remote path for redirected folders in three scenarios:

  1. You are injecting to users whose user or domain names differ from the extracted users, and you want the injection users' folders to be redirected
  2. You are injecting to the same user and domain names you extracted, and the extraction system was not using redirected folders but you want to start using folder redirection on the injection system
  3. You are injecting to the same user and domain names you extracted, and the extraction system used a different path for redirected folders. Use this argument if you want the injection system to use a different path for redirected folders than the extraction system.

Note: In either case, you will still need to configure Active Directory to use the redirected folders at the new location you specify.

If you are using folder redirection on the extraction system and are injecting to the same user and domain names, and you want to use the same path for redirected folders on the injection system, do not use this argument. By default, the same path used for folder redirection on the extraction system will be used on the injection system.

If the specified path to the redirected folders is invalid, Migration Manager will terminate and return an appropriate error code.

Redirected folders will be created at the supplied path, if they do not already exist, in the form \\MyServer\Users\<user name>\My Documents, for example. The files extracted from shell folders on the extraction system will be injected at that path.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT.

Example:   START /w MigrationManager.EXE /autoinject /allusers /REDIRECTFOLDERS \\MyServer\Users

ROAMINGPROFILES

Syntax:   /ROAMINGPROFILES <UNC path for root of roaming profiles>

Extraction use:   N/A.

Injection use:   The /ROAMINGPROFILES command-line argument is used to specify a remote path for roaming profiles when you are injecting to users whose roaming profiles' server share location differs from the extracted users.

If the extracted users are using roaming profiles and you are injecting to users whose profiles are located on the same server as the extracted users there is no need to use this parameter.

Note: You will need to configure Active Directory to use roaming profiles at the new location for the users you specify.

If the extracted users are not using roaming profiles this parameter has no effect.

Roaming profiles will be created at the supplied path, if they do not already exist, in the form \\MyServer\Users\<user name>, for example. The files extracted from roaming profile locations on the source system will be injected to this path. Active Directory needs to be configured to be consistent with this naming convention.

Note: A .V# suffix (such as .V2) is added to the root roaming profile folder for injections on Windows Vista and later.

Must be used with:   AUTOINJECT.

Cannot be used with:   AUTOBACKUP, AUTOEXTRACT.

Example:   START /w MigrationManager.EXE /autoinject /allusers /ROAMINGPROFILES \\MyServer\Users

Advanced Command-Line Parameters

The advanced command-line parameters control behavior that aren’t always used in the most common use cases but handle scenarios that come up from time to time:

  • DisplayErrorCode – display any errors at the end of the operation
  • ElevatedCredentials – Enables embedded Local Administrator passwords
  • HideStatus – don’t display the progress dialog during the operation
  • Import – import file and/or registry rules before an extraction
  • NoCancel – don’t display the cancel button in the progress dialog

DISPLAYERRORCODE

Syntax:   /DISPLAYERRORCODE

Extraction use:   Causes a dialog describing any errors encountered during the extraction after the extraction completes.

If the extraction completes without errors, no dialog is displayed.

Note: This command should only be used if Migration Manager will be run when a user is interactively logged on to the computer. For fully automated scenarios, it’s preferable to check the exit code from Migration Manager and if an error is indicated check the generated log file instead.

Injection use:   Causes a dialog describing any errors encountered during the injection after the injection completes.

If the injection completes without errors, no dialog is displayed.

Note: This command should only be used if Migration Manager will be run when a user is interactively logged on to the computer. For fully automated scenarios, it’s preferable to check the exit code from Migration Manager and if an error is indicated check the generated log file instead.

Must be used with:   AUTOBACKUP, AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   N/A.

Example:   START /w MigrationManager.EXE /autoextract /allusers /DISPLAYERRORCODE

ELEVATEDCREDENTIALS

Syntax:   MigrationManager.EXE /ELEVATEDCREDENTIALS <username> <domainname> <password>

NOTE
This command works with MigrationManager.EXE, and Not with SE.EXE

Extraction use:   Enables migration of users not logged in without giving users Local Administrator rights.

Injection use:   Enables injection on systems without elevating other Local or domain users.

Must be used with:   MigrationManager.EXE and can replace all SE.EXE command line usage.

Cannot be used with:   SE.EXE

Example:   MigrationManager.EXE /ELEVATEDCREDENTIALS JOEADMIN CORPDOMAIN 1234567

This creates the encrypted file "SE.dat" which contains the login credentials.

Migration technician runs Migration Manager MigrationManager.exe /autoextract

MigrationManager.exe will read the "SE.dat" file and launch SE.exe as the specified user with elevated credentials. The expectation is that the migration technician will interact solely via batch script.

This means that: If the SE.dat file is present, MigrationManager.exe requires that it be used with the /AUTOEXTRACT, /AUTOINJECT or /AUTOBACKUP options present. Otherwise, it will not proceed.

No error message will be displayed to the user in the case that MigrationManager.exe (itself, as opposed to SE.exe) encounters an error. In order to detect whether an error has occurred, and which error, the script will need to utilize %ERRORLEVEL%

Note: A side effect of running MigrationManager.exe this way is that the machine will have a password protected account created for the domain admin user specified.

HIDESTATUS

Syntax:   /HIDESTATUS

Extraction use:   Hides the progress dialog during an extraction.

See also the related NOCANCEL command.

Injection use:   Hides the progress dialog during an injection.

See also the related NOCANCEL command.

Must be used with:   AUTOBACKUP, AUTOEXTRACT or AUTOINJECT.

Cannot be used with:   N/A.

Example:   START /w MigrationManager.EXE /autoextract /allusers /HIDESTATUS

IMPORT

Syntax:   /IMPORT <fully qualified path to rule file>

Extraction use:   This command imports a predefined list of file and/or registry rules via the AUTOEXTRACT command-line.

The XML file that contains the rules uses the same format as the rules that are created and exported using the Migration Manager rule export command.

Injection use:   N/A.

Must be used with:   AUTOEXTRACT.

Cannot be used with:   AUTOBACKUP, AUTOINJECT.

Example:   START /w MigrationManager.EXE /autoextract /import \\MyServer\MigrationManager\rules.xml

NOCANCEL

Syntax:   /NOCANCEL

Extraction use:   Hides the Cancel button in the progress dialog during an extraction. See also the related HIDESTATUS.

Injection use:   N/A.

Must be used with:   AUTOBACKUP, AUTOEXTRACT.

Cannot be used with:   AUTOINJECT.

Example:   START /w MigrationManager.EXE /autoextract /allusers /NOCANCEL