Upgrading Enterprise clients to XP SP2

I have to update ~10,000 XP systems to XP SP2.
I already have SUS deployed in my enviroment, and have a WSUS server that I
will be deploying (so it can be used instead.)
The problem is this, when I tried deploying the update for a testbed of 50
users (that WERE warned that the upgrade would be taking place sometime this
week) two of them RESTARTED their computers during the update (saying that
the computer was running slowly so they rebooted) which caused their system
to come up to the BSOD (Blue Screen Of Death), and gave our help desk one
more thing to do.
So the quesiton is this:
Is there a way for me to deploy the update via SUS (or WSUS) without having
to worry about users rebooting? If this happened with 2 out of 50, I don't
want to find out how bad it would be for 10,000 users/systems.
I created a script that would give them a warning, and then install the
update (bypassing SUS), but even with copying the install files locally
first, it still takes 40 minutes for the install to complete, and there's
still the risk of the user restarting. Is there any way to speed the
scripted install up? I don't know if it's even possible to get the install
down to 5-10 minutes per computer.

Any thoughts/ideas would be VERY much appreciated.

THANKS

Forwarded to microsoft.public.softwareupdatesvc via crosspost.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE, Shell/User, Security), Aumha.org VSOP, DTS-L.org

Dan wrote:
> I have to update ~10,000 XP systems to XP SP2.
> I already have SUS deployed in my enviroment, and have a WSUS server that
> I will be deploying (so it can be used instead.)
> The problem is this, when I tried deploying the update for a testbed of 50
> users (that WERE warned that the upgrade would be taking place sometime
> this week) two of them RESTARTED their computers during the update
> (saying that the computer was running slowly so they rebooted) which
> caused their system to come up to the BSOD (Blue Screen Of Death), and
> gave our help desk one more thing to do.
> So the quesiton is this:
> Is there a way for me to deploy the update via SUS (or WSUS) without
> having to worry about users rebooting? If this happened with 2 out of
> 50, I don't want to find out how bad it would be for 10,000 users/systems.
> I created a script that would give them a warning, and then install the
> update (bypassing SUS), but even with copying the install files locally
> first, it still takes 40 minutes for the install to complete, and there's
> still the risk of the user restarting. Is there any way to speed the
> scripted install up? I don't know if it's even possible to get the
> install down to 5-10 minutes per computer.
>
> Any thoughts/ideas would be VERY much appreciated.
>
> THANKS

Is it possible to update these workstation during offshift hours? By this I
mean, if the compliment of users are 7AM to 6PM, can you trust them to
logoff at night so the machine can be updated by the automatic updates
client during the night?

"PA Bear" <> wrote in message
news:...
> Forwarded to microsoft.public.softwareupdatesvc via crosspost.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE/OE, Shell/User, Security), Aumha.org VSOP, DTS-L.org
>
> Dan wrote:
>> I have to update ~10,000 XP systems to XP SP2.
>> I already have SUS deployed in my enviroment, and have a WSUS server that
>> I will be deploying (so it can be used instead.)
>> The problem is this, when I tried deploying the update for a testbed of
>> 50
>> users (that WERE warned that the upgrade would be taking place sometime
>> this week) two of them RESTARTED their computers during the update
>> (saying that the computer was running slowly so they rebooted) which
>> caused their system to come up to the BSOD (Blue Screen Of Death), and
>> gave our help desk one more thing to do.
>> So the quesiton is this:
>> Is there a way for me to deploy the update via SUS (or WSUS) without
>> having to worry about users rebooting? If this happened with 2 out of
>> 50, I don't want to find out how bad it would be for 10,000
>> users/systems.
>> I created a script that would give them a warning, and then install the
>> update (bypassing SUS), but even with copying the install files locally
>> first, it still takes 40 minutes for the install to complete, and there's
>> still the risk of the user restarting. Is there any way to speed the
>> scripted install up? I don't know if it's even possible to get the
>> install down to 5-10 minutes per computer.
>>
>> Any thoughts/ideas would be VERY much appreciated.
>>
>> THANKS
>

No, unfortunatly that's not possible. We have more then a few sites where
users are working 24/7.
Also with the number of users, there would be too many that shut down their
computers. We also have a lot of tiered hour workers. Where some are
working 6-3 while others are 12-9, etc.

"neo [mvp outlook]" wrote:

> Is it possible to update these workstation during offshift hours? By this I
> mean, if the compliment of users are 7AM to 6PM, can you trust them to
> logoff at night so the machine can be updated by the automatic updates
> client during the night?
>
> "PA Bear" <> wrote in message
> news:...
> > Forwarded to microsoft.public.softwareupdatesvc via crosspost.
> > --
> > ~Robear Dyer (PA Bear)
> > MS MVP-Windows (IE/OE, Shell/User, Security), Aumha.org VSOP, DTS-L.org
> >
> > Dan wrote:
> >> I have to update ~10,000 XP systems to XP SP2.
> >> I already have SUS deployed in my enviroment, and have a WSUS server that
> >> I will be deploying (so it can be used instead.)
> >> The problem is this, when I tried deploying the update for a testbed of
> >> 50
> >> users (that WERE warned that the upgrade would be taking place sometime
> >> this week) two of them RESTARTED their computers during the update
> >> (saying that the computer was running slowly so they rebooted) which
> >> caused their system to come up to the BSOD (Blue Screen Of Death), and
> >> gave our help desk one more thing to do.
> >> So the quesiton is this:
> >> Is there a way for me to deploy the update via SUS (or WSUS) without
> >> having to worry about users rebooting? If this happened with 2 out of
> >> 50, I don't want to find out how bad it would be for 10,000
> >> users/systems.
> >> I created a script that would give them a warning, and then install the
> >> update (bypassing SUS), but even with copying the install files locally
> >> first, it still takes 40 minutes for the install to complete, and there's
> >> still the risk of the user restarting. Is there any way to speed the
> >> scripted install up? I don't know if it's even possible to get the
> >> install down to 5-10 minutes per computer.
> >>
> >> Any thoughts/ideas would be VERY much appreciated.
> >>
> >> THANKS
> >
>
>
>

The only other option I can see using WSUS/automatic updates client is not
to force a scheduled install but allow the user to select the "install
updates on shutdown" when they close out for the night. Again, still not a
perfect solution because it relies on the end user making the right choice
or still impacting a 24/7 workstation that needs to incur the 20 to 30
minute install + reboot, but if the site can take some time for the sales
pitch and user training/education, it could work.

Outside of that and considering the size of the site with 10,000
workstations is to use some other method. For example SMS where the
machines can be woken up, update applied, and then shutdown.

"Dan" <> wrote in message
news:3AAEA0D2-1347-4FA1-899C-...
> No, unfortunatly that's not possible. We have more then a few sites where
> users are working 24/7.
> Also with the number of users, there would be too many that shut down
> their
> computers. We also have a lot of tiered hour workers. Where some are
> working 6-3 while others are 12-9, etc.
>
> "neo [mvp outlook]" wrote:
>
>> Is it possible to update these workstation during offshift hours? By
>> this I
>> mean, if the compliment of users are 7AM to 6PM, can you trust them to
>> logoff at night so the machine can be updated by the automatic updates
>> client during the night?
>>
>> "PA Bear" <> wrote in message
>> news:...
>> > Forwarded to microsoft.public.softwareupdatesvc via crosspost.
>> > --
>> > ~Robear Dyer (PA Bear)
>> > MS MVP-Windows (IE/OE, Shell/User, Security), Aumha.org VSOP, DTS-L.org
>> >
>> > Dan wrote:
>> >> I have to update ~10,000 XP systems to XP SP2.
>> >> I already have SUS deployed in my enviroment, and have a WSUS server
>> >> that
>> >> I will be deploying (so it can be used instead.)
>> >> The problem is this, when I tried deploying the update for a testbed
>> >> of
>> >> 50
>> >> users (that WERE warned that the upgrade would be taking place
>> >> sometime
>> >> this week) two of them RESTARTED their computers during the update
>> >> (saying that the computer was running slowly so they rebooted) which
>> >> caused their system to come up to the BSOD (Blue Screen Of Death), and
>> >> gave our help desk one more thing to do.
>> >> So the quesiton is this:
>> >> Is there a way for me to deploy the update via SUS (or WSUS) without
>> >> having to worry about users rebooting? If this happened with 2 out of
>> >> 50, I don't want to find out how bad it would be for 10,000
>> >> users/systems.
>> >> I created a script that would give them a warning, and then install
>> >> the
>> >> update (bypassing SUS), but even with copying the install files
>> >> locally
>> >> first, it still takes 40 minutes for the install to complete, and
>> >> there's
>> >> still the risk of the user restarting. Is there any way to speed the
>> >> scripted install up? I don't know if it's even possible to get the
>> >> install down to 5-10 minutes per computer.
>> >>
>> >> Any thoughts/ideas would be VERY much appreciated.
>> >>
>> >> THANKS
>> >
>>
>>
>>