> 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/parallels-desktop-developers-guide/command-line-interface-utility/manage-parallels-desktop-from-cli/display-parallels-desktop-information.md).

# Display Parallels Desktop Information

**prlsrvctl info**

Displays the detailed information about the Parallels Desktop configuration.

Optional parameters

**--license --json**

Displays the detailed information about the Parallels Desktop license and activation status.

{% hint style="info" %}
**Note**: Beginning from version 26.4.0, the response on Enterprise Edition installations includes **activation\_type** parameter, which can be `LIC_KEY` for copies activated with license keys, or `SSO` for copies [activated using SSO](/landing/pd-ag/getting-started/configuring-the-single-sign-on-sso-integration-with-parallels-my-account.md).
{% endhint %}

**--activation-id**

If included, only the license activation ID is displayed.

**--deactivation-id**

If included, only the license deactivation ID is displayed.

**--json**

Produces the machine-readable output in JSON format.


---

# 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/parallels-desktop-developers-guide/command-line-interface-utility/manage-parallels-desktop-from-cli/display-parallels-desktop-information.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.