Getting Citrix Desktop Lock 4.2 to work in your environment

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:

Storefront Configuration

XenDesktop Delivery Controller Configuration

Group policy configuration

Desktop Configuration

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!

1. Storefront Configuration:

Create a new store to work with specifically for single sign on to avoid messing with your production users. (This is not mandatory, but highly recommended)

On the target storefront store, modify the following configuration files:

After saving both files, be sure to replicate your changes across your Storefront server group, if you have multiple storefront servers in your environment.

Now, on all your storefront servers, we must enable windows authentication from within IIS manager on the particular store we’re targeting for use with Desktop lock. To do this, do the following:Browser for the site that we’re configuring for desktop lock, Clicked into configuration editor for the site, In configuration editor, selected system.webServer, Then expanded out Security – authentication, Clicked into windowsauthentication and enabled it.This is a step that I missed during my configuration and took a while to figure out.

Perform an IISRESET on all storefront servers in scope.

2. XenDesktop Delivery Controller Configuration:

Log on the Delivery Controller(s), then open Windows PowerShell and execute the following commands to enable the Delivery Controller to trust XML requests sent from StoreFront:

If not already loaded, load the Citrix cmdlets by typing asnp Citrix*. (be sure to include the period after Citrix*).

Make sure to reboot after the installation. Rebooting will allow the Receiver single sign-on service to start. Upon reboot, make sure you see ssonsvr.exe running in processes of task manager:

Now let’s test the receiver agent and that single sign on is working. This is an important validation, because if this doesn’t work, then logging in using desktop lock, certainly will not work. To do this, launch the citrix receiver by going to the system tray/notification area and right-clicking on the citrix receiver icon and choosing ‘Open’. From there, it will launch the Citrix Receiver with the default ‘Storefront Green’ background. In the top middle/right you’ll have a link that reads ‘Log On’. Upon clicking, it should not prompt you to enter your credentials again; it should actually just log you in to the receiver and you should see your desktop(s) on the left-hand tab as in the following screenshot:If you receive the same result above, this would validate that the local machine ssonsvr.exe and citrix receiver are working properly. You can proceed to the final step.

Install Citrix Desktop Lock – and test. Feel free to drop me a line here if you run into any issues. Chances are I’ve had the same error you’re seeing now and will be able to offer some guidance.

Feel free to comment if you have any questions. There is a lot involved here. Special thanks to Juan Guerra @ Citrix Support again for the assist here. Good luck!

Comments

Great Post, how ever I am having issues where once a user has signed out after being signed in the user is unable to sign back in until I manually kick them off the server. Is this a known issue or has anyone else had a similar issue?

@Chris, haven’t seen that behavior in our environment although I’ve seen some other oddities. Maybe check the Citrix forums and see if you find anything. I would also suggest running a trace when you’re able to re-create the issue.

d_morris, you say two types of thinclients. What do you mean by thin clients? If you’re using a thin client, you really wouldn’t need Desktop Lock, as the thin client would serve as the single sign-in you’re looking for. Shoot me an e-mail and I’ll help you discuss a little further: http://nickyfixit.com/get-in-touch/

Hi David,My name is Amjad and i am working on one poejrct, where App-DNA and App-V is used by organization for virtualization.I am getting problem in after getting the App-DNA result green for application we want to automate the system to complete the App-V sequence and get the virtual file to deploy.I am running App-DNA and APP-V both on same VM window 7 x32 bit machine.Please let me know after application analysis done how i start the App-V sequencer automatic .Please send me document or process notes Thank you for helpRegards,AJ