Updating the user registry

[Guest]

Background: I run a computer lab with 2003 servers and XP Clients. Users
have roaming profiles with folder redirection via Group Policy. Basically the
only files in their user profile of importance are the Favorites and
ntuser.dat file. Important NOTE: When users log off their local profile is
REMOVED from the computer. We have hundreds of computers and thousands of
users, this settings is essential.

Often new settings or programs are needed and I produce a new XP client
image with that includes these updates. With this new image is an updated
ntuser.dat (in the Default Users folder) that reflects the settings needed
the new programs, AND for changes I have made to standard XP settings, i.e.
background image, screen saver, etc...

Problem/Question: When an user logs on they continue to use their existing
ntuser.dat file which does not contain the correct settings for the new
client image. Obviously many programs/settings to not function correctly when
this happens.

How do I go about making the client check for a newer timestamp on the
ntuser.dat in the Default Users folder and merge it with the existing
ntuser.dat file? Is there another location I can put the ntuser.dat file to
make this happen?

NOTE: One solution I know works is to delete the users current ntuser.dat
file before log on. I cannot use this solution, doing so tricks windows into
thinking the user has never logged on before, thereby overwriting their
entire profile on the server at log off. This results in all Favorites being
destroyed, not a nice thing at all.

Thanks!
(posted also in the server group, no luck)

 

[Chris Priede]

Hi,

Background: I run a computer lab with 2003 servers and
XP Clients. Often new settings or programs are needed and
I produce a new XP client image with that includes these
updates. With this new image is an updated ntuser.dat (in
the Default Users folder) that reflects the settings needed the
new programs, AND for changes I have made to standard XP
settings, i.e. background image, screen saver, etc...

The particular settings you mention and many others can be managed through
Group Policy. Per-user registry settings for new applications can be merged
into an existing user profile from logon scripts. Logon (where you can run
things as the user) and startup (where you can run things under the local
machine account) scripts remain a great instrument for client management --
use them.

I'd also suggest you look at those means (and, perhaps, some third party
management software) for deploying applications and updates, instead of
re-imaging your workstations all the time. Since the last time I had a
chance to do it all over again, I have completely eliminated the practice of
workstation imaging, even for new machines -- all of the required software
(other than Windows) and settings are deployed automatically, when the
machine is joined to the domain, during subsequent reboots, and during the
first time user logon on the particular machine.

For some applications it has been very easy, for others it has required
repackaging; for some it has required extensive scripting. It's a case of
more intelligent work once vs. a lot of brute force work repeatefly.
Although your situation may be different, you should at least consider that
approach as an alternative. I have been extremely pleased with how it has
worked out for me.

 

[Guest]

Thanks for the suggestions.

I already do heavily use Group Policy. I will investigate pushing out reg
entries further with GPOs. That is probably one of the only portions of GP
that I haven't done anything with. This sounds like it might be a winner to
me!

Scripts are great, but I'm looking more for a do it once and it's done
solution here, I don't want to be tied down to more and more scripts at
logon. gets messy.

I don't completely use "brute force" either, I use a combination of
scripting, WSUS, RIS and ghost casting to manage my workstations. Re-imaging
becomes much necessary and easier when it comes down to major changes to the
workstation image. At most I do this 2 times a year, normally only once.
Being that this is a computer lab, the computers are tweaked quite heavily.
Besides, with RIS and ghost casting, re-imaging isn't very painful at all. I
can have every workstation re-imaged and ready for user logon in about 10
minutes start to finish.

Thanks, Marco

 

[Guest]

Well looks like I found pretty much what I was looking for. Maybe this will
work for anyone else looking to solve similar issues...

http://msdn.microsoft.com/library/d...w2kmag01/html/DistributingRegistryChanges.asp