Network Level Authentication - AppPortal Auto-Launch Application

Question

We are moving from our Proof-of-Concept into a vWorkspace Pilot and I need to have the AppPortal Auto-Launch a Desktop Application (VM) after the user logs into the repurposed desktop computer.  Everything have been setup and works fine if the user authenticates at each entry point (PC, AppPortal, VM) but fails during the autologin due to the requirement of NLA.  I have set and checked all required settings and configurations within Group Policy, however the login's continue to fail.  I discovered that our GP's are still based off of Server 2003 but the needed Server 2008 R2 / Windows 7 GPO templates were imported. Does anyone know what might be the problem? Thank! Patrick

david.caddick-q · Accepted Answer

Hi Patrick, Perhaps this post by my colleague Rick Mack might help: How to enable Single Signon (SSO)in vWorkspace for Vista/Windows 7 clients with Kerberos against Server 2008 R2 Cheers, Dave

rmack1 · Answer

Hi Patrick,

I'm not 100% certain whether I'm answering the right question because your description is a tiny bit vague.

I would guess that you want to enable transparent passthrough authentication. This is going to be dependent on a lot of different pieces depending on the level at which you are doing your primary authentication. If the repurposed PCs are still domain members then installing the vWorkspace client with legacy SSO support should take care of things for you. If you're using thinshell, then that can handle the authentication for you.

The last step is passing user credentials by AppPortal to the vWorksce client and virtual host. This should work but Windows 7/Server 2008 RDSH adds some additional security which effectively breaks passthrough Kerberos authentication. I've got a blog article here that covers the user of CREDSSP. If that doesn't help you then I'll need a bit more information before I can point you in the right direction.

regards,

Rick

craditp · Answer

Thanks for the feedback, and I'm going back through the process again so I can provide better details of the issues I'm seeing on my end. I will post the information as soon as I'm finished!

Thanks,

Patrick

craditp · Answer

Here are a few screenshots taken when I first ran across the NLA issue. The first screenshot was taken after discovering the Group Policys were preventing NLA from being selected.

So, I created a new OU for the vWorkspace Pilot and blocked Inheritance so I could configure the required policies. After making those changes, I'm still getting the following:

vWorkspace

Was this post helpful?