Home » receiver 3.0

Tag: receiver 3.0

HDX Volume control sync Server and Client broken

Citrix Support the volume control sync / mute of a Desktop session to also control the HDX media volume playing out on the client.

After upgrading to Citrix Receiver 3.0 this functionality stopped.
HDX Flash Content would be streamed to the client side and would play, but if the XenApp session volume was muted – the HDX content would continue to play – the only way to mute was via any flash enabled controls (if they existed).

If the XenApp session is ‘muted’ the HDX content will still stream to the end users desktop ignoring the controls in the session.

Most users do not notice or care

Resolution: (no permament solution found yet)
We have a call raised with citrix to investigate

Our temporary solution is rolling back clients to the 12.1 version of the citrix ICA Client.
Receiver 3.0 and Receiver 3.1 both do not sync volume controls.

This was tested on a Xen App 5.0 FR3 R01 farm and a brand spanking new XenApp 6.5 Farm – All failed with the Receivers 3.0 and 3.1.

We are not of the opinion this is related to anythign else in our environment other than the ICA Client / Receiver upgrade.

We await further results from citrix.

This feature has been removed as part of receiver 3.0 + as this was crashing the XP workstations / ica clients.

The feature is only availably in later model Clients OS (windows 7 for example) running the receiver, other wise ICA client 12.1 is the last client to support XP local HDX volume sync

Launching citrix apps fails with lock down requirements


After we removed the citrix desktop lockdown, and tried to launch a citrix desktop / application we received.

“Citrix online plug-in Configuration Manager: No value could be found for (ClientHostedApps) that satisfies all lockdown requirements. The lockdown requirements in force may be conflicting”.

1. goto HKEY_CURRENT_USERSoftwareCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownVirtual ChannelControl
2. Delete key ClientHostedApps as REG_SZ
(or worst case create it and set value to FALSE)


UPDATE 30/01/2013:

Upgrading from Citrix receiver 3.0 to 3.3 resulted in the same error when we upgraded our core desktop’s receiver (for end users to connect to second tier applications)

So far the only workaround we have is to delete the entire following key: HKEY_USERS%user_sid%SoftwareCitrixICA ClientEngineLockdown Profiles

More to come (hopefully)