> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/manage-rd-session-hosts/manage-hosts-rd-session-hosts/time-zone-redirection.md).

# Time zone redirection

Time Zone Redirection redirects the client's time zone to user sessions hosted on Windows Server machines. For RD Session Hosts running the Microsoft RD Session Host role, time zone redirection works natively when the corresponding **Allow time zone redirection** Group Policy setting is enabled.

For Windows Server session hosts where the Microsoft RD Session Host role is not installed, Parallels RAS can still redirect the client time zone. In this scenario, users must have the **Change the time zone** user right assigned.

To grant this permission, add users to the following User Rights Assignment policy on the RD Session Host or RD Session Host template.

`Local Policies > User Rights Assignment > Change the time zone`

The **shell.log** file on the session host records successful and failed time zone redirection operations. Use it to verify functionality and troubleshoot redirection issues.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/rd-session-hosts/manage-rd-session-hosts/manage-hosts-rd-session-hosts/time-zone-redirection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.