Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Computers at Carleton are automatically patched in a number of ways:

...

The KBOX receives patches from Lumension , a security company. These patches are then delivered to campus computers. Patches in the KBOX are security related patches only.  Feature related patches and upgrades are not available from KBOX patch management.

What patches are delivered by the KBOX?

The KBOX delivers security-based patches for the following applications:

  • Adobe AIR
  • Adobe Acrobat and Adobe Reader
  • Adobe Flash Player
  • Adobe Shockwave Player
  • Some Adobe CS3-CS6 patches
  • Citrix Receiver
  • Google Chrome (Windows)
  • Apple iTunes and QuickTime (Windows)
  • Apple Safari web browser (Windows)
  • Microsoft Silverlight and Remote Desktop (Mac)
  • Microsoft Office (Mac)
  • Mozilla Firefox and Firefox ESR
  • Oracle Java
  • VLC media player (Windows)
  • VMWare Fusion, Player, Workstation
  • WinZip and 7-Zip (Windows)

When are patches delivered by the KBOX?

When software vendors release patches, Lumension and KACE test them before making them available to the KBOX. This provides more levels of review to catch any potential problems. The KBOX downloads new patch signatures and patch package files for selected operating systems nightly. Then, Carleton computers use the available patches based on the patching schedule to which each computer is assigned. Some patch schedules check for ("detect") patches at one time, and then apply ("deploy") the detected patches at a different later time. Other patch schedules check for ("detect") patches and then apply them ("deploy") immediately thereafter.

There are 10 different patch schedules to which a computer can be assigned. Each computer, virtual machine (VM), and booting operating system (e.g., dual boot), should be assigned to one and only one patch schedule. Any VM or booting operating system on a computer should be assigned to a different schedule than the computer itself, so you can make sure the correct environment is running at the time of each schedule.

Panel
Note: We have found it is very difficult to explain these different patch schedules in writing, so please be patient in reviewing this section, and contact the ITS HelpDesk (x5999) when you have questions.

Here is a list of the different patch schedules each with a different color, and next to that is a picture of when the different steps (detect or deploy) of each patch schedule runs:

Section
Column
width40%

Image Removed

Column
width60%

Image Removed

Image Removed

What do I see when the patch schedule steps run?

When a patch schedule Detect only step runs, nothing is displayed. The computer may seem a bit sluggish, but you can keep working.

Every patch schedule Deploy step has these characteristics:

...

KBOX

...

This table lists the different patch schedules again with more detailed information:

Image Removed

Again, we know this information is hard to interpret. Please contact the ITS HelpDesk (x5999) for help.

Which patch schedule should I choose?

It depends on when the computer (or VM or booting operating system) is active and on the campus network, and whether you want patching to compete with your trying to get other work done. In general, if you don't want to be interrupted, choose an EndOfDay or Overnight schedule, and leave your computer powered on, not in sleep mode, and connected to the campus network.

If you take your laptop computer home most nights, choose instead a schedule that runs during the day at a time when you may be away from your desk (e.g., Convo).

If your laptop computer is seldom on campus at all, choose the Next Check In schedule which will try to run every time you are back on the campus network if you miss the scheduled times. But Next Check In can be very annoying, so choose it only if none of the other schedules works for you.

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.

How do I tell if my machine is on a patching schedule?

  1. Visit the KBOX user portal in your web browser
  2. Log in with your Carleton username and password
  3. Click the My Computer tab
  4. Scroll down the page to the Activities section
  5. Click on the Labels link
  6. If you have a Label beginning with PatchSelf, your machine is on a patching schedule
    1. Note: If you have a VM, multiple Operating Systems, or multiple computers, you'll need to repeat this process from each VM/OS/computer

How do I join a KBOX patching schedule?

  1. Visit the KBOX user portal in your web browser
  2. Log in with your Carleton username and password
  3. Click the Software Library tab
  4. In the Search field, type Patch and click Search, or scroll down the page until you see the entries beginning with Patch Schedule: 
  5. Click on the desired Patch Schedule. (If the Patch Schedule you want does not appear in the list, contact the ITS HelpDesk x5999.)
  6. Read the Installation Instructions and click Install Now
    1. Note: If you have a VM, multiple Operating Systems, or multiple computers, you'll need to repeat this process from each VM/OS/computer

What if my software is already up-to-date?

KBOX patch management should not reinstall patches that are already applied, nor should it downgrade your applications.

How do I keep my computer from sleeping when a patch schedule starts long after I leave?

KBOX patching cannot run if a computer is in sleep mode at the scheduled time. Most campus computers are configured to go into sleep mode after a period of inactivity, usually 4 hours. But if a patch schedule step runs at 4am, and you left your computer on at work at 6pm, the computer will be sleeping by 4am when patching is supposed to start.

There are 4 solutions to this problem:

...

Patch Management is covered in detail here.

Manual Updates Within Applications

Most applications on campus computers have automatic update checking turned off.  Users with the proper privileges can update their software manually, or re-enable automatic update checking. The instructions for doing this vary by application; look for the application article here in Carlpedia, or contact the ITS HelpDesk (x5999).

...