ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Windows & Network Issues >> General Windows & Network Issues >> Daylight Saving Time
http://www.istechforum.com/YaBB.pl?num=1172869442

Message started by Charlie Klihr on 03/02/07 at 13:04:02

Title: Daylight Saving Time
Post by Charlie Klihr on 03/02/07 at 13:04:02

I need to install a fix for DST on Novell 6.5 and associated Java software. I have downloaded DstShift.NLM and TzUpdater-1_0_1.zip (for Java). My question is; Do I need to do both of these on the file server? :-/ I assume I have to run some patch on each Windows PC also. Could not find any answer elsewhere.
Thanks for any advice........

Title: Re: Daylight Saving Time
Post by skyywalker on 03/28/08 at 22:59:00

I know it's a little late but here's my 2-cents anyway.

Yes, you should run DSTSHIFT.NLM on each server's console (or schedule it with the Remote Manager). If it gives you any problems, check the Time Zone SET parameter. If that doesn't help then check the log file, DSTLOG.TXT, which it creates in the same folder as the NLM.

Yes, you should run TzUpdater to update the NetWare Java Runtime Environment (JRE). OR you can try this alternate method suggested by Novell: (https://secure-support.novell.com/KanisaPlatform/Publishing/173/3980430_f.SAL_Public.html)

Quote:

Manually updating JVM time zone data on NetWare servers with JVM 1.4.x
Sun Microsystems Inc. has made a time zone updater tool available that can be used to manually update the existing time zone data on NetWare 6.5 and 6.0 servers running a JVM 1.4.x. This tool will only work with JVM 1.4.x

The following link documents this utility and provides a link to the Sun Java SE download site to obtain the utility:
http://java.sun.com/javase/tzupdater_README.html

1. download and extract the tool to a temporary directory

2. copy the tzupdater.jar file to a temporary directory on the SYS: volume of the NetWare 6.5 server

eg: sys:\temp\tzupdater.jar

3. update the current time zone information with the utility by entering the following at the server console prompt

java -jar /temp/tzupdater.jar -u -bc -v

If you have previously run this tool against Java, use the following command

java -jar /temp/tzupdater.jar -f -bc -v

4. check the results on the logger screen, which should be similar to the following:

java.home: SYS:\JAVA
java.vendor: Sun Microsystems Inc.
java.version: 1.4.2_09
JRE time zone data version: tzdata2003a
Embeded time zone data version: tzdata2006p
Extracting files... done.
Renaming directories... done.
Validating the new time zone data... done.
Time zone data update is complete.
java: Class /temp/tzupdater.jar exited successfully

5. Delete 3 files: EST, MST and HST, all contained in the SYS:\java\lib\zi directory. This is due to the bug found by SUN, referenced here:
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102836-1

An optional step prior to actually updating the time zone data would be to execute the "test" option of the utility (java -jar /temp/tzupdater.jar -t -v). This will generate lots of error messages in the logger screen indicating that time zones were not found or that a test failed. This is normal and expected.

This utility will create a new time zone information directory structure for Java which will take up about 1.7 MB of actual disk space. The existing directory will be renamed so a back out option does exist if needed. The existing time zone data directory will be renamed to sys:\java\lib\zi.tzdata2003a and the new directory will be sys:\java\lib\zi.The old directory can be deleted at a later time if desired to free up a bit of disk space.

For legit Windows XP or later PCs, you can get the DST patch from Windows Update or the Microsoft Download Center. For earlier versions of Windows you'll need to make the registry changes yourself OR use one of the many UNOFFICIAL patches - BOTH can be found with a quick Google search...BUT I HIGHLY suggest that you test the START and END dates and times and a test system (or a virtual machine) before deploying on your network.

I don't know if it'll help, but when I made the registry changes (Yes, I did it myself), switch to a different time zone, "Apply" the change, change back to my time zone (PST) and then "Apply" again to see the effect.

;)

Title: Re: Daylight Saving Time
Post by gtladmin on 04/01/08 at 09:16:36

Skywalker:

I confirm on both the Novell updates and also the Windows updates for the DST. I have Windows 2000 machines, and even after applying the "official" TZedit.exe file last year, about 6 systems didn't roll over this year. Had to go in, change the time zone to someplace like Monrovia, save that, note the system time changed to Monrovia time, then go back in and reset that to Eastern, apply, and it was the correct time. Shut down and restarted the computer, made sure when the user logged back in the time was correct. My XP systems were all OK.

Val

Title: Re: Daylight Saving Time
Post by skyywalker on 04/02/08 at 12:20:22

Hey Val:

Let me check it out. In the meantime I have a couple questions for you:

Are these 6 'problem' boxes the only W2k boxes you have, OR do you have some that did work AFTER applying TZEDIT?
When you ran TZEdit on the problem boxes, were you logged in as an Admin?
On the problem boxes, in the Novell Client Properties, go to the Advanced Settings tab. Is "Set Station Time" set to ON?

It's been a while, so I'm going to rig up my test box to refresh my memory...get back to you when I'm done.

Title: Re: Daylight Saving Time
Post by gtladmin on 04/02/08 at 13:07:38

The 6 are all Win2k only (out of about 25 total Win2k boxes). So most of them did indeed work after applying the TZEDIT program back when the DST was changed. Unsure why these six didn't roll, but in any event simply doing the manual fix worked. TZEDIT requires admin level to run, it will not work otherwise. And yes, set station time is set to ON on all machines by default.

Title: Re: Daylight Saving Time
Post by skyywalker on 04/16/08 at 13:28:17

Sorry it took so long to get back - my day job called!!! ;)

Anyway - I tried everything I could think of to get it to NOT work... no luck!

I'll look at it a little more this weekend, but the only suggestion that I can offer for now is to try it again. This time make a note of the steps you took from point where Windows starts. That way I can try to reproduce it here.

What service pack, if any, do you have installed on the Win2K boxes?

Also, you should turn off any anti virus and/or anti spyware software in case they're blocking changes to the registry.