So I always make sure they get applied when I see the icon on my work desktop. If I see them, they have been approved and pushed out by our server Admins. At home, I generally take a look for problems with them first, but normally just apply them all.
Background: We use Citrix servers, about 20 of them currently, not including those located at the disaster recovery site. Users connect to these when they log into One World from the plants. I do the same.
Come to find out that when a user is connected to a Citrix server that has windows updates waiting to be applied, the notification comes through to the users desktop, and WILL ALLOW THAT USER TO APPLY THEM!!! Some users can reboot, some cannot. I, being an administrator of sorts, can.
Imagine my surprise when I got suspicious earlier this month by having so many patches come my way. At first, I though it was patches to counter the trojan worm we had running rampant through the company, but noooo....
I started paying attention to exactly which patches were being applied, and found they were for Windows Server 2003, not an XP Desktop. Oops
Turns out, I've been applying patches out of cycle, AND rebooting servers while people were on them. Supposedly, the admins are working on a solution to this, but I'm still seeing the update notification. At least now I know what it is, and can avoid doing anything about it.
Way to go Me!
Eric the Grey
Background: We use Citrix servers, about 20 of them currently, not including those located at the disaster recovery site. Users connect to these when they log into One World from the plants. I do the same.
Come to find out that when a user is connected to a Citrix server that has windows updates waiting to be applied, the notification comes through to the users desktop, and WILL ALLOW THAT USER TO APPLY THEM!!! Some users can reboot, some cannot. I, being an administrator of sorts, can.
Imagine my surprise when I got suspicious earlier this month by having so many patches come my way. At first, I though it was patches to counter the trojan worm we had running rampant through the company, but noooo....
I started paying attention to exactly which patches were being applied, and found they were for Windows Server 2003, not an XP Desktop. Oops
Turns out, I've been applying patches out of cycle, AND rebooting servers while people were on them. Supposedly, the admins are working on a solution to this, but I'm still seeing the update notification. At least now I know what it is, and can avoid doing anything about it.
Way to go Me!
Eric the Grey
Comment