Patch Mgmt > Initial Update

Initial Update automatically applies all required service packs and patches according to the Patch Approval Policy beginning at the scheduled initial update time. Rebooting the machine immediately as required.  Unlike the Automatic Update function, this is not a recurring process.  

When a machine is scheduled, Initial Update will perform a patch scan to ensure the latest scan results are available.  Then, updates are scheduled in successive groups.  First, if required, the Windows Installer will be updated.  The second group of updates consists of any operating system related service packs.  After the service packs, non-security patches (Nxxxxxx) are applied.  The next group is the Microsoft security patches (MSyy-xxx).  Next, Office related service packs, where possible, are installed.  Finally, Office related patches, where possible, are installed.

Scripts can be configured to be executed just before the Initial Update begins and/or after Initial Update completes to automate new machine preparation and setup by running scripts to perform common preparation tasks for each machine. Use the Patch Mgmt Pre/Post Script function to configure these scripts on a per-machine basis.

NOTE: Reboots are forced after each service pack and at the end of each patch group without warning.  This is necessary to permit the re-scan and installation of the subsequent groups of patches.

NOTE: Once the Initial Update has been scheduled, the Status column will display the current processing step.  When all processing has been completed, the Status column will display either “Completed - fully patched” or “Completed - remaining patches require manual processing”.  If the latter is displayed, you must go to the Patch Mgmt tab, Machine Update function, and select the appropriate machine to determine why all patches were not applied.  Some patches might require manual install or for the user to be logged in.  In the case of patch failures, manually schedule failed patches to be reapplied.  Due to occasional conflicts between patches resulting from not rebooting after each individual patch, simply reapplying the patches will typically resolve the failures.

NOTE: The Agent for the KServer will not be displayed on the Initial Update screen. Initial Update cannot be used on the KServer.

Schedule

Select a date and time and click SCHEDULE to apply all required service packs and patches on all selected machines.

Cancel

Cancel any pending patch installations.

Stagger By

You can distribute the load on your network by staggering the installation of patches. If you set the stagger for 60 minutes, then patch installation to each machine ID is staggered by 60 minutes. For example, machine 1 runs at 10:00, machine 2 runs at 11:00, and machine 3 runs at 12:00, etc.

Skip if machine offline

Check to only install the updates at the scheduled time.   If machine is offline, skip and reschedule for next day at the same time.  Uncheck to install the update as soon as the machine connects after the scheduled time.