How to execute the Software Update Cycle without using the Default Software Update Plug-in Policy.

Products

• Patch Management Solution for Windows

Issue/Introduction

 

Resolution

The Software Update Cycle may be executed by the Maintenance Window alone.

1. The Default Software Update Plug-in Policy must be enabled and the policy must target each client to be updated.

• Ensure each client is not targeted by more than one Default Software Update Plug-in Policy, for this will cause issues with conflicting configurations.

2. Work through one of the following:

• Delete the schedule on the Default Software Update Plug-in Policy
  • ​Highlight the box holding the schedule for the install and select the red X in the tool bar for that schedule.
  • Note: This step is to inform the client's user that the Default Software Update Plug-in Policy is no longer scheduled as viewed on the Altiris Agent GUI > Software Updates tab.
    • If the Maintenance Window schedule mirrors the Default Software Update Plug-in Policy Schedule, this schedule may be left alone to inform the user that the scheduled time is in order.
  • Advisory: This process is not supported in older versions as deleting the schedule removes the Client's ability to run the Software Update Cycle
     
• Configure the Schedule to run in the far future
  • Setting the schedule to run in the year 2030 and repeat daily is the best practice for this process
    • Caution: Ensure the year in the future does not approach, for per the example above; once the year 2030 begins, the Software Update Cycle will run

3. Configure the reboots as desired for the Software Update Cycle on the Default Software Update Plug-in Policy.

• If the desired schedule for reboots needs to be repeated, select the ' No repeat' link on the right of the schedule window and configure as desired.
• Enable the interval to repeat in the drop down and select the day that the Maintenance Window will be active on.

4. Leave the 'Override Maintenance Windows' disabled located near the bottom of the Default Software Update Plug-in Policy.

5. Schedule the Maintenance Window to open when the Software Update Cycle is to execute.

• Configure the Maintenance Window to open and confirm the arrows on the schedule hourly slide are pointing in the proper direction
  • Go to the Console > Settings > Agents/Plug-ins > Maintenance Windows > All Managed Computers
  • This policy may be cloned as needed

Configuring the Software Update Cycle in this manner will cause the following error to be present in the client logs:

Module: PatchMgmtAgentsUI.dll
Source: Software Update Agent UI
Description: Empty Schedule Text

 

• At this time, this error appears to be cosmetic, for the Software Update Cycle still runs when the Maintenance Window opens. 
• Research found that this error is also thrown when the Start date is chronologically after the End date as configured on the Default Software Update Plug-in (DSUP) Policy, and the Software Update Cycle will not execute if there is no Maintenance Window present, for the schedule is essentially NULL. 
  • Found if disabling the End date is in place, or the End date is chronologically after the Start date; the process works and the schedule is received. 
  • Note: Confirmed in Patch Management 8.x that the setting configured with the Start date is chronologically after the End date the DSUP Policy will not even save and errors with the following GUI notifications:
    • No Software Update Installation schedule set
    • The policy schedule can not be applied, if start date later than end date

Note: This functionality is not best practices, for the Default Software Update Plug-in Policy is the preferred method for executing the Software Update Cycle. This functionality is not present in Patch Management 7.1, for the client will fail to update configuration if the schedule is deleted from the Default Software Update Plug-in Policy.

Review the following relating articles to gain a better understanding of possible conflicts regarding the Software Update Cycle:

• Maintenance Windows may cause issues: TECH127411
• Software Update Policy settings cause issues: HOWTO4916