Re: Server 2003 Automatic Updates
- From: "Anthony [MVP]" <anthony@xxxxxxxxxxxx>
- Date: Thu, 13 Aug 2009 14:03:37 +0100
Dave,
If you have configured them the same in the GUI and there are no policies then they should behave the same. I am not aware of any differences in the default behaviour.
If you definitely want them to install but not reboot (as distinct from download but not install) then you will need to set this in policy where there are more options.
Anthony,
http://www.airdesk.com
"Dave Mc" <DaveMc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:80C5C35A-1F98-4543-A7B1-ECB15D9140DA@xxxxxxxxxxxxxxxx
What I mean is, I built all servers myself and have not ever changed or.
created any group policies. All servers are configured the same in the AU
GUI in control panel to download and install automatically. Yet, they behave
differently. I would like them all to prompt for a reboot if update requires
it, not just reboot automatically after updates are installed. I don't
understand why or how they are acting differently
"Anthony [MVP]" wrote:
Dave,
Not quite sure what you mean.
The best place to configure this is in GPO. You can create policies for
different types of server. For example, utility servers might reboot
automatically. Citrix servers might reboot but at different times. SQL
servers or Mail servers might download but not reboot except manually.
If you have not configured them in GPO, then you just need to use the GUI to
set the options for each server, in Control Panel, Automatic Updates,
Anthony
http://www.airdesk.com
"Dave Mc" <DaveMc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF939687-3D90-4C1D-B9CA-5F0F1EB9E9B2@xxxxxxxxxxxxxxxx
> Where do I look for what is causing the difference in behaviour ?
>
> "Anthony [MVP]" wrote:
>
>> Dave,
>> The servers were probably just configured differently when they were
>> built.
>> Anthony,
>> http://www.airdesk.com
>>
>>
>> "Dave Mc" <DaveMc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:9869D183-6103-4652-AB5B-EE3F4C22217B@xxxxxxxxxxxxxxxx
>> > I have several servers. All of them are set to download and install
>> > updates
>> > at 3:00 am. Some of them do an automatic reboot when required by >> > the
>> > update
>> > but some of them don't--instead, when I log into them, they tell me >> > a
>> > restart
>> > is required and do I want to restart now or later. None of them >> > have
>> > had
>> > their default policies modified nor had any registry changes. Does >> > a
>> > server
>> > being a DC make a difference ? Now that I think about it, it's
>> > possible
>> > the
>> > two who give me the choice about restarting are both DC's.
>>
- References:
- Server 2003 Automatic Updates
- From: Dave Mc
- Re: Server 2003 Automatic Updates
- From: Anthony [MVP]
- Re: Server 2003 Automatic Updates
- From: Dave Mc
- Re: Server 2003 Automatic Updates
- From: Anthony [MVP]
- Re: Server 2003 Automatic Updates
- From: Dave Mc
- Server 2003 Automatic Updates
- Prev by Date: Re: Help proxy binds to wrong NIC
- Next by Date: Re: Shadow Copy
- Previous by thread: Re: Server 2003 Automatic Updates
- Next by thread: Inter-Site AD replication using Server 2003 via the Internet
- Index(es):
Relevant Pages
|
