일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |
Tags
- LiveKD
- windows debugging tool
- windows media service
- Windows Server 2008
- Windows Server 2016 Hyper-v Cluster
- 인문고전
- cluster node as Domain controller
- 프로세스 CPU 사용량
- SQL Server 2012R2 FCI
- windows update
- Local TempDB
- windbg
- ftp7.5 장애조치 클러스터
- 작업관리자
- paged pool
- Session space
- nonpaged pool
- iSCSI target
- failover cluster
- 클러스터
- 안철수
- Hyper-V
- 터키여행
- dsquery
- Nested VM
- Windows Server 2016
- FTP7.5
- SQL Server 2008
- Xperf
- MSCS on VMWare
Archives
- Today
- Total
류짱:Beyond MySelf
Windows update 후 시스템을 바로 재 시작해야 하는가? 본문
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.
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
감사합니다.