티스토리 뷰

Windows update 적용 후 시스템은 바로 시작해야 한다는 당연히 생각은 했지만 왜 그래야 하는지 조금은 더 이유를 알수 있게 되었네용.....^^

MailBag: Should Servers Be Restarted As Soon As Possible After Updates Or Okay To Wait?
http://blogs.technet.com/b/askpfeplat/archive/2013/01/25/mailbag-should-servers-be-restarted-as-soon-as-possible-after-updates-or-okay-to-wait.aspx

If you suppress a restart after applying an update, then the update is not completely in place.   If this update were a security update, the system would remain vulnerable until the restart and completion of the update after boot.  How long should the restart be suppressed?  How long should a system remain vulnerable? 

In theory, you could apply updates, suppress the reboot, and wait an infinite period of time
However, the longer the restart suppression, the higher the chance that unpredictable things could happen…especially if we’re talking about multiple updates.  While suppressing a restart, there is no guarantee that there won’t be side effects based on what changes were applied and those that remain pending.  At least, I’m not aware of any. I certainly have observed system hangs or other odd behavior with systems of my customers when they’ve suppressed restarts.  However, I’ve seen these issues less with Windows Server 2008 and later as compared to Windows Server 2003 or older versions.  The moral of the story here is to restart as soon as you can after updates or changes that require it. 

Windows Update and Automatic Reboots
http://blogs.technet.com/b/mu/archive/2008/10/02/windows-update-and-automatic-reboots.aspx

감사합니다.

댓글
댓글쓰기 폼