Setting up automatic detect and deploy actions consists of the following workflow:
• |
Identify critical patches: Create a patch Smart Label to automatically identify critical patches for laptops. See Using Smart Labels for patching. |
• |
Schedule Detect actions: Create and run a schedule to periodically detect critical patches on laptops. See Configuring patch schedules. |
• |
Schedule Deploy actions: Create and run a schedule to periodically deploy critical patches on laptops. See Configuring patch schedules. |
• |
Check patching status: Periodically check patching status using reports and the patch. See Viewing patch schedules, status, and reports. |
• |
Notify users: Notify users of the patching schedule. You can notify users by sending email and other messaging services outside the appliance Administrator Console. See "Notify users when devices are being patched" in Best practices for patching. |
You can configure the appliance to install non-critical patches according to a schedule.
To schedule non-critical patches:
• |
Detect patches: Create a patching schedule to detect patches on all devices to determine the size of the patching job. See Configuring patch schedules. |
• |
Inactivate patches: If there are patches you do not want to deploy, mark them as Inactive. |
• |
Test patches: Create a schedule to detect and deploy patches to your test devices. See Configuring patch schedules. |
• |
Identify patches for desktops and servers: Create a patch Smart Label to automatically capture the patches to deploy on servers. See Using Smart Labels for patching. |
• |
Check patching status: Periodically check the patching status. See Viewing patch schedules, status, and reports. |
You can create and edit the following types of patch schedules:
Detect-only actions are recommended when the Patch Download Settings are configured to download only Files detected as missing. Running a detect-only action before the deploy creates a list of patch files to download before deployment begins.
1. |
a. |
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
A name that identifies the schedule. This name appears on the Patch Schedules page. | |||
Select Detect. The page updates to the appropriate options. | |||
| |||
To use this option, you must already have created labels or Smart Labels. See Using Smart Labels for patching. | |||
3. |
Detect all available patches. This process can take a long time. Also, it might detect patches for software that is not installed on, or required by, managed devices. For example, if managed devices use anti-virus applications from only one vendor, you might not need to detect patches for all anti-virus vendors. All Patches, however, detects all missing patches regardless of whether they are required by managed devices. To refine patch detection, set up labels for the patches you want to detect, then use the Patch Labels option. | |
Restrict the action to the patches in the labels that you select. This is the most commonly used patch detection option. To select labels, click Edit. To use this option, you must already have labels or Smart Labels for the patches you want to detect. See Using Smart Labels for patching. |
4. |
Run daily at a specified time, or run on a designated day of the week at a specified time. | |||||||||||
Run on the nth of every month/specific month at HH:MM |
Run on the nth day every month, (for example, the first or the second) day of every month, or a specific month, at the specified time. | ||||||||||
Run according to a custom schedule. Use standard 5-field cron format (extended cron format is not supported): Use the following when specifying values:
| |||||||||||
The timezone to use when scheduling the action. Select Server to use the timezone of the appliance. Select Agent to use the timezone of the managed device. | |||||||||||
The time limit for patching actions. For example, if you schedule patches to run at 04:00, you might want all patching actions to stop at 07:00 to prevent bandwidth issues when users start work. To do so, you could specify 180 in the minutes box. |
5. |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy