> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/anywhere/content-creation-publication/content-creation-publication-configmgr.md).

# Configuration Manager

Configuration Manager content should be automatically published based on the Content Publication Settings when that content is created in Configuration Manager. Create a package, application or other content type in the ConfigMgr console, then open Web Portal to view the content in the Content Viewer page.

For additional information please see our [Configuration Manager Publication settings](https://github.com/AdaptivaDocs/docs/blob/main/anywhere/anywhere/configmgr-settings-publication-settings.md) page.

## Viewing ConfigMgr Content

1. Click **Content Publication** and select the content type associated with the ConfigMgr content, Package, Application, etc.

![](/files/h0mv8UODzSQNlnlHRF6Q)

You can now view and interact with content from Configuration Manager that is known to Adaptiva by clicking on each content type tab.

![](/files/qV6Mtt9QfersJ0ZoUC6X)

In the case of a publication error hover over the package and select the ellipses (**...**) for an individual piece of content in the table and select View Detail. By default, if there is an error publishing a package, the Adaptiva Server will await manual resolution/retry.

{% hint style="info" %}
To handle potential content publication failures, there are cloud publish retry settings available . Open `Regedit` to `HKEY_LOCAL_MACHINE\SOFTWARE\Adaptiva\server` and find `contentsystem.content_upload_max_retries`. Set this value to 3 then find `contentsystem.content_upload_retry_pause_duration` and confirm the value is set to 15 minutes (default). This will effectively retry to publish to the cloud 3 times, with 15 minute pauses in between tries.
{% endhint %}

### View Details

With this menu you can get more details about a content item including its General Settings, Cloud Content Settings, and Details. You can either view read-only **Default Package Settings**, or override settings by toggling **OFF** **Use Default \[Content Type] Settings** then click **Override Package Settings**.

If changes were made, click **Save** or **Save & Publish**.

![](/files/wvxjToff7JgkHa7X9bgP)

For more information, please visit our [Content Publication Settings](/anywhere/content-publication-settings.md) page.

The Details section will display information about the package. If there was a publication error, information about the error will be listed.

![](/files/HDLspBphYVrKFn4MN2Oh)

## Publish ConfigMgr Content

If Auto Publish Everything was not selected, then content will need to be manually published in order for Adaptiva to be able to download the content.

Follow the steps below to manually publish ConfigMgr content in OneSite.

1. **Content Publication** and select the content type associated with the ConfigMgr content, Package, Application, etc.

   ![](/files/SoS8RK5s4gl22Bdfvfr7)
2. Click on the ellipses, **...**, under the **Actions** column and select **Publish**

You will notice that the status icon next in the Name column will change to several other icons as the content is being published. Depending on the size of the content this may take some time. Once the content is published the color of the icon will turn green

Once the content is published, it is now available for Adaptiva clients to download and is now ready to use for [Content Push](/anywhere/content-push.md).


---

# 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.adaptiva.com/anywhere/content-creation-publication/content-creation-publication-configmgr.md?ask=<question>&goal=<endgoal>
```

`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.