![]() ![]() If the AU client could not contact your WSUS server, you may see an Event ID 16 (see Figure 7.26), which may be an indication that there is a problem with that client's network card. Be sure you have downtime approved before using Deadlines during production hours Although your servers may be set to download and install updates during downtime hours, if you schedule a deadline for an update in the middle of the day, that installation will override all client settings and possibly reboot your server during production hours. ■ It is recommended that reboots be scheduled after critical- or security-related installations occur, by using either the AU option to reboot or by generating a custom reboot script.īe forewarned when using the Deadlines feature for approving AUs for your clients. Event ID 21 warns you if the computer is set to not reboot. ■ If you decide not to reboot your computers after you install critical- or security-related updates, your computer will not be patched yet and will still be vulnerable to bugs. This event warns you that until the computer is restarted, the updates have not taken effect and your computer is still vulnerable. Event 21 shows a successful installation that was unable to restart due to a logged-on administrator. Event ID 19 shows the successful installation of an update. ![]() It also shows the scheduled installation's date and time. This event shows the stopping and starting of the Event log, and is always shown after a machine is restarted.Įvent ID 18 shows that an update has been downloaded and is pending installation. Search for "Event ID 6006" in conjunction with "Event ID 6005," with significant time lapses in between. Another place to look for a computer restart is in the System Event log. The Event ID is a good place to search when investigating a computer reboot. ■ Cumulative Security Update for Internet Explorer G Service Pack 1
0 Comments
Leave a Reply. |