|
I created an image for 1000-1300 PCs. It has already been pushed, and despite 3 rounds of testing, they are just now discovering errors.
The PCs run Faronics Deep Freeze, which basically restores everything at boot. Hence everytime a user logs in, they get a new profile from the default user profile (which I have previously customized when I built it).
Each boot, a script is run that makes modifications. During the night, Deep Freeze enters a "thaw cycle" and the changes pushed in the script become permanent. Ultimately, I can copy a new ntuser.dat to the default user profile and as long as I use intelligent scripting, I can make it only happen once.
But.. (and in life there is always a but..) When 1000-1300 PCs bang into the server during the that cycle, the CPU, I/O etc goes through the roof for a while. Ideally, I'd like to push 10K of registry changes rather than a 3MB file to these devices. The problem is when it rusn these scripts it does so as .default, and not default user. To make this work, I would have to load the default user's NTUSER.DAT as a hive, make the changes, and unload the hive as part of the script. I'd like to avoid this if at all possible and was hoping there was a better way to manipulate the default user's NTUSER.DAT withough loadinding and unloading it during the boot script.
|