> 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-insights/dashboard-guides/advanced-insights-os-deployment-dashboard.md).

# Advanced Insights "OS Deployment" Dashboard

<figure><img src="/files/YWAjpreV5JMHdTYnradQ" alt=""><figcaption><p>OS Deployment Dashboard</p></figcaption></figure>

The Advanced Insights OS Deployment Dashboard helps you track Task Sequence performance and status over time. The default view shows two week's execution hitory for all Task Sequences with Boot Media assosicated to them. Thje timescale can be extended using the calendar picker.

The OS Deployment Activity chart shows a breakdown of execution time, and status per-day for all selected Task Sequences. This can be filtered to a specific Task Sequence using the chart picker below. Clicking any chart segment will show all OS builds completed on that day.

The OS Deployment Activity table lists each device built, completion time and status. Clicking any individual machine takes you to the Device View OSD Tab. This view shows the status for each task completed during the Task Sequence execution on that device.

<figure><img src="/files/8n35jz9wdsgU2M9kqiDQ" alt=""><figcaption><p>Device view showing OS Deployment Activity</p></figcaption></figure>

Where a task has additional script output, the info icon shows the verbose script output.

The bottom left table shows a comparison of all Task Sequences and their overall performance statistics.

Finally, the bottom right table shows a view of all errors ocurring in all Task Sequences. This view can help optimize Task Sequence performance and identify where post-imaging remediation may be required to ensure devices are built to standard.


---

# 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-insights/dashboard-guides/advanced-insights-os-deployment-dashboard.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.