Pin prompt for Smart card authentication is not available to login into VDA session. User is prompted for “Username” and “Password” instead of Smart card PIN to login into VDA session.
Microsoft has changed the way Smart Card Service (SCardSvr) works in Windows 10 v1803. The service will run only if a Smart Card reader is connected. As ICA sessions redirect the Smart Card, it finds the service not to be running and fails.
This issue would not be encountered if earlier Windows 10 machine with VDA installed is upgraded to 1803. For a clean install of Windows 10 v1803, Microsoft has provided a mechanism to enable to enable Smart Card Service (SCardSvr) by adding a registry key. To add the registry key, follow below steps on the VDA:
Caution! Refer to the Disclaimer at the end of this article before making changes to Registry
Right click on Start button and choose Run
Type ‘Regedit’ and click Ok.
On x86 machine, browse to HKEY_LOCAL_MACHINE -> Software -> Microsoft -> Cryptography -> Calais
On x64 machine, browse to HKEY_LOCAL_MACHINE -> Software -> WOW6432Node -> Microsoft -> Cryptography -> Calais
Right click on Calais in left pane, choose New -> DWORD (32 bit) value.
Enter the value as ‘AllowServiceAccessWithNoReaders’ and hit enter.
Double click on ‘AllowServiceAccessWithNoReaders’ and enter the value as 1.
Close Registry Editor and restart the machine.
Print command from inside an ICA session of Windows 10 v1803 client fails to print using mapped Citrix UPS configured XPS Printer.
XPS Viewer is not available on Windows 10 v1803 by default. It is available as a Feature on Demand.
To install XPS Viewer, follow the below steps:
- Open Command Prompt in elevated mode
- Run the command “Dism /online /add-capability /CapabilityName:XPS.Viewer~~~~0.0.1.0”
- The machine should be connected to the Internet for above command to acquire and install XPS Viewer.
- While upgrading from earlier Windows 10 version to v1803 using ISO, if option ‘Download and install updates’ is chosen XPS Viewer will be retained after upgrade.
Citrix Workspace Environment Management (WEM) Agent fails to work when Windows 10 is upgraded to v1803.
The ‘Norskale’ key under [HKLM -> System -> CurrentControlSet -> Control] is removed during the upgrade to v1803.
Citrix is working with Microsoft to resolve this issue. To restore functionality, users could uninstall WEM Agent on the upgraded machine, reinstall and reconfigure.
Some maximized applications in Local App Access(LAA) enabled desktop sessions cannot be minimized using the minimize button. (Example application: Notepad, CMD)
The issue is due to an incorrect function call getting triggered for LAA enabled desktops.
Citrix is working on a resolution for this issue. As a work around, users could resize the app and then minimize.
Citrix User Profile Manager (UPM) stops working after Windows 10 is upgraded to v1803.
After upgrade, UPM creates local profiles instead of using the shared profiles.
Citrix is investigating this issue. There is no work around for this issue.
With Windows 10 v1803 as PVS Target Device (PVS 7.15 CU2), when Cache Type for vDisk is set as ‘Cache in device RAM’, a BSOD is encountered while booting.
This issue could be due to Kernel changes made in Windows 10 v1803 which might be preventing the Citrix PVS bootstrap and drivers from using reserved memory for RAM cache.
Citrix is investigating this issue. As a workaround, “Cache in device RAM with overflow on hard disk” option can be used.
Note: This only affects Legacy bootstrap PXE booting, which includes BDM and ISO booting. Using UEFI bootstrap works fine, including UEFI BDM and ISO booting.