> 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/scenario-based-quick-start-blueprints/scenario-a-software-developers-and-engineers.md). # Scenario A: Software Developers & Engineers ### Who this fits Developers and engineers who need a Windows environment to build and test against, and who manage their own local toolchains once the VM is up. ### Architecture at a glance Same architecture as described in [Overview & Decision Matrix](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/overview-and-decision-matrix-at-a-glance.md#core-deployment-architecture): the Management Portal sources Windows declaratively, Jamf Pro installs and configures Parallels Desktop, and the resulting VM enrolls in Intune. ### Deployment method and why **Declarative**. Developers get a stock Windows image and add their own toolchains after first launch — there's no need to pre-build and maintain a custom `.pvmp`. ### Management Portal policy settings Create a policy for the developers' user group with a Golden Image set to **Declarative** / **Windows Enterprise**. Recommended settings for this group: * **Security Controls**: Do not allow removing provisioned VMs. * **VM Settings**: Clipboard/Drag-and-drop: Bidirectional · VM startup: Ready in background · Show Developer Tools: enabled. See [Stage 3: Management Portal & Remote Policy Setup](/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/end-to-end-implementation-stages-technical-workflow/stage-3-management-portal-and-remote-policy-setup.md) for how to create the policy, and the full comparison across scenarios. ### Role handoffs * **Portal Admin** — creates the policy and Golden Image, assigns the developer group. * **Mac Admin** — confirms Parallels Desktop is deployed via the Jamf app profile. * **Windows-Identity Admin** — confirms the provisioning package enrolls the VM in Intune correctly for this group. ### Verification In the Management Portal, open the Golden Image card and confirm the developer's VM shows as provisioned. Ask the developer to confirm Windows completes first boot and signs in with their corporate account without manual setup. ### Where to go next Continue to [Stage 1: Account, SSO & Licensing Configuration](https://github.com/Parallels-Corp/DI-OPS-prls-docs/tree/master/parallels-desktop/admin/end-to-end-implementation-stages-technical-workflow/stage-1-account-sso-and-licensing-configuration.md) to set up the developer group's sublicense and activation. --- # 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/scenario-based-quick-start-blueprints/scenario-a-software-developers-and-engineers.md?ask=&goal= ``` `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.