VMware Horizon Community
jmatz135
Hot Shot
Hot Shot

Citrix Receiver in Appstack Single Sign On doesn't work properly

If I put Citrix Receiver within an appstack the single sign on functionality doesn't work properly.  When I go to the Citrix Storefront webpage it does sign me in using my logged on credentials, but if I launch a Xenapp application it then prompts for credentials within the Xenapp rdp session.  If I install Citrix Receiver on the base image everything works as expected.  Has anyone else seen this issue and have any insights into how to get this to work in an appstack?

0 Kudos
4 Replies
anujp
VMware Employee
VMware Employee

Would you mind providing App Volume Manager & Agent version info? Snippet of svservice & svdriver log would be recommended as well.

0 Kudos
jmatz135
Hot Shot
Hot Shot

It doesn't work with App Volumes agent 2.11 or 2.12.1 and manager server 2.12.1.  I'll try to get the appvolumes logs soon. 

0 Kudos
Tomas_Iskra
Contributor
Contributor

Hi All,

We are having the same problem.

When Receiver ICA Client is installed on an App Volume, single sing on process is not running when the volume is attached.

Process is called ssonsvr.exe.

Receiver installation creates a new Network Provider registry value (PnSson) under:

* HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder

- ProviderOrder     REG_SZ     PnSson

* HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

- ProviderOrder     REG_SZ     PnSson

It also creates an entry under under HKLM\SYSTEM\CurrentControlSet\services\PnSson

pastedImage_0.png

I can see the 2nd value present on the machine when AppStack is attached, however I do not see the 1st two network provider entries.

I went through the snapvol.cfg file to make sure these locations are not excluded and they are not.

I modified a startup.bat script to change the registry values so they show PnSson network providers.

pastedImage_1.png

This fixed the problem when AppStack was attached (to hostname) to my clean provisioning machine.

However as soon as this is attached to standard virtual machine (either via username or hostname), it doesnt launch the ssonsvr.exe process even though NetworkProviders are showing up properly (thanks to the script) and therefore preventing single sign on feature to work properly.

I would appreciate any ideas on how this can be resolved.

Thank you.

0 Kudos
FlowDE
Contributor
Contributor

Hey,

could someone solve this issue?

Greetings

Justin

0 Kudos