> For the complete documentation index, see [llms.txt](https://docs.faronics.com/faronicsdeploy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.faronics.com/faronicsdeploy/automated-windows-update-approval/patch-scan-heartbeat.md).

# Patch Scan (Using a Policy)

Faronics Deploy runs a patch scan on computers after the Deploy Agent is installed on them. After the initial scan, the Patch Scan Frequency is set to a default of once every 24 hours. (Patch Scans can also be run on-demand, see [Patch Scan (On-Demand)](/faronicsdeploy/manual-windows-updates-approval/patch-scan-on-demand.md) for further info).

### Setting the Patch Scan Frequency

The patch scan frequency can be changed while creating or editing the Policy that the computers are using. 

![Policies View](/files/-MV2izRMS4jBatqCZHdl)

1\. Navigate to the **Policies** tab in the Control Grid.

2\. Select the **CREATE NEW POLICY** drop-down list.

3\. Select **WINDOWS POLICY**.

4\. Enter a **Policy Name**.

![Select a Patch Scan Frequency](/files/-MV2mPN5LWfjtI-2qKVJ)

5\. Scroll down to **Patch Scan Frequency** and use the drop-down menu to change from ‘**Once every 24 hours**’ to ‘**Once every 12 hours**’ or ‘**Once every 6 hours**’.

6\. Click **SAVE**.

{% hint style="info" %}
Note that the Patch Scan Frequency can also be edited in an existing Policy as shown below:
{% endhint %}

![Edit the Patch Scan Frequency in an Existing Policy](/files/-MV2n4InRjC7IKN-n36N)

###


---

# 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.faronics.com/faronicsdeploy/automated-windows-update-approval/patch-scan-heartbeat.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.