Republish During Next Sync Schedule

Applies to: Patch My PC Publisher Available at level: All Custom Products, All Products, Vendor, Product Available on tab: Updates, ConfigMgr Apps, Intune Apps, Intune Updates

Overview

The Republish During Next Sync Schedule option instructs the Publisher to rebuild and republish an update or application during the next publishing service sync.

This action is used when an item has already been published but its content or core metadata must be rebuilt to restore functionality or include additional files.

Republishing recreates the underlying content rather than issuing a simple metadata change. The exact behavior depends on the platform being targeted.

• For WSUS updates, republishing creates entirely new updates. They appear as separate items in WSUS and ConfigMgr and have a new content path and content hash. By default, the update title is appended with 'Republished on date' to help identify republished updates.

• For ConfigMgr applications, republishing creates a new content version.

• For Intune apps and Intune updates, the existing Win32 app content and metadata are replaced while the Win32 application ID remains the same.

Note

More information on how to configure republished update behavior for WSUS updates can be found on the Update Republishing Options page.

When to Use Republish

Republishing should only be used when the actual content of an update or application must change and the issue cannot be resolved through a normal revision or metadata only update.

Common scenarios include the following:

• WSUS content files were removed If the content for a previously published WSUS update is missing, ConfigMgr will fail to download it and return a 404 error. Republishing restores the missing content in WSUS.

• ScriptRunner binaries must be added When you enable a feature for the first time that depends on the ScriptRunner executable for an already published update or application, the item must be republished so the required binaries are included in the content.

• A right-click customization option modified the content Options such as adding pre or post scripts, attaching an MST, or enabling conflicting process management introduce additional files. Because these changes alter the content itself, republishing is required so the update package or application content can be rebuilt.

• The WSUS code signing certificate changed Previously published updates must be republished so they can be signed again using the new certificate.

Important Intune Considerations

In many environments, deleting an existing Intune Win32 app and allowing the Publisher to recreate it during the next sync can be faster than using the Republish option.

When an app is recreated, it receives a new application ID and the Intune Management Extension evaluates it almost immediately during the next policy sync.

Republished apps keep the same application ID and are subject to the Global Re-evaluation Schedule. This schedule typically rechecks previously evaluated apps about once every 24 hours. As a result, republished apps may take significantly longer to be detected by clients than newly created apps.

Important WSUS Considerations

When a WSUS update is marked for republishing, the Publisher displays a confirmation dialog. This dialog reminds you that a Software Update Point sync is required before the republished update becomes available in ConfigMgr.

After confirmation, you are prompted to choose whether the new update should supersede the existing update in WSUS. If you choose to supersede, the older update will be marked as superseded once the new update is created.

If you prefer older updates to be expired instead of superseded, this can be done manually using the Modify Published Updates wizard in the Publisher.

Important

Avoid deleting previously published updates directly from WSUS or ConfigMgr. Doing so can cause republished updates to reappear unexpectedly and may result in hash validation errors if clients attempt to download content that no longer exists.