DSTshift

From CoolSolutionsWiki

> my other wikis

Contents

[edit]

November 2007

All,

The following outlines information on a bug that all GroupWise customers with DST ending in November will run into. Some customers are already been seeing this bug.

Please read the following if you have GroupWise customers and follow up with them as needed to prevent/minimize this issue.

This affects every North American Customer running GroupWise 7.x using the GroupWise Internet Agent (GWIA)

The GroupWise 7.x GWIA iCal code is incorrectly calculating the end of DST between November 4th and 24th. - Any appointments sent out from a GroupWise system or received by a GroupWise system will be posted one hour early for the recipients of those appointments. - Any appointments sent within the GroupWise system will be correctly posted.

Public information is in TID 3742804 - Appointments from external sources are 1 hour early between Nov 4th and 24th, 2007


TID 3742804 Appointments from external sources are 1 hour early between Nov 4th and 24th, 2007 - North America DST

Bug details can be found in Bug 304001.


https://bugzilla.novell.com/show_bug.cgi?id=304001 You must be an employee to view this

Note: All servers running GWIA need to be updated.

Updated GWIA code for NetWare and Windows is available at:


http://download.novell.com/Download?buildid=VJNHZg1Pdpc~

Please Note: The update above requires GroupWise 7.0.2 Hot Patch 1, 1A or 1A Rev A to already be applied. If one of those patches are not already applied, they need to be applied as well as this GWIA update.

Updated GWIA code for Linux has not yet been publicly released. You can download a 7.0.2 build from October 10th at:


US English only - ftp://ftp.novell.com/outgoing/groupwise_full_2007.10.10_us.tar.gz Multi Language - ftp://ftp.novell.com/outgoing/groupwise_full_2007.10.10_multi.tar.gz

All Linux servers running GWIA code need to be updated with all agents running on that server.

[edit]

What if I'm running GroupWise 6.5?

Please note that gw 6.5.7 does NOT have the option to import an ical appointment, thus it doesn't matter that there is no gwia patch to fix gwia ical for gw 6.5.x.

From my lab tests, I observed that 6.5 client (fat client nor web client) can NOT import an ical appointment. This is where the remaining DST bug remains, in receiving an internet ical msg through gwia. So, if you can't import the appointment, then you won't have any appointments that are off an hour. So, assuming the gwia is 6.5 and all the Post Offices are 6.5 (one can NOT connect a GW 7 client to a GW 6.5 Post Office), then you can't import the ical.

Sure, there may exist a scenario where you have a post office at 7 and thus a 7 client can connect to it and import the ical. With a 6.5 backend (that is not able to be patched for this issue).

Screen shots of GW 6.5 not being able to import ical appointments

[edit]

April 2007

[edit]

Checklist/sequence/order


Work-in-progress

  1. Patch MS windows workstations - all at the same time (or as near the same time as possible).
  2. Run dstshift on all NetWare servers - which updates the autoexec.ncf
  3. Run the correct tzupdater on ALL java.
    1. Be aware of the needed extra switch for MST, HST, EST. java -jar /tmp/tzupdater.jar -u -v -f -bc switch and manually delete the three files EST, MST and HST from the SYS:\java\lib\zi directory. For more details
    2. SLES IDM 3 java tzupdater
    3. ZENworks Desktop Mgmt - use the tzupdater, and NOT the updated JVM as it will break AWSI.
  4. GroupWise
    1. Update timezone info in the tools | groupwise system operations | time zone
      1. This requires a restart of ALL AGENTS to make this change into effect
    2. Do the necessary gwia and webaccess patches
    3. If your users posted GW appt. as an unpatched WS, you may consider running the DST gwcheck
  5. Patch consoleone
  6. See MASTER TID for other Novell product operations
[edit]

TIDs

  1. 3094409 (DST Master TID) Time zone and Daylight Saving Changes for Novell Products - 2006 and 2007.
  2. DST Changes and GroupWise End User Action required
    1. Novell is building a tool to help fix GW appt and you can download it March 1, 2007 from download.novell.com - it is part of gwcheck and must be run on all POs.
      1. GWcheck to fix appt. Released . After a test matrix has been completed it will be fully released (ETA March 2nd or 5th).
    2. GW DST BLOG from GW Engineering
    3. Daylight Saving Time Guide for Novell GroupWise May NOT be needed after March 1st
  3. Novell.com daylight savings page
  4. TID 3802376 NOTICE to GroupWise Customers: Daylight Saving Times are Changing in 2007 for most of the U.S. and Canadian Time Zones.
  5. TID 3867097 iManager Timezone change in United States and Canada 2007, Australia 2006
  6. 3397648 Daylight Savings Time shift tool - README
  7. For Linux: Review TID 3655154 and 3853518
  8. For NetWare: Review TID 3397648 and 2974702
  9. For IDM: Review TID 3950121
  10. URGENT March 12 UPDATE tzupdater defect - MST, EST, HST timezones action NEEDED
    1. Customers running Sun's Java on NetWare will need to run the tzupdater tool with the -f -bc switch and manually delete the three files EST, MST and HST from the SYS:\java\lib\zi directory
