*** Reminder to Everyone ***
 

This weekend has the clocks springing forward one hour Sunday due to taking advantage of sun for energy efficiency, but your computer probably needs to be updated...

So if you have not run your MAC or Windows PC updates in a while - please do so....

For you Cisco people:

clock summer-time est recurring 2 Sun Mar 2:00 1 Sun Nov 2:00

to piggy back that if you are running windows 2000 or below microsoft is not putting out a patch but there is an exe you can download to make the fix

google tzedit.exe run it. change your timezone, apply, then change it back, apply.

Hehehehe - slightly more fun of your still stuck with Echange 2000 on W2K

This is what Ive been doing since mid dec. Fun aint it... :tm:

if you authenticate to a domain controller the workstations "should" get the right time

3517+ servers

Victor - I'm gonna call you "Patches" from now on :hihi:

Is the ramification that the clock on your computer will be wrong for a week? So you should use your watch?
I do understand that if you have a PIM it would have your schedule off by an hour but you're lucky if I write my appointments down never mind enter them.

The ramifications are that your time coordinated items can be pretty screwed up for 3 weeks now and one week in November.

Theoretical example - if your company's payroll kicks off every Thursday at what it thinks is 11:30pm at night to your bank but your bank has been updated and is already the next day, then your payroll misses the Fri 12:00am cut off and because the nature of banks over the weekend does not deposit til Monday (if it does at all)

Connecting international flights at airports not happening or not enough time between connections, supplies not showing where they are supposed to be when they are supposed to be, and computer report batch jobs that have their own time source yet rely on other jobs to be completed, environmental management systems that are hard coded with time zone settings that connot be updated and must be replaced.... List goes on...

F that john, I'm not the patch guy. I grant the "patch guy" the access to install his patches, then I boot him the phuck off my boxes. :angel:

windows 2000 domain workstations do not change even though they get their time from the domain controller...:wall: :wall: :wall: :wall:

still need to apply the tzedit.exe

thankfully we are mostly xp but its gonna be a long day none the less.

That would be Me :wall:

Having issues with Recurring appointments now.....Sux

Yeh - I know - Pony up the $4500 to M$ of upgrade to Exchange 2K3/7

If it were that cheap for us I'd have tried to get them to bite on it. But I did the math for us w/ a new server and we were looking at about $35k-$40k to upgrade.

It was like $8k in CAL's for an upgrade for us.

i havent tested it yet but i was just thinking if you set a group policy to not adjust for daylight savings (i don't even know if there is a gp for that, i assume there is) then maybe the 2000 boxes will sync with the domain controller correctly.

The times line up exactly an hour off. So it is using the DC as atime server but locally it still thinks that its adjusting for DST

I've been trying to get that Microsoft Exchange tool to work all day and it is a pain in the A$$....Its gonna be easier for me to visit everybody one by one and just run the Outlook tool

most annoying thing is they COULD have included it in an update.