Troubleshooting errors
A log is generated each time the ADMU is ran and stored in C:\Windows\Temp\jcadmu.log. The jcadmu.log file can help troubleshoot possible issues with the tool. Frequently found errors are detailed below along with their common resolution paths.
Could not get the profile path for S-1-5-21-4145648710-2827424607-2491035611-1106 exiting...The User Account did not have a corresponding profile image path in it's registry entry. The account is most likely invalid.
Could not get the profile path for someJumpCloudUserName exiting...The User Account did not have a corresponding profile image path in it's registry entry. The account is most likely invalid.
SID or Username is invalidThe user account could not be found on the system. The Account is most likely invalid if this step does not resolve with a valid SID
Could Not Backup Registry Hives: Exiting...The ADMU could not create a copy of the domain or new local user's registry NTUser.dat files. If the account has a process in memory loaded this could trigger this error. Restart the system and try again. If this does not resolve the issue, a scheduled task triggered to start at login could be loaded. Check Task Scheduler if any processes are cached with the user's credentials and set to load at startup. If that's the case, the user's registry is mostly likely being opened and improperly closed by that process. Either remove the task or disable it. Tasks can be assigned to the new local user after migration if they are necessary.
The user: someJumpCloudUserName could not be created, exitingIf the JumpCloud Username could not be created, it's likely the case that the local user already exists on the system. Sometimes this can occur is the ADMU is ran more than once for a particular account. Using lusrmgr.msc delete the local user from the system. Delete the C:\Users\someJumpCloudUserName profile directory before running the ADMU again.
The user: $JumpCloudUserName could not be initalized, exitingIf the JumpCloud Username could not be initialized - ensure that the Administrator running the ADMU has permission to create user accounts on that system.
Could not load and unload registry of migration user, exitingIf the account has a process in memory loaded this could trigger this error. Restart the system and try again. If this does not resolve the issue, a scheduled task triggered to start at login could be loaded. Check Task Scheduler if any processes are cached with the user's credentials and set to load at startup. If that's the case, the user's registry is mostly likely being opened and improperly closed by that process. Either remove the task or disable it. Tasks can be assigned to the new local user after migration if they are necessary.
Could not copy backup registry hives to the destination location in $($olduserprofileimagepath): Exiting...If the account has a process in memory loaded this could trigger this error. Restart the system and try again. If this does not resolve the issue, a scheduled task triggered to start at login could be loaded. Check Task Scheduler if any processes are cached with the user's credentials and set to load at startup. If that's the case, the user's registry is mostly likely being opened and improperly closed by that process. Either remove the task or disable it. Tasks can be assigned to the new local user after migration if they are necessary.
Could not rename origional registry files for backup purposes: Exiting...If the account has a process in memory loaded this could trigger this error. Restart the system and try again. If this does not resolve the issue, a scheduled task triggered to start at login could be loaded. Check Task Scheduler if any processes are cached with the user's credentials and set to load at startup. If that's the case, the user's registry is mostly likely being opened and improperly closed by that process. Either remove the task or disable it. Tasks can be assigned to the new local user after migration if they are necessary.
Could not rename backup registry files to a system recognizable name: Exiting...If the account has a process in memory loaded this could trigger this error. Restart the system and try again. If this does not resolve the issue, a scheduled task triggered to start at login could be loaded. Check Task Scheduler if any processes are cached with the user's credentials and set to load at startup. If that's the case, the user's registry is mostly likely being opened and improperly closed by that process. Either remove the task or disable it. Tasks can be assigned to the new local user after migration if they are necessary.
Unable to rename user profile path to new name - someJumpCloudUserName.If this error is triggered, it's likely the case that the account running the ADMU does not have permission to rename directories in C:\Users\. Run the ADMU with an account that does have permission to rename directories in the users directory.
ERROR: System is NOT joined to a domain.
The system is not bound to a domain. The ADMU requires a system be bound to a domain before converting domain accounts to local accounts.
ERROR: Microsoft Windows ADK - User State Migration Tool not found in c:\adk. Make sure it is installed correctly and in the required location.
The Microsoft Windows ADK must be installed in c:\adk. If it is installed in another directory the script will fail. The ADK default installer path in 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit'. To resolve this uninstall the ADK and either reinstall or let the script install in c:\adk.
ERROR: Failed To Download Windows ADK Setup
If the download step fails to download the file to the directory the script will error out. This could be due to a lack of internet connectivity or other network issues.
ERROR: Failed to complete scanstate tool
the log will show the 'scanstate' command that is being run on the system, if it fails to complete, the script will error out. The preceding INFO log entry can help with troubleshooting and verifying if the command is correct. It could be possible that the disk does not have sufficient space to complete the scanstate command.
INFO: Starting scanstate tool on user jcadb2\bob.lazar
INFO: Scanstate Command: .\scanstate.exe c:\Windows\Temp\JCADMU\store /nocompress /i:miguser.xml /i:migapp.xml /l:c:\Windows\Temp\JCADMU\store\scan.log /progress:c:\Windows\Temp\JCADMU\store\scan_progress.log /o /ue:** /ui: $netbiosname /c
ERROR: Failed to complete loadstate tool
This is similar to the scanstate error but for the loadstate tool, if it fails to complete the script will error out. This could be due to issues with the scanstate step and a corrupted store state in c:\Windows\Temp\JCADMU\store\
ERROR: Failed To add new user ' + $JumpCloudUserName + ' to Users group
If the script fails to add the newly created user to the 'users' group on the system it will error out. This could be due to the fact the account doesn't exist or a duplicate or incorrect account name was used etc.
ERROR: Jumpcloud agent installation failed
The Jumpcloud agent could error due to the agents prerequisites failing to install (C++ runtimes) or due to the installer being passed an incorrect connect key. If either of these steps fail it will error out.
ERROR: Unable to leave domain, Jumpcloud agent will not start until resolved
The final step is for the system to leave the domain and remove the active directory bind of the system. This utilizes a WMI call to leave the domain from the client side. If this step fails to occur, the ADMU will produce this error. If the domain bind still exists the workstation will not be able to start the JumpCloud agent.
WARNING: Removal Of Temp Files & Folders Failed
The script attempts at various stages to clear and recursively delete files to leave the system in a clean state. If any of the files in use are locked, this step will output a warning. This would indicate the files may still be on the system and should be manually cleared if required.