Blog

DST preparations - step 1, read technotes and run in circles. No, ok really here we go...


Tags :


So reading the technotes we have some gaps in what will transpire and in what order at most customer sites.  A lot of this relies on the ability, or timing, of getting the desktop operating system patched.  If you follow the simple step plan in technote #1254624 you will see that (1) the server OS gets patched, (2) then the Domino version (if possible), (3) the JTZU for Sametime servers or other Java dependent apps and then it gets fuzzy.

(4) is in relation to putting the OS patch on the clients.  For one thing, Lotus suggests that the Notes client is closed when the patch is applied.  How many of your users leave the client open all night long?

The computer should be restarted after the patch is applied and before restarting Notes.  If the computer is not restarted after installing the patch, Notes will return the old time zone information for time zones other than the current time zone.

A lot is riding on this client restart or even patching.  I am also not sure how you are forcing your users with machines at home or laptops to do it.  If you start scheduling meetings across the clients that do and do not have the OS patch, then you will get variances in what they see and how correct they are.

Now to toss in some confusion, (5) should be done as soon as possible in relation to the OS updates.  This is finely designed and choreographed dance folks.  The amount of errors that DWA users will get relies heavily on this.  See technote #1241063 for the alternative issues.  From simple error pop-ups to meetings getting scheduled in Greenwich Mean Time, I think we have a problem here.  There is no way to get all those DWA user machines.

(6) moves on to the RnR database and the users mailfiles.  Now, if the users have local replicas also, they should be grabbing the change agent through replication before you run it on the server too.  See technote #1254639.  The RnR Manager must be shut down when the agent runs, and you even get a prompt while running this from the database Action menu.  Note, you will be signing these agents with some id file that needs at least editor access to the RnR database.

I will have more info for you to follow this one as we finalize and formulate the plan to update servers globally, hopefully it helps.