$CustomShell = $ShellLauncherClass.GetCustomShell($Users_SID) $ShellLauncherClass.SetDefaultShell("explorer.exe", 0) # This well-known security identifier (SID) corresponds to the BUILTIN\Administrators group and BUILTIN\Users. # Create a handle to the class instance so we can call the static methods. $null = Enable-WindowsOptionalFeature -Online -FeatureName "Client-EmbeddedShellLauncher" -All If ((Get-WindowsOptionalFeature -Online -FeatureName "Client-EmbeddedShellLauncher").state -eq "Disabled") In order to enable and configure this solution we created the following PowerShell script: $SelfServicePath = Get-Item "C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe" -ErrorAction Stop The solution we ended up using is to utilize Windows Shell Launcher feature to launch Selfservice.exe. The obvious solution to this problem would be to increase the timeout for Desktop Lock, however we weren’t able to find a way to do this. Users don’t always use the same client so they’ll experience this bug once on every client. After the second login things work fine because the profile is already present. This is because creation of the users local Windows profile on Windows 10 takes too long causing Desktop Lock to time out. We’re in the middle of a Windows 10 migration for one of our customers and noticed the following issue: after installing Windows 10 on a client machine with Citrix Workspace App Desktop Lock as the shell the first time a user logs in Desktop Lock will fail and the user will be logged out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |