# Content Prestaging Settings

Prestaging content makes the content available on the device locally when the deployment time arrives. This reduces the deployment time and minimizes the chances of missing service windows or having devices going offline before a content download finishes.

You can create Content Prestaging Settings within the Patching Strategy, Business Unit, or Deployment Channel templates.

## Defining Content Prestaging Settings

The templates for Patching Strategies, Deployment Channels, and Business Units include the choice to set Content Prestaging settings. Settings default to **Not Enabled**.

Content Prestaging settings include two options:

* **Server Content Push (Recommended)** -- The Adaptiva pushes the content to the best-suited sources in all locations that require the content.Adaptiva recommends this type of prestaging when the Deployment Strategy targets only a subset of devices. High-availability machines receive the content and function as local sources during discovery and deployment.
* **Client Content Pull** -- This option enables any client that requires the content to download and cache it before deployment. Suitable when a Deployment Strategy targets all clients that need the updated content.

**Push Content**

* **Not Enabled** -- Disables any prestaging as part of the Patching Process workflow or Patching Strategy.
* **Handled by System** -- The Adaptiva system handles the prestaging automatically and pushes content to three automatically chosen devices within the office that require the content.
* This push occurs at once when the metadata updates include the latest content that meets patching requirements.
* **Handled by Workflow** -- When enabled as part of a Patching Process, Deployment Channel, or Business Unit template, pushes the content upon deployment of the Patching Process.

**Pull Content**

* **Not Enabled** -- Disables any prestaging as part of the Patching Process workflow or Patching Strategy.
* **Handled by System** -- The Adaptiva system handles the prestaging automatically. The Client pulls content from the Server and instructs all Clients that require the content to download and cache it ahead of any deployment.
* **Handled by Workflow** -- When enabled as part of a Patching Process, Deployment Channel, or Business Unit template, the Client pulls the content upon deployment.

## Content Prestaging Considerations

Due to the large size of monthly updates, server-side pre-staging is disabled for some content. It is much more efficient for clients to download sparse files with only the relevant content needed for that device.

* You can only pre-stage WSUS content using the Client Content Pull method. Server Content Push is disabled for Windows Server Update Services (WSUS) content by default.
* OneSite Patch does not support pre-staging of Office 365 content.

## Set Content Prestaging Settings

Use this procedure to add or change Content Prestaging Settings in Patching Strategy, Business Unit, or Deployment Channel templates.

1. Expand the **Notifications** in an open object template, and then scroll down to the **Content Prestaging Settings**.

   ![](/files/G2DINafwYCemBjiWVx4B)
2. Expand the **Content Prestaging Settings** to view the available settings.

   ![](/files/1DkQGlBpbjXHL2GaGch6)

### Enable Client Content Pull

Client Content Pull defaults to **Not Enabled**. To enable pull settings, complete the following steps in the **Content Prestaging Settings** of a Patching Strategy, Business Unit, or Deployment Channel template:

![](/files/41Cw6rIRi1UZ3XKTA7tD)

1. Select the arrow to the right of **Client Content Pull** to expand the menu of available options.

   ![](/files/3UtKHJNL4F1nGIpnq4Yy)
2. Select the option you need for the object template you are using. For definitions of push options, see [Defining Content Prestaging Settings](#defining-content-prestaging-settings).
3. Select **Save** on the upper-left to save your changes:

   a. Check the **Error View** and resolve any errors.

   b. Select **Save** again if you make any changes.

### Enable Server Content Push

Server Content Push defaults to **Not Enabled**. To enable push settings, complete the following steps in the **Content Prestaging Settings** of a Patching Strategy, Business Unit, or Deployment Channel template, complete the following steps:

![](/files/41Cw6rIRi1UZ3XKTA7tD)

1. Select the arrow to the right of **Server Content Push** to expand the menu of available options.

   ![](/files/qd0ODGjjIRwiAnuQbYQs)
2. Select the option you need for the object template you are using. For definitions of push options, see [Defining Content Prestaging Settings](#defining-content-prestaging-settings).
3. Select **Save** on the upper-left to save your changes:

   a. Check the **Error View** and resolve any errors.

   b. Select **Save** again if you make any changes.


---

# Agent Instructions: 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:

```
GET https://docs.adaptiva.com/patch/advanced-settings/content-prestaging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.