• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

So WSUS screwed up and didn't push the DST updates

2Xtreme21

2Xtreme21

Diamond Member
My company's responsible for probably ~500 computers or so spread out over a bunch of clients, and turns out something "screwed up with WSUS" (which I take to believe someone wasn't keeping up with the updates as they are supposed to) and now we need to install the XP DST update manually on nearly every computer.

Question is, is there a way to write some sort of logon script that will execute the XP update .exe file if stored in a given location on a server? Could save me a lot of time and energy rather than going to 14 different locations in the next day (which is impossible for me anyway).
 
Yeah very easy to do with a vb script and AD. I know I have a script for something very similar, if I can find it before someone else chimes in I'll post it for ya...

Otherwise google can find it for ya
 
and turns out something "screwed up with WSUS" (which I take to believe someone wasn't keeping up with the updates as they are supposed to
Click to expand...

Pretty much.
I bet it was a blast when the servers were patched and the clients were failing kerbero's and wouldnt map drives or authenticate 😀

The funny thing is WSUS isnt hard to manage. Send the patch out and create a report that shows which machines have failed to update.

 
2Xtreme21, I'm sure there's a way to do this in AD scripts, a Windows AD expert should pipe up and tell you how. AD folks I know seem to be able to do nearly anything in a login script.

I must, however, say (Nelson Mundt voice): "ha ha"

All of my *IX boxen were no action required for this one. Windows folks I know had a frenzied week last week and are having a fairly rough week this week cleaning up all the random little things.

This is one of those times I'm happy to be an OS bigot 😉

n0cmonkey, for behind-the-curtain equipment, I agree with you that UTC is great. From a purely technical standpoint, time zones and DST are both silly. Time is universal, and moves forward. Any time-keeping systems that don't honor those properties is broken. But for end-user-facing systems, like desktop Windows boxen, you're just going to confuse folks if you don't use correct local time.
 
You must log in or register to reply here.
Back
Top