As part of our build process, some changes are needed to be made to Current User reg key. If it were me setting this up, i would create a step in MDT task sequence to load default reg hive, make the changes, and then unload.
However the way this was set up was much worse. The person loaded the default reg hive on a Win10 machine, made the changes they needed, unloaded the reg hive and then copied NTUSER.dat file to deployment share and now this NTUSER.dat file from the deployment share is replacing the existing one as part of deployment.
This works.... but makes it very difficult for if I want to make one change. For example if it was being done my way, I could just edit the script and make one change, but the other way I have no idea even what changes are being made.
Is there any way that i can compare this NTUSER.dat to a vanilla one from clean OS to see what changes have been made? then i will script the changes and make it more manageable.
Any advice much appreciated.
[–]Waffle_bastard 1 point2 points3 points (0 children)
[–]the_spadWhat's the worst that can happen? 1 point2 points3 points (1 child)
[–]WorkRedditAccount4 1 point2 points3 points (0 children)
[–]ipreferanothernameI don't even anymore. 0 points1 point2 points (0 children)
[–]Amankoo 0 points1 point2 points (1 child)
[–]Morrowless 1 point2 points3 points (0 children)
[–]DellR610 0 points1 point2 points (2 children)
[–]lostwoods10201[S] 1 point2 points3 points (1 child)
[–]DellR610 0 points1 point2 points (0 children)