*Product*: Citrix Workspace app for Mac 2603.10 I...
# citrix-workspaceapp
a
Product: Citrix Workspace app for Mac 2603.10 I appreciate the continuous modernization of solutions, including the transition from Secure ICA to Secure HDX in the Citrix Workspace app for Mac. However, announcing a deprecation and completely removing a feature in the exact same release (version 2603.10) deprives IT teams of the critical runway needed for a seamless transition. Forgoing a proper grace period for such an impactful architectural change poses unnecessary challenges to stable infrastructure management. Moving forward, I hope Citrix returns to the standard practice of providing advance notice for feature retirements, showing greater consideration for their customers' time and operational overhead.
💯 4
Update: The depreciation was announced in the CVAD 2402 LTSR documentation but without a specific implementation date.
s
Arthur, as you mentioned, Secure ICA deprecation was announced in CVAD 2402. Secure HDX has been available on CWA for Mac since 2409. I think there is a correction that needs to be made in the CWA for Mac docs to accurately reflect that. The norm is to announce deprecation of a functionality and eventually remove it in a future release. Due to prioritization constraints and unknown variables, it is difficult to provide a removal date at the time of deprecation announcement.
💯 1
a
@Saurabh Bisani Thanks Saurabh, doc fix aside, removing Secure ICA from CWA for Mac in the same release it was deprecated (2603.10) is a serious mistake. The client has no LTSR to pin to, so the first bug or CVE forces users onto a build that already dropped it, with no safe path back. Removal can't track the client's release cadence, it has to track the backend: as long as a customer's CVAD still supports Secure ICA, CWA must keep supporting it too, and only drop it once the infrastructure itself stops supporting it. The core expectation is simple: if the infrastructure supported something yesterday, it should still work today. Admins shouldn't wake up to a previously compliant environment that is suddenly broken by a client update. Bottom line, this is a strategic miss that undermines trust in the platform, and that trust is far harder to rebuild than any single feature is to keep.