> 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/common-management-tasks/resolving-z-order-issues.md).

# Resolving z-order issues

If you encounter an issue related to z-order in applications published with Parallels RAS, you can try doing the following:

1. Open the Windows Registry on the computer where Parallels Client is installed.
2. Create a value named `ZOrderMode` with the type `DWORD` in the `HKEY_CURRENT_USER\Software\Parallels\AppServerClient\<guid>` key, where `<guid>` is the ID of the Farm.
3. Specify one of the following values:
   * `1`: Simple window manager rendering, no window clipping support. Works best with rectangular window areas.
   * `2`: Simple window-to-window copying with a fixed refresh rate, supports window clipping. Supports all window area shapes.
   * `3`: Heuristic mode, which switches between modes `1` and `2`.
   * `4`: Improved heuristic mode, which can require more resources.


---

# 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/common-management-tasks/resolving-z-order-issues.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.
