Skip to main content

Overview

These are recommended best practices for deploying Citrix HDX and HP Anyware PCoIP on MacStadium infrastructure. This document provides generalized guidance on MDM enrollment, permissions, networking, and performance tuning.

Security and Encryption

Disable FileVault unless your security policy requires it. If a machine with FileVault enabled powers down, a MacStadium Data Center Technician must intervene locally before it can be accessed remotely. If encryption is required, coordinate with MacStadium to set up secure restart scripts that automate reboots and recovery before enabling it. Use an MDM solution (Jamf Pro, Kandji, or Intune) to enforce your security baseline. See MDM Policies and Permissions for VDI-specific configuration.

MDM Enrollment for VMs

Apple Business Manager (ABM) Automated Device Enrollment is not available for virtual machines. Apple identifies VM hardware identifiers as virtual and blocks auto-enrollment. This cannot be worked around. The standard approach is user-initiated enrollment scripted into your golden image. A LaunchDaemon runs at first boot to install the management framework. A LaunchAgent runs at login to prompt the user to approve the MDM profile. That approval is a macOS requirement on unsupervised devices. MacStadium’s tested and supported enrollment process for VMs at scale uses Jamf Pro. For a full walkthrough, see Jamf Enrollment for MacStadium VDI Desktops. The LaunchDaemon/LaunchAgent pattern is the same for Intune and Kandji, but MacStadium is still validating and developing optimized guidance for those platforms. A few things to get right before sealing the image:
  • Set enrollment tokens to expire on a schedule aligned to your image rotation cycle.
  • Verify enrollment on a test VM before promoting to production: profiles status -type enrollment should return MDM enrollment: Yes.
  • Do not seal the image with an MDM profile or management framework already present.
For image build and versioning guidance, see VDI Golden Image Management.

MDM Policies and Permissions

Configure and test these before sealing your golden image. Some permissions cannot be pre-approved via MDM, so they need to be granted manually on a clean VM before the image is sealed.

Privacy Preferences (PPPC / TCC)

Bundle IDs for PPPC profiles: HP does not document Team ID information for HP Anyware. To generate a code requirement string for use in a PPPC payload, run this against the installed host agent:
Paste the designated => line from the output into the Code Requirement field of your MDM’s PPPC payload.

System Extensions (Citrix only)

Citrix VDA installs system extensions for camera and USB redirection. Pre-approve these to prevent user-facing prompts. On macOS 15 (Sequoia), admin users can remove system extensions via System Settings. Jamf Pro 11.9.1+ and Kandji 3.x both support marking extensions as non-removable. Citrix also installs background services under /Library/LaunchAgents and /Library/LaunchDaemons. On Ventura and later, users see a “Background Items Added” notification on first login. This is expected. Do not suppress or disable these services.

MDM Platform Notes


Networking and Connectivity

Disable packet inspection and SSL interception on VDI session traffic. Both HDX and PCoIP are sensitive to latency added by middleboxes. Route sessions as directly as possible and avoid unnecessary proxy hops. Required ports: Enable EDT (UDP 1494/2598) for Citrix where possible. It provides noticeably better performance over variable-quality connections compared to TCP-only transport. Bandwidth planning per concurrent user: Maintain a secondary administrative access path (VNC or MacStadium remote console) independent of your VDI session for recovery scenarios.

Performance Tuning

macOS Settings (both protocols)

Disable desktop animations and transparency effects before sealing your image: System Settings > Accessibility > Display > Reduce Motion and Reduce Transparency. Disable screen saver, hot corners, and idle timers:
MacStadium hosts use wired Ethernet. If any nodes in your cluster are on Wi-Fi, disable Wi-Fi power saving to prevent the NIC from dropping into a low-power state during active sessions.

Protocol-Specific Tuning

HP Anyware plist directives (set before sealing, or push via MDM config profile):
Changes take effect after the PCoIP agent service restarts or the VM reboots.

Management and Policy

Define MDM policies before sealing your golden image. A baseline for Orka VDI: Do not apply aggressive idle timeout or auto-sleep policies that conflict with active session stability. See VDI Golden Image Management for incorporating MDM configuration into your image build pipeline.

Backup and Recovery

Keep machines in an always-on or wake-on-network state. Maintain a secondary administrative connection (VNC or MacStadium secure console) that does not depend on your VDI session. Enable Time Machine or equivalent backup on a schedule that meets your retention requirements. VDI sessions are not a substitute for enterprise backup.

Quick Reference

Related: