Patch for SCCM, powered by Shavlik

Automatically Publishing Updates Using a Recurring Scheduled Task

You can automatically publish updates on a recurring basis by creating a scheduled task. You can only have one scheduled recurring task at a given time.

1.Within the Configuration Manager Software Library workspace, expand the Software Updates folder and click on Ivanti Patch.

2.On the Home tab, click Settings (or right-click Ivanti Patch and click Settings).

The Ivanti Patch for SCCMSettings dialog is displayed.

3.On the Schedule tab, specify when the scheduled task should run and what action(s) should occur.

Schedule Download and/or Publication: Specify when you want the recurring task to 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.

Publish the packages 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.

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.

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.

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\

Password: Type the password for the proxy server account.

Verify password: Retype the same password.

4.(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.

You can use the Auto-Publish feature of Ivanti 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?    

The topic was:



Not what I expected