ADMU GUI
Download the latest version of the ADMU executable GUI from the releases page. To run the application, double click the gui_jcadmu.exe file. When the ADMU GUI launches, a list of the system accounts, migrations settings and Account Migration information is displayed.
If a system is bound to a domain and the Secure Channel is healthy, accounts will be displayed with their Domain\Username. If the secure channel for a system and domain is broken, system accounts may be displayed with a security identifier value (SID). In this case, the Local Path field can help identify which account is intended to be migrated.
To run the tool, an account must be selected, system migration options configured and account migration specified. If a set of options or information is left unspecified, the ADMU will not validate nor allow the user to select "Migrate Profile"
The following options can be configured when migrating accounts. Refer to the parameter documentation for a complete explanation of each setting and all configurable options which may not be available in the GUI version of the tool.
A JumpCloud Organization's Connect Key. This field is required if the Install JCAgent checkbox is selected. This value must be 40 characters in length.
A JumpCloud Administrator's Organization API Key. This field is required if the Autobind JC User checkbox parameter is selected. This value must be 40 characters in length.
If an MSP administrator key is entered, the tool will prompt you to select the appropriate organization.
Selecting this checkbox will require the JumpCloud Connect Key to be entered. The JumpCloud agent will be installed on the system when this is selected.
Selecting this checkbox will require the JumpCloud API Key to be entered.
The ADMU will attempt to bind the username specified in the "Account Migration Information" box to the system after a successful migration.
If this parameter is selected and the user is bound to the system, the newly created user can login with their JumpCloud password instead of the temporary password. The username provided in the "Local Account Username" field will be validated against the JumpCloud console if this checkbox is selected. If the username is not found in the JumpCloud organization, a notification will display that the user was not found.
Usernames entered in the ADMU must match the case sensitive username in JumpCloud.
Selecting this checkbox will force reboot the system after migration.
It's often required to restart the system if the Leave Domain parameter is selected in order to fully update the Windows login window. The Leave Domain and Force Reboot parameters are often selected together.
Selecting this checkbox will un-join the system from it's configured domain.
The fields under the Account Migration Information refer to the new local account in which the selected domain account will be migrated to.
This field should correspond to a user in an organization's JumpCloud console. This is the account in which the migrated user will log into post-migration. If the JumpCloud API Key is specified and Autobind JC User checkbox is selected, the ADMU will attempt to bind this username to the system. If this username does not exist in JumpCloud, the tool will display a message.
This field is the temporary password in which the newly created local account may use to login. If the AutoBind JC User checkbox is selected, the newly migrated user will login with their JumpCloud password, otherwise, the user will login with this password.
The 'Migrate Profile' button will not become active active until the form validates. Informational and error icons next to each field should display help messages if the cursor hovers over the icon.
To use the GUI, run the gui_jcadmu.exe file as administrator from the latest release. On windows 10 'smartscreen' can alert the user the file is high risk. The executables publisher can be verified to ensure it came from JumpCloud Inc.
Chrome/Edge .exe download alert:
Windows Smartscreen alert:
The ADMU can be launch via PowerShell as long as the support scripts are also in the same folder. The 3 required scripts are:
- Form.ps1
- Start-Migration.ps1
- Start-JCADMU.ps1
cd \PathContaining\Start-Migration.ps1
.\Start-JCADMU.ps1