MPaquette wrote:
Like I said in my original post, this doesn't work. An error message appears
saying ""Not all data was successfully
written to the registry. Some keys are open by the system or other
processes."
:
Howdie!
MPaquette wrote:
I already tried creating a *.reg file but a normal user cannot update those
specific registry keys. How are people going to visit hundreds of machines
where normal users don't have local administrator access? What a nightmare.
You don't have to.
Log on as Administrator. Look for the registry key and create a
*.reg-file for it.
Go create a Group Policy startup script (under CompConf\...) which will
run under the SYSTEM-account and have sufficient rights to make the
changes at the registry.
Deploy the registry key within a script via regedit /s whatever.reg
cheers,
Florian
--
Nachwuschsadmin aus dem Süddeutschen/Germany.
eMail: Vorname [bei] frickelsoft [Punkt] net.
blog:
http://www.frickelsoft.net/blog.
You didn't say in your original post that you deployed it by running a
startup script. The error message is generic, as it says, some keys MAY
be open. It also may just mean you don't have permissions. Since the
startup script runs with the necessary rights to write to the registry,
that should solve the permissions issue without having to make all of
your users administrators. Most registry keys are not left "open" for an
entire session, but are opened just long enough to read or write a
value. Are you now saying that you have tried this by running a .reg
file from a startup script?
....kurt