Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW replacing ntduser.dat in a bunch of remote machines

  • Thread starter Thread starter Manuel
  • Start date Start date
  • Replies Replies 4
  • Views Views 2K

Manuel

Well-Known Member
Messages
301
Reaction score
8
Points
18
Hello everyone

I had the windows user profile corrupted and for that reason it did not load the user profile and I could not logon on two domain computers

After replacing the ntuser.dat file in the default folder with another good file from the same OS version, the problem disappeared

I have some remote computers and few technical staff located remotely, so I would like your opinion if it is feasible to use the configuration manager to replace the ntduser.dat file, in a collection of computers?

Or is there a consideration to keep in mind for scenarios like this
 
That would be pretty simple with some PowerShell to replace all users on a machine. I would do a check for a user being logged before it was replaced. I would do task sequence with ps and package to get the ntduser.dat file.
 
That would be pretty simple with some PowerShell to replace all users on a machine. I would do a check for a user being logged before it was replaced. I would do task sequence with ps and package to get the ntduser.dat file.
If the server has 4 profile users, perhaps one of them has this issue, so the rest of users are working fine.

the same behavior happens in other server, so I would like to change only in the affected profile user the ntduser.dat file
 
If the server has 4 profile users, perhaps one of them has this issue, so the rest of users are working fine.

the same behavior happens in other server, so I would like to change only in the affected profile user the ntduser.dat file
How do you know which profile is affected? once you can determine that , you can create a powershell script to test for that.
 
How do you know which profile is affected? once you can determine that , you can create a powershell script to test for that.
Hi Garth, hope you get well!,
Till now, I believe it’s quite difficult to know it, in other sceneries this error happen due to 3rd party software, like AV and malware agent and not happen with all user profile. In this case, a ntduser.dat file does not have all the Windows security access entries.

If I manually load it, the user profile error would disappear. Ya
 
Back
Top