Command prompt: W32tm /tz should return: [Standard Name<Your timezone> Bias: 0min Date:(M:11 D:1 DoW:0)] [Daylight Name <Your timezone> Bias:-60min Date:(M:3 D:2 DoW:0)]
For Daylight Savings The M:3 D:2 DoW:0 means 2nd Sunday of March and should NOT say M:4 D:1...if it does, it needs a DST patch. I used PSEXEC to check several servers w/out having to RDP in each one. Dave Lum - Systems Engineer [EMAIL PROTECTED] - (971)-222-1025 "When you step on the brakes your life is in your foot's hands" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2008 4:58 AM To: NT System Admin Issues Subject: Re: DST adjustment Could it be getting its time from either a DC or other server which is "off"? -------------------------------------- Richard McClary, Systems Administrator ASPCA Knowledge Management 1717 S Philo Rd, Ste 36, Urbana, IL 61802 217-337-9761 http://www.aspca.org "Greg Page" <[EMAIL PROTECTED]> wrote on 03/09/2008 06:48:23 AM: > Windows XP SP 2 fully patched. My computer was off Saturday and I > didn't turn it back on until Sunday morning. The first thing I > noticed was that the time was still set to Standard Time, I figured > it would reset but it didn't, so I rebooted. The time still is at > Standard time. Anyone else experience this? > > It has always worked correctly in the past. > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
