I followed the 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."

Anyone else try to use this method and get success? I really don't want to
change the time zone on 500+ PC's manually.

MPaquette wrote:
> I followed the 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."
>
> Anyone else try to use this method and get success? I really don't want to
> change the time zone on 500+ PC's manually.
Likely, your user account doesn't have permission to write to those
registry keys or hives. Be sure you are logged on as as administrator.
Also, check out the free downloads at intelliadmin.com. They have a
daylight time fix.

....kurt

Howdie!

MPaquette wrote:
> I followed the 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."
>
> Anyone else try to use this method and get success? I really don't want to
> change the time zone on 500+ PC's manually.

Try creating a *.reg file with the changes for the machines and call it
within a Group Policy startup script. A startup script will have
sufficient rights to make the changes in the corresponding registry nodes.

You could also write a custom ADM template - I'm sure someone else did
that before... maybe google or any other search engine might help you out.

cheers,

Florian
--
Nachwuschsadmin aus dem Süddeutschen/Germany.
eMail: Vorname [bei] frickelsoft [Punkt] net.
blog: http://www.frickelsoft.net/blog.

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.

"Florian Frommherz" wrote:

> Howdie!
>
> MPaquette wrote:
> > I followed the 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."
> >
> > Anyone else try to use this method and get success? I really don't want to
> > change the time zone on 500+ PC's manually.
>
> Try creating a *.reg file with the changes for the machines and call it
> within a Group Policy startup script. A startup script will have
> sufficient rights to make the changes in the corresponding registry nodes.
>
> You could also write a custom ADM template - I'm sure someone else did
> that before... maybe google or any other search engine might help you out.
>
> cheers,
>
> Florian
> --
> Nachwuschsadmin aus dem Süddeutschen/Germany.
> eMail: Vorname [bei] frickelsoft [Punkt] net.
> blog: http://www.frickelsoft.net/blog.
>

Most companies don't give users local admin rights to their PC. This is
going to be a major problem. I looked at the patch you mentioned on
intelliadmin.com but it's an EXE which can't be pushed out using Group Policy
and you have to be an admin to install it. What a mess.

"Kurt" wrote:

> MPaquette wrote:
> > I followed the 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."
> >
> > Anyone else try to use this method and get success? I really don't want to
> > change the time zone on 500+ PC's manually.
> Likely, your user account doesn't have permission to write to those
> registry keys or hives. Be sure you are logged on as as administrator.
> Also, check out the free downloads at intelliadmin.com. They have a
> daylight time fix.
>
> ....kurt
>

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.

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."

"Florian Frommherz" wrote:

> 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.
>

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."
>
> "Florian Frommherz" wrote:
>
>> 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

That is correct. In my initial post I mentioned that I followed the
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 appears
> > 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 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
>

MPaquette wrote:
> That is correct. In my initial post I mentioned that I followed the
> 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 appears
>>> 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 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
>>
Then the next question is if you run the .reg when logged on as a
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