jworkmanjc
commented
1 day ago Hey @l1ttlerain56, I'd encourage you to actually use the latest version of the ADMU found in our releases page: https://github.com/TheJumpCloud/jumpcloud-ADMU/releases
Can you give that a shot and let me know if that works?
The NTUser.DAT file can be locked for so many reasons but technically what's happening on your system is (most likely) some application is leaving an open handle in memory, loading that user's registry when you attempt to migrate and not closing that handle correctly.
The ADMU entirely relies on being able to close and open the user's registry to migrate the account. If you open up Registry Editor and check in the HKEY_USERS hive I bet you'll see the user's profile loaded before, and if not, during migration. It could be the case that an Anti-Virus or Data Protection application is holding on to your user's registry during migration and if that's the case you might want to try to run the tool with those disabled.
Again, there are going to be multiple possibilities for the NTUser.DAT file being locked but generally you can narrow it down to one or two thing. Please try with the latest version, we've added a number of items to the tool since 2.5.0
l1ttlerain56
Hi there,
We've been using ADMU v2.5.0 without issue to migrate users. However, on one of our user's endpoints, the ADMU tool consistently fails due to it thinking that the AD user's ntuser.dat file is being used by another process. This happens while logged in as the local admin, and even after multiple reboots. Using sysinternals process explorer, I see no process that is utilizing that user's .dat file. Not sure what else to check for. Please advise.
Thank you!