GP cumulative effect and SUS

[Rich]

We've been using SUS at work for about a month now with
weekly reboots and updates occurring without incedent so
far...

What I'm wondering is if I create another GP with only
the Windows Update sections configured and apply it to
the same container as my normal GP, can I effectively get
TWO schedules for SUS to auto-install and reboot? I'd
like them about 2-3 hours apart because what I'm seeing
is updates being installed and then more updates
immediately in the queue that wait a whole week to get
deployed.

The question is - would one policy override the other, or
can I have a Windows Update section with TWO scheduled
install times?

My instinct is that one GP would override the other and
the cumulative effect would give me only one time for SUS
installs. Am I right?

 

[Ken]

I'd agree with you--you'll override one policy with
another and still have one scheduling. Why not bump up
the frequency to daily/nightly? We have it set to check
daily for updates at lunch time, when the user isn't
there. They've been fore-warned that they should save
their work before going to lunch... only hear complaints
the first one or two times someone's work gets lost, and
then they learn to save, and know we weren't kidding.

 

[Rich]

We could never schedule people to go to lunch at a
coordinated time around here! ;-)

The SUS server itself checks in the ealy morning each
day, and the desktops auto-updates are already set up by
default to check about once every day, so people already
have the globes on their trays for this weekends
updates. Some are savvy enough to just go ahead and
install and reboot manually from the update client.

But I agree that I'd probably get one schedule rather
than two. Too bad, too.