...
A note about the NOJava schedules: The patch schedules whose names contain the phrase NOJava exclude any Java Runtime Engine (JRE) updates, because a few third-party applications run correctly only when their preferred version of Java is not changed. Only if you have such an application should you choose a NOJava schedule, and in those cases, you can enhance your computer security by disabling Java in Web browsers: Look for a Java Control Panel with a Security tab and a setting titled "Enabled Java content in the browser" that you can uncheck. If doing this causes the application Web site to fail, just reverse your actions.
Panelbox |
---|
id | 4 |
---|
title | More detailed information is available about each of these schedules. |
---|
|
When software vendors release patches, Lumension tests them before making them available to the KBOX. This provides a second level of review to catch any potential problems. The KBOX downloads patches on a nightly basis. Carleton computers are set to check for patches on one of the following schedules: - Thursdays at 3:00 am
- this schedule is recommended for computers connected to the campus network at 3:00 am
- computers should automatically power on at 2:50 am (Wake on LAN)
- at 3:00 am the KBOX will detect and deploy patches
- the KBOX will suspend pending tasks after 3 hours
- if a patch is actively being installed at the 3 hour mark, it will continue installing
- if a reboot is required, users will be prompted to reboot. After 5 minutes a reboot will be forced and patching will continue
- Thursdays at 12:05 pm (Common Time)
- This schedule is recommended for computers connected to the campus network on Tuesday/Thursday from 12-1 pm
- Tuesday at 12:05 pm the KBOX will detect which patches need to be deployed
- no patches will be deployed at this time
- the KBOX will suspend pending tasks after 50 minutes
- Thursday at 12:05 pm the KBOX will deploy patches
- based on the patch list compiled on Tuesdays
- the KBOX will suspend pending tasks after 30 minutes
- if a patch is actively being installed at the 30 minute mark, it will continue installing
- if a reboot is required, users will be prompted to reboot but a reboot will not be forced
- Thursdays at 12:05 pm (Common Time) or next connection
- This schedule is recommended for highly-mobile computers, or computers that are rarely connected to the campus network
- Friday at 4:00 am the KBOX will detect which patches need to be deployed
- if the computer is not connected to the campus network at this time, a detect will run the next time it is connected
- no patches will be deployed at this time
- the KBOX will suspend pending tasks after 60 minutes
- Thursday at 12:05 pm the KBOX will deploy patches
- if the computer is not connected to the campus network at this time, a deploy will run the next time it is connected
- based on the patch list compiled previously
- the KBOX will suspend pending tasks after 30 minutes
- if a patch is actively being installed at the 30 minute mark, it will continue installing
- if a reboot is required, users will be prompted to reboot but a reboot will not be forced
- Thursdays at 5:00 pm
- this schedule is recommended for computers connected to the campus network at 5:00 pm
- at 5:00 pm the KBOX will detect and deploy patches
- the KBOX will suspend pending tasks after 5 hours
- if a patch is actively being installed at the 5 hour mark, it will continue installing
- if a reboot is required, users will be prompted to reboot. After 5 minutes a reboot will be forced and patching will continue
- Fridays at 11:00 am (Convo)
- This schedule is recommended for computers connected to the campus network on Thursday from 12-1 pm and Friday 11 am - 12 pm
- Thursday at 12:05 pm the KBOX will detect which patches need to be deployed
- no patches will be deployed at this time
- the KBOX will suspend pending tasks after 50 minutes
- Friday at 11:00 am the KBOX will deploy patches
- based on the patch list compiled on Thursdays
- the KBOX will suspend pending tasks after 30 minutes
- if a patch is actively being installed at the 30 minute mark, it will continue installing
- if a reboot is required, users will be prompted to reboot but a reboot will not be forced
|
How do I tell if my machine is on a patch schedule?
...