Merge of 2.0.0 changes into master. This release contains the following features:
Auto bind functionality when APIKEY is provided prior to migration
GUI Validation for username in JumpCloud console
Prompts after migration to view logs
Registry backup is more robust if the tool needs to be run twice
USMT references/ functions have been removed from the tool
Reversal framework to better handle cases where the tool fails
Is there anything particularly tricky?
Yes, this is a overhaul of most of the codebase but the majority of the convert user functionality remains unchanged. The most significant changes between 1.6.8 and 2.0.0 are the addition of the auto bind feature and the reversal framework where the tool can recover if it encounters an error.
How should this be tested?
Functional tests cover many scenarios and test against new feature set. The GUI changes however should be tested manually
Test AutoBind + APIKEY + Username validation works in GUI:
Load GUI on AD Bound system
Select "AutoBind JC User", Enter valid API KEY and enter an invalid user in the JumpCloud org
Select Migrate Profile
The prompt should appear and note that a matched user was not found in the org
Load GUI on AD Bound system
Select "AutoBind JC User", Enter valid API KEY and enter a valid user in the JumpCloud org
Select Migrate Profile
The ADMU should continue to migrate and complete successfully
Test log prompt functions work
Load GUI on an AD Bound System
Complete migration of a user
After successful migration the ADMU should prompt and note that the log may be viewed
Test that by clicking 'Ok' the log is indeed opened.
Errors during migration which prevent migration should result in the new user being removed from the system
Load GUI on an AD Bound System
Start a process for the user being migrated
The ADMU should fail to write back to that user's registry during the registry replace step
The new username provided when running the ADMU should no longer exist on the system after the ADMU errors out.
Azure AD Profile is successfully migrated
Migrated AzureAD Account either with the GUI or CLI version of the tool
Issues
What does this solve?
Merge of 2.0.0 changes into master. This release contains the following features:
Is there anything particularly tricky?
Yes, this is a overhaul of most of the codebase but the majority of the convert user functionality remains unchanged. The most significant changes between 1.6.8 and 2.0.0 are the addition of the auto bind feature and the reversal framework where the tool can recover if it encounters an error.
How should this be tested?
Functional tests cover many scenarios and test against new feature set. The GUI changes however should be tested manually
Test AutoBind + APIKEY + Username validation works in GUI:
Test log prompt functions work
Errors during migration which prevent migration should result in the new user being removed from the system
Azure AD Profile is successfully migrated
Screenshots
ADMU GUI: