Re: Domain Controller / Automatic Updates..



I'm with you 10,000% on this.... I **NEVER** allow an update to be
automatically installed on a non test server automatically.... Ever.... I
also am on the same page when it comes to re-booting. I've had a hard drive
fail on a cold re-boot. Also have seen BSODs. I've rebooted servers
remotely, but it's often early in the AM when I am planning to be at work in
an hour and on a server that isn't critical (second DC or one of multiple
load balanced Citrix servers)......

As to the failure to re-boot, sounds like a BIOS setting needs changing.....

--
Regards,
Hank Arnold

"Danny Sanders" <Danny.Sanders@xxxxxxxxxxxxxxxxx> wrote in message
news:emA0intYFHA.3620@xxxxxxxxxxxxxxxxxxxxxxx
> As important as a DC is to the entire network I tend to want to install
> the updates manually after testing them on a test server. I would do it on
> a weekend when I have time to recover from a bad patch.
>
> Read up on a patch, browse the news groups to see if others are having
> problems with a particular patch and see how it was solved. Make sure you
> have good system state and file backups. A current ERD, and if possible a
> third party server recovery application that supplies support on the
> weekends.
>
> In my experience the most critical/stressful time for an admin is the
> "reboot" after installing a patch, you really need to be at the server.
> You need to know what patch caused the "glitch" and you should be the
> first to know, and be there to fix it.
>
> What happens if you go on vacation and SUS installs a patch that crashes
> the server?
>
> hth
> DDS W 2k MVP MCSE
>
> "Blenky" <sblenkhorn@xxxxxxxxx> wrote in message
> news:1117203795.134878.295810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>> I have our domain controllers setup to check our internal SUS server
>> for updates that I have approved. It checks every morning for new
>> updates and then downloads and installs when there are new ones. My
>> issue is in the reboot of the server after installation. The domain
>> controllers have been getting the signal to reboot, but unfortunately
>> they never do, they actually shut off and then remain off until we
>> intervene and reboot them. Has any one else seen this?
>>
>> TIA,
>> Sean
>>
>
>


.



Relevant Pages

  • The patch killed my system!
    ... prompts for a reboot, I say "Yes"...boom! ... that reason more often than any other on a server. ... when a patch appears to cause a problem with your server its more likely ... Now I'm not saying this to discourage reports of problems with patches, ...
    (NT-Bugtraq)
  • Re: RDP to Server Broken After Security Patch
    ... A reboot was required after this patch. ... Windows Small Business Server 2008 Unleashed ... Remote desktop was working fine up until the reboot for the security patch. ...
    (microsoft.public.windows.server.sbs)
  • Re: clarification of cvsup process.
    ... >> I have a FreeBSD 6.0 server that I manage that is used as a DNS / mail ... >> patch as listed in the announcement, but the patch just seemed to hang, ...
    (freebsd-questions)
  • RE: Windows 2000 Sec rollup 2 patch -- Ouch!
    ... Well, after trying the patch on two servers, I'm 50/50 going on none. ... Upgrade of server #1 went fine, ... First the machine went into a repetitive reboot for about 3 times, ...
    (Bugtraq)
  • Re: Domain Controller / Automatic Updates..
    ... updates manually after testing them on a test server. ... Read up on a patch, browse the news groups to see if others are having ... What happens if you go on vacation and SUS installs a patch that crashes the ...
    (microsoft.public.windows.server.active_directory)