Skip to Main Content
Patch My PC Ideas & Feedback

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:

3 VOTE
Status SUBMITTED
Created by Guest
Created on Sep 1, 2025

macOS: Citrix Workspace

macOS: Citrix Workspace Application Packaging Request

Why is it Useful?

Packaging the Citrix Workspace app for macOS provides a standardized, automated, and scalable way to deploy, configure, and maintain the application across multiple Macs in an organization. This is essential in environments where centralized IT management is expected, such as in:

  • Enterprises with remote desktop infrastructure

  • Schools using virtual labs

  • Healthcare systems accessing cloud-based EHR

  • Call centers and BPOs needing secure remote access

Key benefits:

  • Automated Deployment: No need for manual installations across each Mac.

  • Consistency: Ensures the same version and configuration across the fleet.

  • Security: Predefined and locked settings reduce misconfigurations and vulnerabilities.

  • Scalability: Easily deploy to hundreds or thousands of machines using tools like Jamf, Munki, Intune, etc.

  • Maintenance: Simplifies patching and updates.


Who Would Benefit?

  • IT Admins/Enterprise SysAdmins: Streamlines workflows and saves time.

  • Security Teams: Ensures compliance with organizational access policies.

  • End Users: Gain a working Citrix environment out of the box.

  • Managed Service Providers (MSPs): Helps maintain multiple client environments efficiently.


How Should It Work?

Here’s a general overview of how the Citrix Workspace macOS packaging should be structured and function:


1. Package Contents

  • Installer Package (.pkg) of Citrix Workspace

  • Post-install scripts (optional) to apply custom configurations

  • Configuration profiles (.mobileconfig) or plist files to enforce settings


2. Configuration Capabilities

Should support configuration of:

  • Default Store URL (e.g., https://company.cloud.com)

  • SSO settings (e.g., enabling Pass-through authentication)

  • Auto-updates (enable/disable)

  • Log upload settings

  • Receiver cleanup (to remove older installations)


3. Packaging Tools Compatibility

Should be compatible with common macOS deployment tools:

  • Jamf Pro

  • Munki

  • Intune

  • DEP (Apple Device Enrollment Program)


4. Update & Maintenance Support

  • Regular updates should be scriptable or handled via MDM

  • Ability to auto-remove older versions during deployment

  • Support for background updates or prompts


5. Logging & Reporting

  • Logging during install to validate deployment

  • Error reporting to system logs

  • Ability to integrate with tools like Splunk, if needed

  • Attach files
  • +2