Time zone group policy change not working properly

I followed "Method 1: Change the time zone settings on multiple networked
computers", in http://support.microsoft.com/kb/914387, but my Windows 2000
systems will only reflect the changes once the time zone is manually changed
to a different time zone, then changed back to the original time zone. The
article doesn't say that this is required for this method, and fairly
certain that it's not.

This problem is occurring on systems that run the group policy startup
script as specified in "Method 1". The script runs successfully, and we get
the "DST 2007 Registry Update and Refresh has been executed on this
computer. Current time zone is: Time_zone_name" in the event log.

A manual time zone change isn't needed if the registry file and script are
run later after logging into the system. Although the article doesn't
mention setting specific security on the group policy, I've verified that
the authenticated users group has the "apply group policy" right.

Please help!

I found that by running the refresh VBScript twice the issue was resolved in
my environment. So the process was to import the REG file, wait 10 seconds
(wscript.sleep 10000), run the refresh one time, sleep again for 10 seconds
and run the refresh again.



"Oran Turner" wrote:

> I followed "Method 1: Change the time zone settings on multiple networked
> computers", in http://support.microsoft.com/kb/914387, but my Windows 2000
> systems will only reflect the changes once the time zone is manually changed
> to a different time zone, then changed back to the original time zone. The
> article doesn't say that this is required for this method, and fairly
> certain that it's not.
>
> This problem is occurring on systems that run the group policy startup
> script as specified in "Method 1". The script runs successfully, and we get
> the "DST 2007 Registry Update and Refresh has been executed on this
> computer. Current time zone is: Time_zone_name" in the event log.
>
> A manual time zone change isn't needed if the registry file and script are
> run later after logging into the system. Although the article doesn't
> mention setting specific security on the group policy, I've verified that
> the authenticated users group has the "apply group policy" right.
>
> Please help!
>
>
>

Will,

Amazingly enough, I had discovered the same thing and was returning here to
post the fix! Actually we found that it's not necessary to pause. Simply
running the script twice works every time...so our .cmd file reads:

@echo off
regedit /s \\domain\netlogon\TZupdate.reg
cscript \\domain\netlogon\refreshTZinfo.vbs
cscript \\\domain\netlogon\refreshTZinfo.vbs

Oran Turner



"Will" <Will@discussions.microsoft.com> wrote in message
news:6AB271F8-4A03-4EA8-B24B-AC3DFE8F8B85@microsoft.com...
>I found that by running the refresh VBScript twice the issue was resolved
>in
> my environment. So the process was to import the REG file, wait 10
> seconds
> (wscript.sleep 10000), run the refresh one time, sleep again for 10
> seconds
> and run the refresh again.
>
>
>
> "Oran Turner" wrote:
>
>> I followed "Method 1: Change the time zone settings on multiple networked
>> computers", in http://support.microsoft.com/kb/914387, but my Windows
>> 2000
>> systems will only reflect the changes once the time zone is manually
>> changed
>> to a different time zone, then changed back to the original time zone.
>> The
>> article doesn't say that this is required for this method, and fairly
>> certain that it's not.
>>
>> This problem is occurring on systems that run the group policy startup
>> script as specified in "Method 1". The script runs successfully, and we
>> get
>> the "DST 2007 Registry Update and Refresh has been executed on this
>> computer. Current time zone is: Time_zone_name" in the event log.
>>
>> A manual time zone change isn't needed if the registry file and script
>> are
>> run later after logging into the system. Although the article doesn't
>> mention setting specific security on the group policy, I've verified that
>> the authenticated users group has the "apply group policy" right.
>>
>> Please help!
>>
>>
>>

Good deal!

Will

"Oran Turner" wrote:

> Will,
>
> Amazingly enough, I had discovered the same thing and was returning here to
> post the fix! Actually we found that it's not necessary to pause. Simply
> running the script twice works every time...so our .cmd file reads:
>
> @echo off
> regedit /s \\domain\netlogon\TZupdate.reg
> cscript \\domain\netlogon\refreshTZinfo.vbs
> cscript \\\domain\netlogon\refreshTZinfo.vbs
>
> Oran Turner
>
>
>
> "Will" <Will@discussions.microsoft.com> wrote in message
> news:6AB271F8-4A03-4EA8-B24B-AC3DFE8F8B85@microsoft.com...
> >I found that by running the refresh VBScript twice the issue was resolved
> >in
> > my environment. So the process was to import the REG file, wait 10
> > seconds
> > (wscript.sleep 10000), run the refresh one time, sleep again for 10
> > seconds
> > and run the refresh again.
> >
> >
> >
> > "Oran Turner" wrote:
> >
> >> I followed "Method 1: Change the time zone settings on multiple networked
> >> computers", in http://support.microsoft.com/kb/914387, but my Windows
> >> 2000
> >> systems will only reflect the changes once the time zone is manually
> >> changed
> >> to a different time zone, then changed back to the original time zone.
> >> The
> >> article doesn't say that this is required for this method, and fairly
> >> certain that it's not.
> >>
> >> This problem is occurring on systems that run the group policy startup
> >> script as specified in "Method 1". The script runs successfully, and we
> >> get
> >> the "DST 2007 Registry Update and Refresh has been executed on this
> >> computer. Current time zone is: Time_zone_name" in the event log.
> >>
> >> A manual time zone change isn't needed if the registry file and script
> >> are
> >> run later after logging into the system. Although the article doesn't
> >> mention setting specific security on the group policy, I've verified that
> >> the authenticated users group has the "apply group policy" right.
> >>
> >> Please help!
> >>
> >>
> >>
>
>
>

I just wanted to say thanks for the tip. I thought I was losing it
( The event log even said it worked, though it didn't change) That fix
worked for me too. I just ran the script twice in a row and now it's
working- thanks!

If you are having problems with TZUPDATE not working, as I was, and you are receiving the error message that "not all data was sucessfully written..." I have found that you are placing the script in the wrong area in active directory. I could not figure this out for 3 days and I finally got it to work. you have to make sure that in your Group Policy, you ONLY have the script under the "computer configuration, windows settings, scripts, startup"! DO not put it under USER configuration. It is a machine startup script, and if you place it in the machine startup scripts and then just reboot your machines, it will automatically apply the update, and you will notice the clock change on login, even for non-admin users.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com