> For the complete documentation index, see [llms.txt](https://docs.idea-hpc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idea-hpc.com/modules/virtual-desktop-interfaces/user-documentation/virtual-desktop-scheduling.md).

# Virtual desktop scheduling

How to change the schedule of your Windows or Linux desktop

By default, your virtual desktop comes with the Stop On Idle schedule. This will stop/hibernate your virtual desktop only when the CPU use is below the cluster set utilization threshold. Default is 30%. AND when no one has logged in for at least `virtual-desktop-controller.dcv_session.idle_autostop_delay`. Default is 60 minutes.

{% hint style="info" %}
Virtual Desktop will only be stopped if idle (e.g: no active session connected within the Idle Timeout period and CPU usage below 30%). This is meant to prevent accidental stop and ensure you won't have to worry if you have a simulation running on your desktop overnight but have configured auto-stop after 8PM
{% endhint %}

You can change this behavior by configuring your own scheduling, and IDEA will ensure your desktop will automatically start/stop based on your own requirements.

There are a number of schedules to choose from. Please review the table below.

<table><thead><tr><th width="186">Mode</th><th width="222">Running Desktop</th><th>Stopped Desktop</th></tr></thead><tbody><tr><td>No Schedule</td><td>Stay running until you stop/terminate</td><td>Stay stopped until you manually restart it</td></tr><tr><td>Stop On Idle</td><td>Will be stopped if idle after AutoStop Idle timeout &#x26; CPU use is less than Utilization Threshold</td><td>Will stay stopped</td></tr><tr><td>Started All Day</td><td>Will stay running</td><td>Will be automatically started after 00H</td></tr><tr><td>Working Hours</td><td>Will be started at 9 AM</td><td>Will be stopped if idle after 5 PM</td></tr><tr><td>Custom Schedule</td><td>Will be started based on your own time</td><td>Will be stopped if idle based on your own time</td></tr></tbody></table>

Simply click the dropdown menu to chose your schedule for that day using the different presets below:

You can at any moment review whether or not you have a schedule configured for the current day on your virtual desktop by checking the settings bar of your session (note: schedule are unique to each desktop)

The **Idle stop** badge appears only on a day whose schedule runs the idle check. Its absence on another day does not change that day's explicit start or stop times.

<figure><img src="https://4178558898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff38qThSa0Aa40txosxbS%2Fuploads%2F1rrx7gJ85d0j7JxjufRH%2Fmods_vdi_user_schedule_verify.webp?alt=media&amp;token=8f146b06-512e-4e01-806c-1401ebb58dbb" alt=""><figcaption><p>Verify if a schedule is applicable by checking the settings bar</p></figcaption></figure>

To create/edit a schedule, click "**Actions**" > "**Schedule**". This will open a new modal where you will be able to choose the schedule for any given day:

<figure><img src="https://4178558898-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff38qThSa0Aa40txosxbS%2Fuploads%2FBIL7OSBG0FtmmZ1Z1iF1%2Fmods_vdi_user_schedule_custom.webp?alt=media&amp;token=82920cce-4540-4032-880b-31622413bd7d" alt=""><figcaption><p>Set a custom schedule per day</p></figcaption></figure>

{% hint style="info" %}
Schedule is re-evaluated every 30 minutes
{% endhint %}

Idle-stop comparisons and their log timestamps use UTC internally, so a non-UTC host timezone does not shift the decision. The schedule itself still uses the configured cluster timezone.

If your administrator allows it, the same modal also shows a **Stop On Idle after (minutes)** field above the weekly schedule. This overrides `virtual-desktop-controller.dcv_session.idle_autostop_delay` for this desktop only; set it to `0` to fall back to that cluster default. The value you can request is capped by `virtual-desktop-controller.dcv_session.idle_autostop_delay_max`, 240 minutes out of the box, and lowering that cap later also clamps any override you already saved. A cap of `0` turns per-session overrides off, and the field does not appear.


---

# 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.idea-hpc.com/modules/virtual-desktop-interfaces/user-documentation/virtual-desktop-scheduling.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.