Contact Us
Help Center Home > Troubleshooting KB > Troubleshoot: Active Directory Migration Utility Errors

Troubleshoot: Active Directory Migration Utility Errors

You may encounter errors related to copying the target user’s registry hive when running the JumpCloud Active Directory Migration Utility (ADMU).

Error

Registry Backup Error: Could not take a backup of the user registry files. Verify that the admin running ADMU has permission to NTUser.dat/UsrClass.dat. Verify that no user processes/ services for the migration user are running.

Resolution

  • Session Management
    • Log in as a local administrator and ensure the target user is not active on the device. The ADMU interface will display the Active status of the users on the device. Occasionally a reboot is necessary to ensure all of the active user’s files are closed.
  • Antivirus and Security Checks
    • Ensure that the ADMU Tool executable and NTUser.dat/UsrClass.dat are both added to the antivirus whitelist.
  • Device Configuration
    • Verify that the Administrators groups has full access permissions for NTUser.dat and UsrClass.dat.

Error

The ADMU tool closes with no errors. In the log, you may see:

2024-05-30 12:30:14 WARNING: ADMU encoutered the following errors: backupOldUserReg
2024-05-30 12:30:14 WARNING: The following migration steps were reverted to their original state:

Resolution

This is a permissions error message. Download PSExec from MS Sys Internals website. Run the following command to launch ADMU as LocalSystem to resolve the permissions error.

psexec -s -i c:\path\to\gui_jcadmu.exe

Error

Users are unable to use windows Apps and Resources and windows search keeps buffering with loading sign.

Symptoms:

  • ADMU tool is used to migrate accounts from a domain to local accounts
  • Whenever users try to login they are unable to click on any icons on the desktop
  • Sometimes the monitor goes black and can only be accessed from the CTRL + ALT + DELETE menu.
  • Resources can be accessed by pressing the windows key and typing, but nothing works otherwise

Resolution

  1. Go to C:\Users\targetuser\Appdata\Local\Microsoft\Windows      
  2. Rename the folder and let windows recreate this folder by restarting the system, e.g., C:\Users\targetuser\AppData\Local\Microsoft\Windows.old
Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case