> 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/administration/updates/options/configmgr-component-management.md).
# ConfigMgr Component Management
*Applies to: Patch My PC Publisher V2.x*
## Overview
The **ConfigMgr Component Management** section provides visibility into the **WSUS Configuration Manager (WCM)** component status. This section is primarily used during initial onboarding and troubleshooting scenarios where ConfigMgr needs to immediately re-evaluate WSUS configuration data.
When you publish your first Patch My PC update, the update is written to WSUS, but ConfigMgr does not become aware of the new Patch My PC product category until it re-processes WSUS configuration data. Normally, this happens during a Software Update Point (SUP) synchronization.
Restarting the WCM component triggers this re-evaluation without the need to perform a SUP sync. As a result, the Patch My PC product category becomes visible in the SUP component properties immediately.
The available actions are:
* Click **Query** to retrieve the current WCM component status from ConfigMgr. This action refreshes the status shown in the Publisher field **WCM Component Status** and does not make any configuration changes.
* Click **Restart** to restart the WCM component to force ConfigMgr to immediately re-evaluate the WSUS configuration on the site server. This includes subscribed products, classifications, and third party update categories.
{% hint style="info" %}
**Note**
We automatically attempt to restart the WCM component after the first Patch My PC update is published to ensure the new product category is properly recognized in ConfigMgr immediately.
The WCM component typically configures the WSUS server once every hour automatically to ensure that the settings configured in WSUS match the setting specified in the ConfigMgr console.
{% endhint %}
## Logging
These actions are logged in the *%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-ConfigMgrClient.log* log.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.patchmypc.com/patch-my-pc-publisher/administration/updates/options/configmgr-component-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.