Re: DST Updates - fun, fun

On Mar 12, 11:06 am, Jeff <J...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Afterworking hard to make sure that all systems on our network were patched,
(XP, sp2, Windows 2000 Pro/Server, 2003 Servers), we are experiencing strange
issues with this. Most XP machines received the daylight savingtimeupdate
via Windows Update as well as 2003 machines

When restarting machines, thesystemtimeis jumping ahead an additional
hour on top of the daylight savingtimeshift.

Example: Computertimereads 12:00 pm. This is the correcttimewithDST
2007. The basetimeof the computer would then be 11:00am (and ifDST2007
didn't exist, this would be the correcttime), with the additional hour added
in. When restarting asystem, thetimethen shifts to 1:00 pm.

As you can imagine, on a network, this is causing all sorts of minor issues,
but most of all it is annoying. And before anyone wastes theirtimeasking:

- all Windows XP, sp2 computers have been patched and verified.
- all Windows 2000 machines, including 2 servers, have been patched and
verified.
- all Windows 2003 Server machines (including our Global Catalog Server)
have been patched and verified.
- Exchange 2003 Server / Outlook clients, have had the Outlook Tool ran
against each mailbox to update calendar items.

On most computers, I have manually taken off the checkbox to update for
daylight savingtimechanges. This appears to prevent anyupdatesand shows
the correct,DST2007time.

My questions:
- I'm wondering if thesystemBIOS could be mistakenly shifting thesystemtimesomehow? So when thesystemrestarts, the BIOS has the correcttime,updatesWindows when it boots and then Windows shifts ahead an additional
hour to compensate forDST.

- Because we are on an ADS network that hastime-updating built in through
the WindowsTimeservice, all computers should eventually synchronize to the
correcttime. Does each computer then apply its own 1 hour shift to the UTC
(universaltime) applied by the server? Or does thetimesent by the server
override this?

Also, thesechangeswere not evident over the weekend when testing was done.
Any suggestions? Anyone experiencing a similar problem?

--
Thanks, Jeff

Hi Jeff,

I experienced a problem similar to yours. W2K server/domain, used
TZedit to modify DST on server. Time on some XP workstations updating
correctly, but some didn't. All patches applied. I verified the
server's TZ....toggled all settings multiple times, still failed.

Try this: Goto Start> Run> timedate.cpl on the W2K server and select
the appropriate TZ and apply.... I was simply double-clicking the
clock or going to the control panel which caused my problems.

Hope this helps!
Aric


.

Relevant Pages

  • Re: Fileserver question
    ... >> another box running both 9.0 and Windows. ... >> computers in the same room and connected to a router. ... otherwise you will need to run a DHCP server on one ... > of the machines, preferably the server, or give both machines static ...
    (alt.os.linux.suse)
  • nslookup times out on some WinXP clients
    ... Basically, nslookup times out on some Windows machines, but not on others. ... we currently have a Windows 2000 Server DNS & DHCP Server serving IP ...
    (RedHat)
  • Re: New: LanMan98 V2 Not connecting
    ... all) Windows machines, the computer name as found in the system ... essentially Windows was rejecting the connection because it hadn't ... LanMan98 appears to be one, ... uses a low-level message protocol called SMB (Server Message Block). ...
    (comp.sys.acorn.networking)
  • Re: How do I see users that logged in ?
    ... - I know W98 machines should be migrated, but there are to many hindrances: ... Each subdirectory contains sub-subdirectories like administration, drawings, ... I know you can use the $ to share in windows, ... Can you log on to the server as user X and log on localy as user Y ??? ...
    (microsoft.public.windows.server.general)
  • Re: DST Updates - fun, fun
    ... Most XP machines received the daylight savingtimeupdate ... all Windows XP, sp2 computers have been patched and verified. ... all Windows 2003 Server machines ... All patches applied. ...
    (microsoft.public.windowsxp.general)