Re: How to configure daylight saving time for the United States in
- From: MPaquette <MPaquette@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Feb 2007 11:05:20 -0800
Yes. I can successfully run the .reg while logged in as a local
administrator. I am just ticked that Microsoft published a fix like the one
in the article I referenced knowing full well it wouldn't work because of
registry keys being locked.
"Kurt" wrote:
MPaquette wrote:.
That is correct. In my initial post I mentioned that I followed theThen the next question is if you run the .reg when logged on as a
instructions for Method 1 in this article:
http://support.microsoft.com/default.aspx?scid=kb;[LN];914387 but when I
reboot my test PC I get a pop-up saying "Not all data was successfully
written to the registry. Some keys are open by the system or other
processes." Method1 walks you through exporting registry keys, creating a
startup script, etc. It doesn't work.
"Kurt" wrote:
MPaquette wrote:
Like I said in my original post, this doesn't work. An error message appearsYou didn't say in your original post that you deployed it by running a
saying ""Not all data was successfully
written to the registry. Some keys are open by the system or other
processes."
"Florian Frommherz" wrote:
Howdie!
MPaquette wrote:
I already tried creating a *.reg file but a normal user cannot update thoseYou don't have to.
specific registry keys. How are people going to visit hundreds of machines
where normal users don't have local administrator access? What a nightmare.
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.
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
administrator does it work? Perhaps the key(s) in question are open
during the time that the startup script runs. (Not that that's a
solution, just trying to narrow down the root of the problem).
....kurt
- References:
- Re: How to configure daylight saving time for the United States in 200
- From: Florian Frommherz
- Re: How to configure daylight saving time for the United States in
- From: Florian Frommherz
- Re: How to configure daylight saving time for the United States in
- From: Kurt
- Re: How to configure daylight saving time for the United States in
- From: MPaquette
- Re: How to configure daylight saving time for the United States in
- From: Kurt
- Re: How to configure daylight saving time for the United States in 200
- Prev by Date: Re: How to configure daylight saving time for the United States in
- Next by Date: Applying Computer settings takes a longtime <1169866297.835873.206430@s48g2000cws.googlegroups.com>
- Previous by thread: Re: How to configure daylight saving time for the United States in
- Next by thread: Re: Password Policy
- Index(es):
Relevant Pages
|
Loading