Hi There,

I am relatively new to AD, and am interested in doing the following:

Setting up Organizational Units, by department, so that I can push out MS
Patch updates via Group Policies, and have some of the OU's automatically
install and reboot after the patches are installed, and other OU's NOT
automatically reboot, but just push the updates out and hold until they are
manually rebooted.

The reason for this is that we are also a laboratory, and restarting some
computers while testing is going on will cause significant problems,
including damage to some of our proprietary hardware, which we build
in-house.

Can anyone point me to articles or white papers on how to do what I'd like
to do, or, if this is an impractical approach, offer an alternative?

Best Regards,
David


--
David Reed
Nework Administrator
(E-Mail Removed)

Read the Software Update Services whitepaper, it details scenarios like you
describe.

There is also a SUS newsgroup: microsoft.public.softwareupdatesvcs

"David Reed" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi There,
>
> I am relatively new to AD, and am interested in doing the following:
>
> Setting up Organizational Units, by department, so that I can push out MS
> Patch updates via Group Policies, and have some of the OU's automatically
> install and reboot after the patches are installed, and other OU's NOT
> automatically reboot, but just push the updates out and hold until they
are
> manually rebooted.
>
> The reason for this is that we are also a laboratory, and restarting some
> computers while testing is going on will cause significant problems,
> including damage to some of our proprietary hardware, which we build
> in-house.
>
> Can anyone point me to articles or white papers on how to do what I'd like
> to do, or, if this is an impractical approach, offer an alternative?
>
> Best Regards,
> David
>
>
> --
> David Reed
> Nework Administrator
> (E-Mail Removed)
>
>