After battling the configuration of getting Citrix Desktop Lock to work in our environment, I think I’ve got all the missing pieces documented. For some reason, I had trouble figuring this out even with the Citrix Desktop Lock documentation located here. I got it working in our US domain workstations, then a couple weeks passed by, and it was asked to get it working down in our Brazil office, and I had forgot all the steps involved. The purpose of this post is to memorialize all those steps in case there is a next time 🙂
For those of you who don’t know what Desktop Lock is, it’s add-on that runs on top of Citrix Receiver 4.2 and when installed properly on a domain-connected workstation, it passes the users AD credentials and logs them directly into their VDI desktop. This is super useful if you don’t have thin clients available and want to re-purpose existing desktops while improving user experience on VDI, ALL without actually spending any money except a little bit of time. Normally if you go from physical machine to VDI, the user is plagued with now having to deal multiple logins, multiple screensaver timeouts, etc. Desktop lock addresses this problem because now the user just logs into their physical desktop and it passes the credentials and logs the user directly into their default VDI desktop. When the user logs off of VDI, it logs them off of both the VDI desktop and physical machine they’re running lock from.
To make this as straight forward as possible, I’m going to break this out to a couple different areas here:
As you can tell, there a lot of different areas here that need some form of adjustment to get this to work – so let’s get to it!
(Refer to this article for more information: http://support.citrix.com/proddocs/topic/receiver-windows-42/receiver-windows-configure-passthrough.html)
CitrixReceiver.exe /includeSSON /ENABLESSON=Yes STORE0="Store;https://my.storefront.com/Citrix/YOUR_Store/discovery;on;STORENAME"