DescentBB

Anyone else gonna be manually patching their PCs at work for this?

I have to patch twice, once for XP and once for Outlook and the obvious servers also.

We are not on Active Directory yet so it's not as easy.

fun ain't it?

We're making a script to scan our subnet and let us know which ones are alive, then another script to remotely push the patch to the PCs.

W00p @ scripting.

Canada hopped on board too? I think it's a really bad idea. I mean, yay for it being light until 7pm, but now I have to throw out all my clocks because they set themselves over the radio, and aren't ready for the DST change.

It's a conspiracy, I tells ya!

If the US changes something like time, then trust me, we will follow.

I work in IT for a college university... Our server admins released the Outlook patch to the WSUS server as well as patching our Exchange servers. There were a very small percentage (Me included) of people that has Outlook 2003, were patched successfully and still had all of their Calendar apointments moved back an hour for the 1st 3 weeks of the new DST period.

Yaarrr!

It is a pain b ut not as hard as I originally thought. We have 2 patches to push. The Windows one and the Outlook one. We don't have an Exchange server yet so we don't have to worry about that.

The longest part is updating all the blackberries etc.

I look at it this way...

\"The more they over work the plumbing, the easier it is to stop up the drain.\"

This too (just like the \"Y2K bug\") will pass and we'll all get to go back to what we really should be doing.

I patched my work computer, outlook and my pda at work in 15 minutes, and when I got home, I patched my computers, took 15 minutes.

No headache for me.

from what im reading WinXP will fix itself right?

whats the deal here?

Testiculese wrote:I patched my work computer, outlook and my pda at work in 15 minutes, and when I got home, I patched my computers, took 15 minutes.

No headache for me.

Patching single PCs is easy. Patching 300 is different.