Operators of Tranxition Migration Manager can avoid elevating user permissions during migration. The process works by embedding an encrypted password in the Migration Manager configuration. When the application runs, it utilizes this elevated status to access all supported elements of user persona embedded within the device.
Here is an excerpt from the Automation Guide that shows how to deploy the feature.
NOTE: |
This command works with MigrationManager.EXE, and Not with SE.EXE |
Syntax |
MigrationManager.EXE /ELEVATEDCREDENTIALS <username> <domainname> <password> |
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 account specified. |
Automating
Using Tranxition migration manager requires no client install. The initial installation of the software goes to a network share, which can then be called by any desktop or laptop visible to the share. There is no remaining software on the system when the capture or injection is complete
View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.