Patch for SCCM
Scheduling Publications and Downloads
You can schedule automatic publications and downloads on a recurring basis by creating one or more scheduled tasks. You can have multiple scheduled tasks for each console. One reason you may want multiple scheduled tasks is to define different cadences for publishing updates and metadata. There is no theoretical limit to the number of recurring scheduled tasks you may have at a given time, but you may determine that there is a practical limit for your site.
The ability to view and edit recurring scheduled tasks may be affected by whether or not shared settings are being used. For more information, see Shared Settings Tab.
1.Within the Configuration Manager Software Library workspace, expand the Software Updates folder and click on Ivanti Patch.
2.On the Home tab, click Scheduled Tasks.
The Scheduled Tasks dialog is displayed. The fields in the bottom half of this dialog are read-only and show how the selected task is configured. To change a field in the selected task you must click Edit selected task.
This dialog is a shared item so it will show scheduled tasks for all consoles if shared settings is enabled. If a user has not opted in to shared settings, that person will be able to see all tasks created on their console machine but not tasks created on other console machines.
Each scheduled task is owned by the user who creates the task. If a scheduled task exists, the owner's name will be displayed in the Owner column.
3.Determine if you want to create, edit or delete a scheduled task.
•If you want to create a new scheduled task, click Create new task.
•If you want to edit a scheduled task that is owned by you, select it, click Edit selected task and then modify the task as needed. If you do not want to save your changes, click Cancel.
•If you want to delete a scheduled task that is owned by you, select it, click Delete selected task and then click Yes on the confirmation dialog.
•If you want to edit a shared scheduled task that is owned by another user, you should contact that user and discuss the change that you want to make. If after that discussion you still want to take ownership of the task and make changes, click Edit selected task. The new schedule will now be owned by you and your name will be displayed in the Owner column.
•If you want to delete a shared scheduled task that is owned by another user, you should contact that user and discuss why you want to delete it. If after that discussion you still want to delete the task, select it, click Delete selected task and then click Yes on the confirmation dialog.
4.If you are creating or editing a scheduled task, the Schedule a Recurring Task dialog is displayed.
Specify when the task should run and what action(s) should occur.
•Description: Specify the purpose of the scheduled task.
•Schedule: Specify the day and time when the task should run.
•Run the scheduled task offline: If enabled, the scheduled publication task will be run in offline mode. This means the console will not attempt to download the selected update files. In order for the publication to be successful, the update(s) must already reside in the Local Source folder.
This check box is automatically enabled if Run disconnected is enabled on the Offline Options tab.
•Accept all metadata updates in the catalog: If you want to automatically update WSUS with any metadata revisions that are available for updates that have been previously published, enable this check box.
•Synchronize updates: If you want Configuration Manager to automatically synchronize itself with the WSUS database as part of this task, enable this check box. This will cause an incremental synchronization to be performed. If you do not enable this check box, the published updates will not be available for deployment until your regularly scheduled synchronization process occurs. Synchronization can also be started by selecting the Home tab and then clicking Synchronize Software Updates.
•Publish the updates selected by this filter: Enables you to specify which updates you want to publish on a recurring basis. You can choose either the predefined filter named *Latest not-published or any of your custom filters. If you are using shared settings, only shared custom filters can be selected.
Example 1: To publish all updates that have not been previously published and that are not superseded, select the * Latest not-published filter. This is an easy way to automatically publish new updates on a recurring basis.
Example 2: Assume you have previously created a custom filter that identifies all unpublished critical updates for the products you use in your organization. Simply select that filter here to publish just those updates on a recurring basis.
If an update contains different packages for different languages, only the language versions specified on the Languages tab will be published.
•Publish metadata only: If enabled, this will publish detection logic for the update but not the actual software update binaries. You might do this if you want to detect if an update is needed by your clients but ensure that the update cannot be installed. This is useful only in very specific scenarios and server configurations.
If you edit an update that is published as metadata-only, the original update will be deleted and the edited update republished as metadata-only. This means the revision number for these updates will always be 1. An update that is published as metadata-only cannot be re-signed because there is no content to sign. An attempt to re-sign it will result in a warning message in the log file.
•Add published updates to a new or existing Software Update Group: Microsoft's System Center Configuration Manager provides the use of software update groups to help you organize and deploy your software updates. Updates that are published using Patch for SCCM can be automatically added to a new or existing software update group.
TIP: A video tutorial is available on this topic. To access the video, click the following link:
•Name: If you want the published updates to be added to an existing software update group, select the group name from the drop-down list. You can also type the first few letters of the name until the correct group is displayed. If you want to specify a new group, select New from the drop-down list and provide a unique group name and a description.
•Description: This field describes the purpose of the specified software update group. The description is defined when the group is created and cannot be modified here.
The updates will be added to the software update group after the publication process is complete and a synchronization has been performed.
•Logged on user: If enabled, specifies that you will use the credentials of the currently logged on user to add the publishing task to Microsoft Scheduler. The User box is automatically populated so you only need to type the account password.
•Different user: If enabled, specifies that you want to use a different user account when adding the publishing task to Microsoft Scheduler. For example, you might specify a service account whose password does not expire.
The account must:
•Have Log on as a batch job rights
•Be a member of the WSUS Administrators group on the WSUS server
•Be a member of the local administrators group on the WSUS Server if the WSUS Server is remote
When specifying a different user, you must indicate if credentials are required to authenticate to a proxy server.
•Proxy authentication is required – use these credentials: If enabled, indicates that proxy server credentials are required when using the user account. If you then choose Same as above, the user account credentials will be used as the proxy credentials. If you choose Credentials below, you can provide a separate set of proxy credentials.
•User name: Type the user name for an account on the proxy server. It may be necessary to specify a domain as part of your user name (for example: mydomain\my.name).
•Password: Type the password for the proxy server account.
•Verify password: Retype the same password.
5.(Optional) Use the Configuration Manager Trace Log Tool to open the AutoPublish.log file and monitor the publication process.
The AutoPublish.log file is written by any one-time or recurring scheduled jobs that publish to WSUS. The log is located in the \Users\<user name>\Ivanti\Patch directory.
You can use the Auto-Publish feature of Patch for SCCM in conjunction with Automatic Deployment rules in Configuration Manager to keep clients up to date with the latest third-party updates.
Was this article useful?
Copyright © 2019, Ivanti. All rights reserved.