> 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/pd-ag/parallels-desktop-enterprise-quick-start-guide/overview-and-decision-matrix-at-a-glance.md).

# Overview & Decision Matrix

This guide walks you through deploying and managing Parallels Desktop Enterprise Edition across your organization. Start here: match your environment against the inputs below, find the scenario and deployment method it points to, then open that scenario's blueprint for the full walkthrough.

This guide assumes you're already familiar with Jamf Pro or Microsoft Intune. It does not assume you know Parallels Desktop.

### What you need to know before you start

| Input                    | What to check                                                                                    |
| ------------------------ | ------------------------------------------------------------------------------------------------ |
| Mac management           | Are your Macs enrolled in an MDM (Jamf Pro, Intune), or unmanaged?                               |
| Windows guest management | Will the Windows VMs be Intune-enrolled, or not?                                                 |
| Who the users are        | Employees, contractors, or automated build agents?                                               |
| Activation               | Corporate account single sign-on (SSO), or a license key?                                        |
| When software can arrive | After provisioning (delivered by Intune or similar), or does it need to already be in the image? |

### What this guide tells you

Every scenario resolves to a Golden Image in the Management Portal. A Golden Image's **Deployment method** is either **Declarative** — Windows sourced by the Portal (**Windows Enterprise** or a **Custom ISO**) with a Microsoft provisioning package (`.ppkg`) applied at first launch — or **VM image** — a `.pvmp` virtual machine you build and host. The table below maps each scenario to its method.

| Scenario                                                                                                                                                                                                             | Deployment method       | Why                                                                                       |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------- |
| [Scenario A: Software Developers & Engineers](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints/scenario-a-software-developers-and-engineers.md)                   | Declarative             | Stock image; developers add their own toolchains                                          |
| [Scenario B: Knowledge Workers & Enterprise Fleet](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints/scenario-b-knowledge-workers-and-enterprise-fleet.md)         | Declarative             | Standard fleet image; Intune delivers line-of-business apps                               |
| [Scenario C: Contractors & BYOD Users](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints/scenario-c-contractors-and-byod-users.md)                                 | Declarative             | No MDM requirement; an invitation email covers unmanaged Macs                             |
| [Scenario D: App Delivery / App-Centric (Hidden Windows)](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints/scenario-d-app-delivery-app-centric-hidden-windows.md) | **VM image** (required) | Single Application Mode needs a `.pvmp` file in an Autodeploy Package, and exactly one VM |
| [Scenario E: DevOps & Automated Pipelines](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints/scenario-e-devops-and-automated-pipelines.md)                         | **VM image**            | Declarative deployment is Windows-only; pipelines need pinned, reproducible state         |

Each scenario's blueprint spells out the exact Security Controls and VM Settings for that path.

### Core Deployment Architecture

Modern Parallels Desktop Enterprise Edition deployments decouple the host management experience from guest operating system preparation:

```mermaid
flowchart TD
    MP["<b>Parallels Management Portal</b><br/>Policies · Golden Images · Bundles"]
    subgraph MAC["Mac host — enrolled in Jamf Pro"]
        PD["<b>Parallels Desktop</b><br/>Installed from Jamf app catalog<br/>Configured via app profile"]
        WIN["<b>Windows 11 Enterprise VM</b><br/>Sourced by the Portal<br/>Provisioned by .ppkg<br/>Enrolled in Intune"]
        PD --> WIN
    end
    MP -->|Policy and licensing| PD
    MP -->|Golden Image configuration| WIN

    classDef portal fill:#4F46E5,stroke:#4338CA,color:#ffffff,stroke-width:2px
    classDef desktop fill:#F1EBFE,stroke:#7C3AED,color:#4C1D95,stroke-width:2px
    classDef windows fill:#E4EEFC,stroke:#2563EB,color:#1E3A8A,stroke-width:2px
    class MP portal
    class PD desktop
    class WIN windows
    style MAC fill:#FFFDF3,stroke:#E9C46A,stroke-width:2px,stroke-dasharray: 5 5
```

License management — including creating new sub-licenses — lives in My Account; the Management Portal is where policies and Golden Images live. On the Mac, Jamf Pro installs Parallels Desktop from its app catalog and configures it through an app profile. Parallels Desktop then provisions the Windows VM the Portal points it to, and the provisioning package enrolls that VM in Intune.


---

# 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.parallels.com/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/overview-and-decision-matrix-at-a-glance.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.
