> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options/software-update-point-sync.md).
# Software Update Point Sync section of Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **SOFTWARE UPDATE POINT SYNC** section on the **WSUS Options** tab in Patch My PC (PMPC) Publisher lets you trigger Software Update Point (SUP) synchronizations and ultimately serves as the foundation for all Publisher interactions with ConfigMgr.
This section also allows you to manually initiate a SUP sync, which is the process by which ConfigMgr retrieves update metadata from WSUS (and ultimately Microsoft Update), making newly published first- and third-party updates visible and actionable in the ConfigMgr console.
## Perform Delta Synchronization
Clicking the **Perform Delta Synchronization** button triggers a *delta sync* that only retrieves the changes from WSUS that have occurred since the last successful synchronization.
This includes newly added updates and updates that have been revised or removed. Updates that were previously synchronized and have not changed are not re-evaluated.
Because of this limited scope, delta syncs are faster and place less load on WSUS, SQL, and the ConfigMgr Site Server. For this reason, most synchronizations in ConfigMgr (both manual and scheduled) run as delta syncs.
The key characteristics of delta synchronization are:
* Only new or changed update metadata is synchronized.
* The entire update catalog is not reprocessed.
* Faster and less resource-intensive.
* Commonly sufficient after publishing or enabling third-party updates.
{% hint style="danger" %}
**Important**
It’s important to note that a delta synchronization does not repair updates that may have been damaged or deleted during previous synchronizations.
{% endhint %}
## Perform Full Synchronization
Clicking the **Perform Full Synchronization** button forces ConfigMgr to perform a *full sync*, i.e. to synchronize the entire update catalog from WSUS, filtered by the SUP site components product and classifications configuration.
At the end of a full sync, the ConfigMgr database reflects the complete and current state of the WSUS catalog.
Full syncs are more resource-intensive and take longer to complete, especially in environments with large update catalogs. Because of this, they are not typically used for routine operations.
The key characteristics of a full synchronization are:
* The entire update catalog is re-evaluated.
* Updates that were damaged or deleted in previous synchronizations can be repaired.
* More time-consuming and resource-intensive.
* Intended for troubleshooting or recovery scenarios.
{% hint style="info" %}
**Note**
ConfigMgr typically escalates to a *full sync* when required. This occurs when configuration changes are detected that cannot be processed incrementally.
Examples include:
* Switching to a different default SUP.
* Changes to Product and Classification selection in the SUP site component properties.
* Modifications to supersedence settings or the supersedence window.
In addition, ConfigMgr periodically performs a full sync at a fixed interval (every 7 days by default).
See [About Synchronizing the Software Update Point](https://learn.microsoft.com/en-us/intune/configmgr/develop/sum/about-synchronizing-the-software-update-point) for more information on SUP synchronization.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options/software-update-point-sync.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