[edit]

non US timezones

Apparently, the early version of DSTSHIFT did not have the safe guard in it to limit the timezone which would be modified by the utility.

The fixed version: dstshift.nlm Version 1.00.00 Friday, December 08, 2006
http://support.novell.com/servlet/filefinder?name=dstshift.nlm

[edit]

Consoleone

To best minimize risk, the ConsoleOne core team has decided to address the DST change via a manual update to ConsoleOne 1.3.6f. See TID 3639513 for details. The engineering team has done extensive tests on this solution ... To date, no problems have been found.

ConsoleOne 1.3.6g will not be re-posted. Please make sure that no customers deploy it. This message will been sent to everyone that has downloaded it, as well.


[edit]

JVM considerations

[edit]

JVM Verification

A couple of ideas come to mind.
1) reading the readme - looks like there are two verification checks

1.1) In logger you'll see: "Validating the new time zone data... done"
1.2) 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.


[edit]

JRE for IDM on SLES 9

http://wiki.novell.com/index.php/DSTjreIDM

[edit]

DNS/DHCP Management Console

[edit]

Questions


Clarification on TID: 3621952

Customer is wondering, if he updates the server side - does he need to update the workstations?

My understanding is, you install from the server and then it is on your workstation from then on.

So, current ones will need to be updated. But will future ones need to be updated ?

He was saying something about a path not existing. NetWare: sys:\public\mgmt\DNSDHCP\jre\bin Windows: C:\Novell\DNSDHCP\jre\bin

He has NW servers, but installs the console to his workstation.


[edit]

Answers

Where ever the console is installed to - needs to have that specific JRE instance updated.

If he installed to his workstation - where did he install it to? Under that path location there will be a ..\jre\bin directory that should be used. The examples in the TID provide the default locations of this utility if installed that way. Quickly reviewing my setups, I probably should remove the NetWare path since this is normally installed to the workstation(s) only.

As for future updates to this console - I hope that they will include the updated Java. With all the discussions of late I expect that it will, although I have not heard a commitment to that. TEST

[edit]

Helpful Matrix spreadsheet

Operating System OS Glibc Version Glibc Required OS Patch No. Sun Java Required Patch No. IBM Java Required Patch No.
SLES8 2.2.5-235 2.2.5-235 10905 1.3.1_18-b01 1.3.1-18 - 1.3.1-229 1.3.1-237 11387
SLES9 2.3.3-98.73 2.3.3-98.61 10738 - 1.4.2-129.23 10920 1.4.2-0.68 1.4.2-0.76 11388
OES Linux 2.3.3-98.73 2.3.3-98.61 10738 - 1.4.2-129.23 10920 1.4.2-0.68 1.4.2-0.76 11388
SLES10 N/A N/A N/A N/A N/A N/A 2461
Operating System Action Sun Java Required Action
NW5.1 Apply DST NLM 1.3.1_06 tzupdater131.jar
NW6.0 SP3 Apply DST NLM 1.3.1_06 1.4.2_13 tzupdater131.jar
NW6.0 SP5 Apply DST NLM 1.3.1_10 1.4.2_13 tzupdater131.jar
NW6.5 Apply DST NLM 1.4.2_06 1.4.2_13 1.4.2_13 or tzupdater (sun)
Application: Action Java Location Who ?
iManager on NW Patch OS *
iManager on Linux tzupdater (Sun) /opt/novell/j2sdk<java_version>/bin Chris
Extend Patch Java /opt/novell/j2sdk<java_version>/bin Chris
ConsoleOne tzupdater (Sun) or move to 1.3.6g ..\1.2\jre\bin
C1 on Servers tzupdater (Sun) or Upgrade to 1.3.6g ..\1.2\jre\bin
ZFD N/A
ZAM Windows OS
ZPM Patch OS/Java
Oracle 9 Patch to 9.0.8 Chris
SNA on Linux N/A
* Done by NetWare patching.

Table generated by gnumerics - cool tool!

[edit]

My lab - screen shots of the procedure

my lab updated March 12 to include JVM 1.3.1_09 1.31.06


[edit]

Reported DST Problems

  1. Webaccess appt. were not right. It was found they had missed a very important step (Setting the GW system operations time zone change parameter).
  2. Another customer reported a problem running the DST gwcheck in aggressive mode on a user that had 3 calendars (GW cal, smart phone cal, and they sync'd to their MAC calendar) - then they deleted all the appt. in the cabinet.
  3. non-issue - Another customer suspected that the DST gwcheck messed up his frequent contacts (created 6 or so duplicate contacts - the dups had wrong email addresses). A more likely cause was that changing smart phones in the last 5 days and then changing back caused this issue.
  4. After March 11th, email messages (not appt.) show off by an hour - on the 2nd or 3rd reply. Fix : is to ensure you have updated the gw system operations time zone AND restart the agents. If that fails, the admin msg/threads may not be flowing down to the POA and a GW repair (rebuild) will be needed on THAT PO.
Retrieved from "http://wiki.novell.com/index.php/DSTshift"