Why do I have to reboot a Server 2003 and not a WinXP when update

[Guest jk]

Hallo,

 

I have 10 Server 2003 and 6 WinXP in a network. They are updated by WSUS and

it's works fine. The problem is that reboot for the machines are very

critical. It seem that the WinXP computers don't need to reboot every time an

update has been installed bu the Servers allways need at reboot! Why this

difference and can change some settings on the Servers 2003 so I not allways

need to reboot?

 

Thanks in advance

JK

[Guest Roger Abell [MVP]]

If a reboot is seen as needed it should be done. There are MS docs

that mention how after MU or WSUS delivered updates if reboot is

needed the machine is in an intermediate, and potentially unstable,

state until the reboot is done.

A given fix, in its W2k3 and XP versions might need a reboot on

one system and not on another, even if both are W2k3 or both XP.

This depends on such things as what is in use at the time.

A server usually has more things going on at any given moment.

 

Roger

 

"jk" <jk@discussions.microsoft.com> wrote in message

news:CAAC753D-8A82-4797-AF89-861CF629B0D0@microsoft.com...

> Hallo,

>

> I have 10 Server 2003 and 6 WinXP in a network. They are updated by WSUS

> and

> it's works fine. The problem is that reboot for the machines are very

> critical. It seem that the WinXP computers don't need to reboot every time

> an

> update has been installed bu the Servers allways need at reboot! Why this

> difference and can change some settings on the Servers 2003 so I not

> allways

> need to reboot?

>

> Thanks in advance

> JK

>