Release Date: February 5, 2026
- Added functionality to validate if the user is logged on during pre-migration stage
- This release includes the option perform the migration reversion successfully even if the registry profilelist is renamed with .bak suffix.
- Bug fix release addressing issues with Agent Install, reverting profiles with .bak.
- Updated Windows MDM removal logic
- Additional method for migration reversion by considering the .bak suffix in the reg profile path.
- Added support for secret variables and description based bulk migration using an API key
- Test added to validate new features and existing functionality.
- Added new functions and features to handle potential edge cases when removing Windows MDM providers
- Added functionality for Invoke-SystemAPI to create, update, and delete attributes Added support for secret variables in DeviceQuery for bulk ADMU
- Resolved an issue where renaming a created temp profile fails and freezes the migration This release includes the option perform the migration reversion successfully even if the registry profilelist is renamed with .bak suffix.
- When installing the JumpCloud Agent and also specifying that the tool autobind a user, the tool would not correctly validate the passed in APIKey. This has been resolved in this release.
- This release includes the option perform the migration reversion successfully even if the registry profilelist is renamed with .bak suffix.
- Fixed a bug with Write-ToLog not properly handling Warnings in the host/console
Release Date: January 20, 2026
Added Bug fix for temp user directory renaming
- Resolved an issue where renaming a created temp profile fails and freezes the migration
Release Date: January 15, 2026
This release includes the option to update ADMU status on the JumpCloud system description field when migrating remotely. This allows administrators to track migration progress remotely.
Additional method for remotely migrating system by reading the device description field.
Several new tests added to validate new features and existing functionality.
Release Date: January 2, 2026
Patch release focused on reducing GUI and Progress bar wait times and preloading the migration progress form.
- Added functionality to backup profileImage permissions
- Added Start-Reversion Function
- Integrated Reverse Migration functionality in the GUI
- Progress form now displays immediately when the migrate button is clicked, showing placeholder values while calculations are performed
- Migration progress form is preloaded with user information before Start-Migration begins
- Added GUI loading progress bar
Release Date: December 15, 2025
This release reduces the time required to perform a migration by deferring the file permission traversal and setting to a scheduled task that runs in the background after migration completes. This should significantly reduce the time required to perform a migration on systems with large user profiles. This release includes a bug fix for flashing icons post-migration due to Windows UCPD preventing process from changing certain file default preferences like https/http/.
Decreased time required to perform a migration. Several changes and consolidation of log messages.
Resolves an issue with flashing icons post-migration due to Windows UCPD preventing process from changing certain file default preferences like https/http/.
Release Date: November 18, 2025
Patch release to address several issues.
- Resolved an issue where the ADMU EXE would return exit code 0 if an invalid API key was used. The ADMU will now return exit code 1 if an invalid API key is provided.
- Resolved an issue where remote invoke script status was not being reported correctly in certain edge cases.
- Added PrimaryUser parameter to allow for setting a user as a device's Primary User
- This release introduces the ability to set a device's primary user using the PrimaryUser parameter. This can only be done when using the AutoBindJCUser feature as well as using SystemContext.
- Profile image permission backup functionality added
Release Date: November 06, 2025
Added GUI API support for JC EU Organizations
- Added support for authenticating using API keys from EU-based organizations in the GUI.
- Updates to the invoke scripts. Additional MDM removal feature added directly to the tool.
- This release introduces an enhancement to the bulk migration script, allowing it to validate duplicate SIDs only on the local device. This change prevents unnecessary errors when the same SID exists on different devices in the CSV file.
- The ADMU now includes a feature to remove MDM enrollment from devices during the migration process. This is particularly useful for devices that are AzureAD joined and enrolled in MDM, as it allows for a smoother transition to JumpCloud management.
Release Date: October 20, 2025
Update to the invoke scripts + module to support executing the ADMU as our EXE application opposed to the PowerShell module.
- Updated the invoke scripts and module to support executing the ADMU as our EXE application opposed to the PowerShell module. This should improve reliability when invoking the ADMU remotely from JumpCloud Commands or other RMM tools.
Release Date: October 13, 2025
Patch release of the ADMU module, several non-functional change improvements and new tests added to the module.
Update deploy build process to generate pester tests for private functions. New private functions created to reduce duplicated code.
Release Date: October 6, 2025
Addresses an issue where failed migrations were never reported back to the JumpCloud console if using the `$reportStatus` parameter. Addresses an issue with slow performance when setting file permissions.
N/A
- Migrations, specifically setting NTFS permissions should be much faster on large directories with many files. The ADMU will now use
icacls.exeto set file permissions which has shown to be significantly faster on large directories with many files.
- The ADMU will now report failed migrations back to the JumpCloud console if the
$reportStatusparameter is used. Previously only successful migrations were logged correctly to the console.
Release Date: October 1, 2025
Updated gui_jcadmu.exe to handle parameters for bulk ADMU migration
Command-Line Parameter Support for gui_jcadmu.exe
- The ADMU GUI executable can now be invoked with command-line arguments to automate and script user migrations
- The ADMU Template Build script has been updated to accept and process parameter inputs, embedding them directly into the template file
- The build process for gui_jcadmu.exe was enhanced to create a mapping of string and boolean parameters, ensuring proper handling of command-line arguments
Added a fix for Shutdown or Restart not working when using the API key
Release Date: September 9, 2025
Added additional validation for API calls to the JumpCloud API. Updated the remove Invoke Commands for remotely calling ADMU from JumpCloud Commands.
- Resolves an issue where the ADMU would not successfully migrate a user if the console.jumpcloud.com could not be accessed. The ADMU will now retry API calls up to 3 times and will not throw a terminating error if the API is unreachable.
Release Date: September 5, 2025
Added migration status reporting using the JumpCloud system description field (CLI only).
This release addresses an issue with setting permissions on the migrated account
Migration Status Reporting in JumpCloud: The migration tool now updates the System Description field for a device in the JumpCloud console with its real-time migration status. This allows administrators to remotely monitor the progress of a migration directly from the JumpCloud UI without skimming through JumpCloud Commands results. (Note: This is currently available for migrations initiated via the CLI only.)
Enhanced visibility into the migration process by providing real-time status updates directly within the JumpCloud console, reducing the need for administrators to check local logs or have direct access to the machine.
- Resolves an issue with migration where a device that had left a domain was unable to successfully migrate a domain user due to account name resolution. This release matches on a user's SID opposed to account name to accommodate scenarios where account migration occurs and the device is no longer joined to the domain.
Release Date: August 19, 2025
Added informational validation and logging messages for the bulk ADMU script. Improved performance for setting NTFS permissions on the user's profile directory. When a user is migrated in this version of the tool, their profileImagePath will now be appended with a ".ADMU" string to ensure that the profileImagePath is unique and does not conflict with existing user profiles. Accounts that have been previously migrated with the ADMU will not be affected by this change. Accounts migrated with this and future versions of the ADMU will have a unique profileImagePath and the tool will prevent these users from being accidentally migrated twice.
- Added CI tests for bulk ADMU
- Improved performance for setting NTFS permissions on the user's profile directory
Release Date: May 29, 2025
This release includes several bug fixes for remotely invoking the ADMU, addresses an issue with GPO wallpaper policies and addresses an issue with permissions in sub directories of the AppData folder not being migrated correctly.
- When an invalid API key was used to invoke the ADMU from a remote script, the tool would exit with an error code that was not properly handled and difficult to trace. A change to the remote invoke scripts is included in this release to ensure that the full error message is returned. The Start-Migration script will no longer error in the same way when an invalid API key is used.
- When a device was migrated that had previously had a domain wallpaper applied, the previous versions of the ADMU would not detect this policy and a user migrated from this state would have a blank wallpaper on first login. This release will remove this wallpaper policy from the newly created user's registry. They will receive the default wallpaper and a new policy will need to be applied if a managed wallpaper is required.
- Certain hidden directories in the AppData folder were not being migrated correctly. This release addresses this issue and ensures that all sub directories of the AppData folder are migrated with the correct permissions.
Release Date: May 29, 2025
This release changes the ownership of the migration profile's file directory to the newly migrated user. Previously the ownership of these directories remained under the AD user profile.
Release Date: May 13, 2025
This release addresses an issue with the ADMU where the tool would not leave a hybrid joined domain. This release also addresses an issue with Windows Universal Platform (UWP) applications where the tool would not register the UWP applications on first login if a path for the app was not found.
Release Date: May 7, 2025
Update to the logging function to specify certain parameters to be excluded from the log file. Updated the remote migration script to include several new validation steps.
Release Date: May 06, 2025
Add new feature to bind user with the systemContextAPI as opposed to APIKey/ OrgID credentials.
The ADMU now allows for binding a userID to the device post-migration with the $systemContextBinding & $JumpCloudUserID parameters
Addition help messaging generated for the Start-Migration parameter and parameter sets
Release Date: April 15, 2025
Resolves a bug in 2.7.17 where the connectKey would validate but not allow a user to complete GUI migration.
Resolves the bug where the start migration button would never initiate migration.
Release Date: April 14, 2025
Newly generated JumpCloud connect keys are no longer only limited to 40 characters this change removes the check to validate connect key length.
Release Date: March 25, 2025
This release addresses an issue introduced v2.7.11 where local domains were no longer being left when the tool was prompted to leave a domain post-migration
Addresses an issue where the tool would not leave local domains
Release Date: March 18, 2025
This release enhances user directory redirection validation. Migrations now proceed correctly when user shell folders are redirected to OneDrive, Google Drive, and other local paths.
N/A
Release Date: March 12, 2025
This release addresses an issue with Registering Default Windows Platform apps on first login. And resolves several issues with registering the file type associations on first login.
The UWP application is now updated to use XAML presentation framework, a job for re-registering the APPX files is now kicked off through the UWP app as a separate process. This resolves the issue where the Add-AppxPackage function would fail to register apps.
Release Date: January 31, 2025
This release addresses some code quality issues and a bug-fix for certain Windows 11 systems where migrated users could lost access to use Windows search post-migration.
- Functions in this release are now broken up into individual files to de-clutter the Start-Migration script
- Windows 11 systems with a specific build and Microsoft KB installed could lose access to the Windows Start search menu post-migration, this release applies the same fix in 2.4.3 (At the time then only affected Windows 10 systems) to Windows 11 systems.
Release Date: January 3, 2025
- This release prevents ADMU from migrating if one of the main user folders (Desktop, Downloads, Documents, Pictures, Music, Videos, Favorites) are redirected to network shared path
- Fix issue when migrating a user with one of their main user folders are redirected to a network path. ADMU will now throw an error and prevent migration if any of the primary user folders (Desktop, Downloads, Documents, Pictures, Music, Videos, Favorites) are redirected to network shared path
Release Date: November 21, 2024
- This release removes 40 char API key validation
- When the migration fails during the account copy/merge processes, the tool would revert and remove the newly created account. We risk deleting user data once we do the account reversal in this step. To combat this, we have added a tracker to not remove the created account profile during account merge failure.
- Remove unused .exe files
- Fix progress form buttons disabled when JCAgent install fails
- Fix issue with JCUsername that have a localUsername where progress form GUI get's stuck during migration when AutoBind is selected
- Fix issue with MTP selection popups when migrating a user that belongs to an MTP
Release Date: October 14, 2024
This release prevents the ADMU from considering the migration a failure if the leave domain step does not complete as expected. This release adds Windows OS version, edition, and build number information to the log
- When the ADMU encounters an issue with leaving the domain, the tool would mark this step a failure and attempt to revert the newly created user. In doing so the account being migrated was erroneously removed. This release allows for the leave domain step to fail but does not consider the failure of that step to be an overall migration failure. Migration can still succeed if the system fails to leave the domain for any reason.
Release Date: September 25, 2024
This release resolves an issue on Windows 10 systems where users were unable to use the search bar post-migration
- Resolves an issue on Windows 10 systems where users were unable to use the search bar post-migration
Release Date: August 21, 2024
This fixes an issue with disabled Migrate Button
- Fixed an issue with ADMU UI "Migrate Profile" button where it remained disabled even though all the required fields were satisfied.
Release Date: August 28, 2024
This release reverts changes from 2.7.4 in the UWP app, specifically the xaml form was reverted back to the original windows form to display progress of the Appx/ File Association during first boot. This release adds additional logging to the UWP app.
- Reverted UWP changes from 2.7.4 to address reports of the UWP app freezing on first login
Release Date: August 14, 2024
- Fixed an freezing issue with UWP app/form when interacted
- Updated useragent text
Release Date: July 25, 2024
- Fixed an issue with leave local AD
Release Date: July 16, 2024
- When a system had more than 5 local user accounts, the GUI window would stretch to show multiple accounts and the Migrate button would become hidden. The window size is set to a static value in this release.
Release Date: July 16, 2024
- UI improvements for Form
- While migrating with the exe application, the ADMU will now show the progress of the migration within a GUI window. Migration logs can be viewed in this window, new migrations can be triggered after a successful or failed migration.
- Updated JC brandings
- Added an optional param -AdminDebug for showing verbose log messages
- An error mapping function was added to the tool to provide better feedback when the tool encounters an issue with a migration.
- When loading/ unloading a user's registry hive and an error is encounered, the tool will attempt to close any processes owned by that user.
- Added a validation to check if jumpcloud username and local username are the same
- UWP wording change
Release Date: May 14, 2024
- Addresses a specific case that would prevent migration when a user's `NTUSER.DAT` registry hive was set with a `system` attribute
Release Date: Mar 29, 2024
- Fixes an issue with hybrid unjoin would not leave local domain
Release Date: Mar 28, 2024
- Update Signing Certificate
Release Date: Mar 6, 2024
- Addresses an issue with the `leaveDomain` parameter where devices that were hybrid joined would not leave the domain.
- When selecting "leave domain" in the GUI or specifying the `leaveDomain` parameter using the PowerShell module, hybrid joined devices will now leave the domain successfully
- Set the PowerShell module to release
Release Date: February 12, 2024
- Added a feature to migrate default applications (file associations) and protocol associations
- Addressed a issue where a registry hive fails to load, the tool will now halt migration instead of continuing
- Fixed a bug with Module Changelog version test where release type number is not properly outputted
- Fix issue with manual release type not included in tests
Release Date: December 18, 2023
Migrate the CI workflow from CircleCI to GitHub Actions
Additional tests written to validate module before release
Release Date: August 30, 2023
- The ADMU now checks for scheduled tasks before migration and attempts to disable any non-microsoft task. Scheduled tasks which load a user's registry into memory have been reported to have locked a user's registry into memory which will prevent the ADMU from functioning. This release of ADMU will attempt to disable any root level scheduled tasks and will re-enable these tasks after migration or if the ADMU fails to migrate.
- Only tasks that are in a "Ready" state will be disabled, currently running tasks are not stopped.
Release Date: Aug 23,2023
- Fixed an issue with Windows 10 devices, where migrated users would no longer be able to access their start menu and search bars.
- Remove Microsoft Visual C++ 2013 dependencies that are not needed for JCAgent installation.
- Fixed incorrect agent binary name causing incorrect installation checks.
- Add validation of JCAgent using Service instead of file path for installation.
- Fixed an issue when Migrating from AzureAD users where their AppxPackages were not properly identified.
- Fixed an issue when leaving an AzureAD domain where the tool would not leave the domain.
Release Date: Aug 4,2023
- Add additional logging and validate file permissions when migrating.
- The GUI From now validates that windows usernames be a max length of 20 characters.
Release Date: March 31,2023
- When the 'Autobind JC User' option is specified, a JumpCloud user's 'Local User Account' will be used instead of it's 'username' if the 'Local User Account' value is set in the console.
If a JumpCloud user has a 'Local User Account' value set and the 'Autobind JC User' option is not set, the selected user will be migrated as the username specified in the 'Local Account Username' Field.
Release Date: March 27,2023
- Updated JumpCloud ADMU to optionally set last logged in Windows user to the migrated user
- Updated JumpCloud ADMU installer to .msi
Release Date: February 22, 2023
Update the JumpCloud Agent Installer URL to new CDN URL.
Release Date: February 21, 2023
This version of the JumpCloud ADMU will unbind systems as NT/Authority SYSTEM if running as administrator. This change should only address a limitation with administrator credentials and leaving AzureAD Domains.
Update Code Signing Certificate
Release Date: Dec 6, 2022
- For the GUI version of the tool, if the system is AzureAD Domain Bound, the tool will prevent users from leaving the domain. System access is required to leave an AzureAD domain, administrator permission is not sufficient. A future change will be added to address this issue where a job will be kicked off with system permission. In the meantime, [refer to the wiki](https://github.com/TheJumpCloud/jumpcloud-ADMU/wiki/Leaving-AzureAD-Domains) for details behind this change.
Release Date: November 17, 2022
- Additional Logging for username search
- Support for binding users as Administrators
- Invoke-FromJCAgent scripts updated
- Support for MTP Admins
- New Parameter `JumpCloudOrgId` added to the Start-Migration function.
- GUI Prompt added to specify an MTP Organization if a MTP Key is detected
Release Date: November 2, 2022
- JumpCloud username search is no longer case sensitive.
- Updated Advanced Deployment Scripts to support multi-user migrations.
- Script failures should not result in the ADMU catching the error & displaying the log message.
- When selecting AutoBind JumpCloud User, the ADMU will also validate that the agent is installed prior to running migration. The tool would otherwise always fail to bind the user.
Release Date: Oct 21, 2022
- Updated prerequisite paths for JumpCloud Agent and added try/ catch statements.
- Addressed an encoding issue with the PowerShellForGitHub module and the invoke ADMU from agent workflows. If the newest version of the module 0.16.1 is used the scripts will no longer throw an error regarding invalid JSON.
Release Date: Oct 13, 2022
- Module EXEs have been updated with a new DigiCert code signing certificate. The prior GoDaddy certificate could not be renewed at the end of this year.
- Wmic commands replaced with powershell equivalent options (thanks to [@willemkokke](https://github.com/willemkokke) for the suggestion)
- Addressed an encoding issue with the PowerShellForGitHub module and the invoke ADMU from agent workflows. If the newest version of the module 0.16.1 is used the scripts will no longer throw an error regarding invalid JSON.
Release Date: September 16, 2021
- Added API Key form and parameter to allow for "Auto-Binding" the user during Migration
- If selected, both the API Key value must also be entered
- At the end of migration the ADMU will search the JumpCloud Organization for the username entered and bind the user to the system. If the user does not exist the ADMU log will produce a warning message.
- The GUI will validate that the JumpCloud user exists in the console before Migration
- GUI runs of the ADMU should prompt to view the log after migration
- The migration user's registry hive is saved as a unique filename (ex: NTUSER_original.DAT is now NTUSER_original_yyyy-mm-dd-HHMMSS)
- The 2.2.0 version of the tool no longer includes the Microsoft User State Migration Tool (USMT). Prior versions of the tool should be used if it's necessary to copy data from one profile to another.
- The default behavior of the 2.2.0 tool is to convert accounts with what was previously the `ConvertProfile` parameter.
- If profile data was mapped to a network share, the USMT could have a valid use case but the Custom XML would have to populated to migrate that data
- This is a breaking change for the CLI version of the tool, the convertProfile parameter does not exist in 2.2.0
- Migration users may be automatically bound to systems post-successful migration
- If the ADMU fails to migrate a user, the tool will attempt to remove the newly created local user so that the tool can be run again.
- This negates the need to manually remove the new local user if re-running the tool
- GUI version of the tool no longer queries account home directory size and should load much faster
- Option to Update Home Path has been removed from the GUI version of the tool
- Often times changing the home path from "migration_user" to "migration.user" would break app functionality and cause more confusion than it was intended to solve. the
UpdateHomePathparameter can still be set to true through the CLI/ PowerShell Module Version of the tool
- Often times changing the home path from "migration_user" to "migration.user" would break app functionality and cause more confusion than it was intended to solve. the
- Given the case where the ADMU writes a registry backup, subsequently fails, exits and is run again, The registry backup should not be overwritten with the same name.
Release Date: August 09, 2021
Fix for previous version 1.6.7 where after migrating a domain user with the same username as the system hostname
Domain users with the same name as the system hostname now initialize correctly and the GUI will allow for migration of these user accounts
Release Date: July 22, 2021
Block profile conversion via GUI where domain username matches system name.
Block profile conversion via GUI where domain username matches system name.
Release Date: July 8, 2021
Added AzureAD leave domain check, if not running as NTAUTHORITY\SYSTEM popup will inform in gui related wiki article.
Add logic to only run AzureAD leave domain command if running as NTAUTHORITY\SYSTEM. If not AzureAD joined, it will leave domain as normal.
If not run as SYSTEM, the GUI will stop the param being passed and a dialog shown. In the migration script an error will be logged and continue without running the leave domain command in the case of not being run as SYSTEM and AzureAD joined.
Updated 'Accept EULA - more info' link to correct URL
Release Date: June 15, 2021
Updated automated testing framework and pipeline for ADMU, no changes to the migration tool since version 1.6.4
Release Date: June 14, 2021
Added ability to change the rename step in the profile home path step. This defaults to not renaming to better account for systems where the folder is in use or can't be renamed. Also helps with any applications hardcoded to previous home path.
Adds 'Update Home Path' paramater and checkbox
Release Date: April 13, 2021
Some remote agents or RMM tools may invoke commands as NT Authority\System. If the ADMU is remotely invoked with those tools and run as the NT Authority\System account, previous versions of the ADMU would fail to migrate sucessfully. v1.6.3 addresses this and resets permissions of the blank profile so that NT Authority\System can delete the blank profile after it's NTUSER.DAT & UsrClass.dat files have been copied back to the user-to-migrate's profile.
Exit 1 (error) conditions explicitly defined when the tool fails to complete migration.
Fixes a bug for some remote agent or RMM tools which would cause the ADMU tool to fail migration.
Release Date: March 29, 2021
Improve registry load, copy and unload steps.
Registry load, copy and unload steps have been streamlined. Before modifying a user's registry, the files are first checked to unsure they can be loaded and unloaded without error. After loading the profiles for modification the copy step will only modify the backup registry file. Once all modifications are complete, the registry files recognized by windows are renamed for backup and the backup files are renamed so windows recognizes those files on profile login. This should prevent profiles being left in a half-migrated state if some step in the process fails.
Release Date: March 16, 2021
Improve local user folder check for capitalization and other scenarios.
Fix Discovery AD query for GT $time.
Add ADMU version in log.
Fix Discovery AD query to output correctly -gt
Account for capitalization in AD username and local profile folder
Release Date: February 24, 2021
Calling ADMU Start-Migration using WinRM no longer requires CredSSP to initialize the user profile account.
New user profile is initialized without spinning up a new process for that user.
Added example scripts for invoking ADMU & discovery scripts from RMM/ Agents on systems
New local user initialization is streamlined and no longer relies on passing the user's temporary credentials.
Fixed a bug where new user accounts with the same name as the domain user account would be named "username.000" and not convert correctly.
Release Date: February 18, 2021
Updates to the Invoke Migartion script for auto binding the migration changes before reboot.
Fix for the invoke migration script where the jumpcloud user was never bound to the system after migration.
Release Date: February 11, 2021
Minor bug fixes to improve conversion process when run as foregin language.
Add monitor job and improve admu-discovery script.
- Improve admu-discovery script and add monitor job function
- Add SID lookup to ACL function to account for foreign languages
- Add additional wait time for unload of user registry before conversion starts
Release Date: January 18, 2021
Added ADMU advanced deployment scripts for use with mass deployments, added ability to utilize credssp for new user instantiation.
Added mass deployment scripts for discovery and invoke-admu
Time required to 'Convert User' has been significantly decreased.
- Fix for profile path where similarly named profile paths evaluated to the same profile path
- Fix uwp_jcadmu.exe 0kb download bug
Release Date: December 21, 2020
Added exit code check if error when creation of user for example if password does not meet complexity requirements.
ADMU will error and exit if the new user creation step does not complete.
Release Date: December 11, 2020
During login and after an account has been converted, a powershell window displayed while the uwp apps were registered to the new local account. This release includes an update to the uwp_jcadmu.exe to display the JumpCloud logo and a progress counter with progress percentage of the uwp apps registered to the new user.
- Splash screen added during first login to converted account
Release Date: Dec 10, 2020
Ability to convert rather than duplicate domain user accounts. User's AppData is kept intact. This conversion process is much faster than the default behaivor of migration and no addtitional storage space is required.
The Convet User Process makes several changes to the registry. It is reccommended to take a backup before converting the user account. Included in this release is an additional option to take a system restore checkpoint before running the ADMU.
Added convert User profile functionality to GUI & CLI. If secure channel is in a broken state, the ADMU can convert a profile to a local account. Added optional field to create a system restore point before migration or conversion. SelectedUserName parameter is verified to ensure that a username in the form of Domain\username or user account SID is valid on the system before migration.
Fixed local admin membership bug not displaying consistently in GUI. Fixed AzureAD informational display in GUI form.
Release Date: August 3, 2020
Functions.ps1 renamed to Start-Migration.ps1 to allow module creation and import.
Now allows install-module JumpCloud.ADMU
- Builds
ModuleChangeLog.md - Start-Migration autogen help docs
- Kill stuck installer for test pipeline
- Out-null file
- Error removing temp files when exe still in use
- Remove double jcagent install
- Don't call dsregcmd on windows 8.1 systems
- Display 'Fix secure channel' when domain joined but no healthy secure channel, rather than blank.
Release Date: July 28, 2020
JumpCloud-ADMU powershell module release pipeline.
- Package and release JumpCloud-ADMU to PSGallery.
- Azure pipeline and release tasks for automated builds and module creation and deployment.
Release Date: July 2, 2020
Fix CLI bug when installing JCAgent, improve compatability with foreign language windows versions.
- Improve administrator group query changed to use SID to work with foreign language windows versions.
- Test syntax updated for Pester V5
- Add missing condition when $InstallJCAgent -eq $true to make sure JumpCloud Connect Key is provided
Release Date: May 12, 2020
Add local and domain username checks to avoid duplicate or failed migration.
- GUI check local username doesn't exist on system to avoid duplicate user errors
- CLI parameter checks local username doesn't exist on system to avoid duplicate user errors
- CLI improved parameter validation on DomainUserName
- CLI $JumpCloudConnectKey check if $installagent $true
- Add date line to log when tool run
- Account for state if user exists on system but not ever logged in
Release Date: April 30, 2020
Improve JCAgent install order and connect key verification
- If agent install selected, will now try install steps first and error out if fails vs converting account and then running agent installer.
- Added repository outline readme
- Added JCAgent installer connect key check and error on failed install
- Can run account conversion without installing agent or requiring a connect key input value
- Clear old install directory that is generated when failed install so doesn't reuse bad connect key
Release Date: April 27, 2020
Allow Administrator to customize USMT process with custom.xml file and modify in ADMU GUI.
- Added ability to use and load custom.xml for use in scanstate & loadstate steps.
- XML validation in GUI
- CLI Start-migration -Customxml $true will use C:\Windows\Temp\custom.xml in migration script.
Release Date: April 14, 2020
Improve JumpCloud ADMU to work in remote non domain joined scenarios.
- ADMU launches when not domain joined or broken secure channel
- Shows AzureAD accounts in GUI with AzureAD information
- Now allows migration of non domain joined, AzureAD bound scenarios
- Now allows migration of domain joined AND AzureAD bound scenarios
- Now allows migration of broken secure channel scenarios
- GUI now shows orphaned profile accounts as 'UNKNOWN ACCOUNT'
- Local Administrator check added on launch
- Leave domain option for AzureAD profile will disconnect AzureAD
March 16, 2020
- Migration language fixes
- Improve pipeline and release steps
- Move images into wiki
February 3, 2020
- Fix download link in readme
- Regex for pipeline build number checks
February 2, 2020
- Fix build status badge
- ps2exe module install check
- Revert latest agent installer
January 31, 2020
- Readme changes
- Add aditional tests
January 31, 2020
- Added Azure pipeline exe builds & signing
- Block local profile migrations in GUI
- exe and XAML form version checks
January 3, 2020
- Test-ComputerSecureChannel check for GUI and CLI
- Readme Computer Account Secure Channel explanation
- Fix $true/$false values for parameter logic
December 31, 2019
- Fix $AzureADProfile string & boolean error
- PSScriptAnalyzer fixes
- Azure Pipelines & testsetup script for local build server
- Changes for seperating repo from support
- Add in additional exe, gpo tests
- Fix flaky 'Add-LocalUser Function' test by swapping 'get-localgroupmember' with 'net localgroup users'
December 2, 2019
- ConvertSID Function updated to work on windows 7 and powershell 2.0
November 26, 2019
- Add $AzureADProfile Parameter to allow conversion via migration.ps1 script
November 19, 2019
- Force reboot without delay or keypress to work with CLI deployments
- Update Boolean options for EULA, Agent, LeaveDomain & ForceReboot
October 29, 2019
- Fix Win7/Powershell 2.0 SID conversion query used in local admin check in GUI
October 14, 2019
-
Improve further and reduce migapp.xml & miguser.xml entrys. This will reduce overall file count and scanning times.
-
Aditional Pester tests and azure pipeline CI for improved automated testing.
September 27, 2019
-
Improve and reduce migapp.xml & miguser.xml entrys. This will reduce overall file count and scanning times.
-
Add UI loading feedback using write-progress.
-
Add localadmin column to UI for profiles.
-
Add profile size column to UI for profiles. Also add system c:\ available space to UI.
-
Introduce Pester tests and azure pipeline CI for improved automated testing.
September 6, 2019
-
Fix netbios name to use better function and account for cases where netbios name is different than domain name.
-
Change ADK install path to use default.
-
Improve install and running of USMT on x86 and x64 systems.
-
Introduce custom config.xml to remove APAPI prompt.
-
Introduce custom migapp.xml and miguser.xml to add more applications and downloads folder migration.