1 Rookie

 • 

3 Posts

November 2nd, 2010 16:00

You could also do something like a default autologin with a user that has little to no local/network privledge and launches into Thinshell to authenicate the users 'real identity' to a desktop/application served via vWorkspace.  But, then the end user also has the option to 'log off' of thin shell and connect to the local explorer.exe shell for local computing.  The article Rick references is helpful in this as well.

1 Rookie

 • 

48 Posts

October 30th, 2010 10:00

Hi Francois,

I guess the answer is yes and no. The default shell can be determined either on a machine basis (HKLM\Software\Microsoft\Windows NT\Winlogon, shell) or on a per-user basis (HKCU\Software\Microsoft\Windows NT\Winlogon, shell), so if you use a group policy, you could assign a different per-user shell depnding on security group membership.

http://msdn.microsoft.com/en-us/library/ms838576(WinEmbedded.5).aspx has a detailed description of the options.

I guess you could have 2 logins for users, one local and one AD and define the shell that way, however otherwise you would have to have a custom GINA to allow that sort of selection pre-login.

regards,

Rick

101 Posts

July 2nd, 2015 04:00

Thinshell does have two modes available.  Native and Shell.  Native will not allow any choice of applications to users but if you use Shell mode then you can.

more details here: http://en.community.dell.com/techcenter/virtualization/vworkspace/b/vworkspace-blog/archive/2012/06/13/thinshell-2-5-native-mode-v-shell-mode

No Events found!

Top