Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.update_services
Thread: How WSUS handles machines in standby (S3) mode?

HTVi
TV Discussion Newsgroups

How WSUS handles machines in standby (S3) mode?
johnf 6/5/2007 2:21:00 PM
We are considering entering our workstations into standby mode during non
work hours. I would like to know if the WSUS clients would wake during the
scheduled time for either their detect time or install time? If not, are
there any solutions to allow for this?
Thanks
Re: How WSUS handles machines in standby (S3) mode?
"Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/5/2007 10:42:40 PM
"johnf" <johnf[ at ]discussions.microsoft.com> wrote in message
news:1D114E46-227C-49AE-A1F1-23662578167B[ at ]microsoft.com...
[Quoted Text]
> We are considering entering our workstations into standby mode during non
> work hours. I would like to know if the WSUS clients would wake during
> the
> scheduled time for either their detect time or install time?

Nope. Both events are local CPU driven events. If the CPU is in standby ==
nothing happens locally.

> If not, are there any solutions to allow for this?

You can use WakeOnLAN to trigger a wakeup event a few minutes before the
scheduled /installation/ event, to ensure that installations proceed as
scheduled.

Detections, however, occur at random intervals around the clock, every 22
hours (minus a random offset of 1-20%). If the machine is asleep, the
scheduled detection will be missed.

--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....


Re: How WSUS handles machines in standby (S3) mode?
DaveMills <DaveMills[ at ]newsgroup.nospam> 6/6/2007 6:16:13 PM
On Tue, 5 Jun 2007 17:42:40 -0500, "Lawrence Garvin \(MVP\)"
<onsitech[ at ]community.nospam> wrote:

[Quoted Text]
>"johnf" <johnf[ at ]discussions.microsoft.com> wrote in message
>news:1D114E46-227C-49AE-A1F1-23662578167B[ at ]microsoft.com...
>> We are considering entering our workstations into standby mode during non
>> work hours. I would like to know if the WSUS clients would wake during
>> the
>> scheduled time for either their detect time or install time?
>
>Nope. Both events are local CPU driven events. If the CPU is in standby ==
>nothing happens locally.

Many BIOS now have a wake up time setting. You could say set the BIOS to wake
the PC at say 7am (before work starts). This would allow you to actually
shutdown the PC rather than go to standby. Then they wake up at the designated
time and the missed install (if allowed to reschedule) will install some minutes
later. It also means the any software deployed will get installed at the startup
event and be done and dusted by the time the user arrives. The PC will be hot to
trot when the user arrives. If they come in very early then they will have to
wait for the startup events to complete.

>
>> If not, are there any solutions to allow for this?
>
>You can use WakeOnLAN to trigger a wakeup event a few minutes before the
>scheduled /installation/ event, to ensure that installations proceed as
>scheduled.
>
>Detections, however, occur at random intervals around the clock, every 22
>hours (minus a random offset of 1-20%). If the machine is asleep, the
>scheduled detection will be missed.
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
Re: How WSUS handles machines in standby (S3) mode?
johnf 6/11/2007 7:49:00 PM
Hi Lawrence thanks for your reply. Would you know where the time at which
the detections occur would be stored and when they are created? We have
other products that needed the PC to be "woken up" before hand and therefore
I created waitable timers, similar to the task scheduler with the wakeup
option. Perhaps this would be suitable for WSUS as well?
Thank you.

"Lawrence Garvin (MVP)" wrote:

[Quoted Text]
> "johnf" <johnf[ at ]discussions.microsoft.com> wrote in message
> news:1D114E46-227C-49AE-A1F1-23662578167B[ at ]microsoft.com...
> > We are considering entering our workstations into standby mode during non
> > work hours. I would like to know if the WSUS clients would wake during
> > the
> > scheduled time for either their detect time or install time?
>
> Nope. Both events are local CPU driven events. If the CPU is in standby ==
> nothing happens locally.
>
> > If not, are there any solutions to allow for this?
>
> You can use WakeOnLAN to trigger a wakeup event a few minutes before the
> scheduled /installation/ event, to ensure that installations proceed as
> scheduled.
>
> Detections, however, occur at random intervals around the clock, every 22
> hours (minus a random offset of 1-20%). If the machine is asleep, the
> scheduled detection will be missed.
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)
> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>
> Everything you need for WSUS is at
> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>
> And, almost everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
>
>
>
Re: How WSUS handles machines in standby (S3) mode?
Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/11/2007 8:16:47 PM
johnf wrote:

[Quoted Text]
> Hi Lawrence thanks for your reply. Would you know where the time at which
> the detections occur would be stored and when they are created? We have
> other products that needed the PC to be "woken up" before hand and therefore
> I created waitable timers, similar to the task scheduler with the wakeup
> option. Perhaps this would be suitable for WSUS as well?

Best option in this scenario would probably be to initiate detections to your
own schedule, using the command line:

wuauclt /detectnow

Remember not to schedule your clients for the same time. You need to introduce
some random factor to spread the load out.

One other alternative is to allow the detections and downloads to occur during
the day when the machines are on anyway, scheduling a wakeup just ahead of the
installation time.

Another would be to use a script to detect, download and install all applicable
updates. You could schedule a wakeup to run the script at a randomly chosen
time during the night.

Harry.

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen