Profile Management: File Type Association (FTA) Fails to Roam on Windows 10 and Windows Server 2016

On Windows 10 and Windows Server 2016, Microsoft introduced a new security mechanism to check settings of default applications in the registry. Occasionally, the Windows Profile Service changes the security settings of the user registry entry. As a result, the settings of default applications are reset to Microsoft recommended defaults.

When testing Windows 10 and Windows Server 2016 without a VDA installed, this issue does not happen. Citrix is working with Microsoft to provide a long term solution. In the meantime, use the following workaround to avoid this issue.

Related:

  • No Related Posts

Legacy graphics mode with Windows 8, 8.1, 10, Server 2012, R2 & 2016

Legacy graphics is a host (computer) policy and its use should be treated as an always on or always off. Behavior will differ between Workstation OS VDA and Server OS VDA. You should only ever be using legacy mode for OS’s for which it was designed for: i.e. Windows 7, Windows 2008 R2 and earlier (also called Legacy OS’s). Legacy graphics is highly optimised for legacy OSs and should be regarded as the first choice for those operating systems unless other factors are involved.

Legacy graphics mode is not tested or supported with modern operating systems: Windows Desktop OS: 8, 8.1, 10 or Windows Server 2012, 2012 R2 & Windows Server 2016.

Thinwire plus (aka: TW+ or compatibility mode) should be used instead and is the replacement for legacy mode.

The above doesn’t necessarily mean it will not work with modern operating systems. However, issues like: grey, frozen and black screens have been observed and reported.

Before calling your support representative please test the issue against Thinwire, the modern graphics delivery method.

Related:

  • No Related Posts

Recommended Hotfixes for XenApp 7.x

The following Citrix and Microsoft hotfixes are found to resolve the most common issues with XenApp/XenDesktop 7.6, and XenApp/XenDesktop 7.5 running on a Windows Server 2008 R2 or a Windows Server 2012 R2 platform. These hotfixes focus on basic functionality and stability.

Note :

1. Fixes for Current Releases will likely be released in the next Current Release; therefore, it is less likely that an individual fix would be released for a Current Release version. You may be asked to upgrade to the next version of a Current Release that includes the requested fix and new functionality.

2. This article aims to describe the recommended hotfixes before Citrix LTSR(7.6.300) and Citrix CR(7.7~7.14). Please go to docs.citrix.com for more hotfixes regarding LTSR and CR.

Issue: Attempts to restart the Citrix Device Redirector Service from within a VDA or RDP session can cause the service to remain in an unresponsive state rather than actually restarting.

Available Software Updates:

ICAWS760WX64047 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit) – English
ICAWS760WX86047 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64053 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

Issue:

  • The operating system experiences an error on picadm.sys and a blue screen appears with stop code 0x20.
  • A deadlock on picadm.sys can cause published applications to become unresponsive.
  • The operating system experiences an error on picadm.sys and a blue screen appears with stop code 0x50.
  • The VDA might become unresponsive at the “Welcome” screen due to a deadlock on picadm.sys.
  • Remote Desktop (RDP) connections to the server fail.

Available Software Update:

ICATS760WX64048 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue: Certain third-party published applications might fail to start on XenApp servers. As a result, the wfshell.exe process might close unexpectedly. When this error occurs, no indication that the session is starting or error messages appear on the user device.

Available Software Updates:

ICAWS760WX64042 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit)-English
ICAWS760WX86042 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64040 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue: Citrix XenApp 7.6 and XenDesktop 7.6 VDA Core Services running on Windows Server 2008 R2 (Server OS) might become unresponsive at the “Welcome” screen. If this occurs, new Receiver and Remote Desktop (RDP) connections to the server fail.

Available Software Updates:

ICAWS760WX64026 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit) – English
ICAWS760WX86026 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64032 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue: The Citrix Stack Control service quits unexpectedly if there is an invalid session key.

Available Software Update:

ICATS760WX64006 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

XenApp 7.5/ 7.1

Issue:

  • The memory consumption of the Monitoring Service can grow steadily until the service stops responding to requests from Director, eventually rendering Director unresponsive as well.
  • If the resource name (display name) changes on the Delivery Controller, users who previously subscribed to the applications cannot start the applications.
  • If you create virtual machines (VM) with Desktop Studio that uses Machine Creation Services and the VMs are hosted on a VMware hypervisor, attempts to update VMs that are part of the machine catalog fail.

Available Software Updates:

Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x64 – English
Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x86 – English

_______________________________________________________

Issue:

  • VDAs can becomes stuck in the “initializing” state of registration process. The issue occurs after the Citrix Desktop Service is running for several days without being restarted.
  • When the function “CName” is enabled, VDA registration can take excessively long.

Available Software Updates:

BrokerAgent750WX64003 – For Broker Agent 7.1/7.5 for Windows OS (64-bit) – English
BrokerAgent750WX86003 – For Broker Agent 7.1/7.5 for Windows OS (32-bit) – English

_______________________________________________________

Issue: Installing hotfixes for XenApp 7.5, and XenDesktop 7.1 and 7.5 VDA Core Services for Windows Desktop and Server OS released before September 2014 causes the ICA Session performance monitor counter to be removed. This can have an adverse effect on the operation of tools and processes that rely on these counters.

Available Software Updates:

ICAWS750WX64011 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English
ICAWS750WX86011 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English
ICATS750WX64011 – For VDA Core Services 7.1/7.5 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue:The Citrix Print Manager Service (CpSvc.exe) process might exit unexpectedly.

Available Software Updates:

ICAWS750WX64019 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English
ICAWS750WX86019 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English
ICATS750WX64019 – For VDA Core Services 7.1/7.5 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue:

  • This fix addresses an intermittent high memory utilization issue of the Broker Service on the Controller.
  • This fix addresses a memory consumption issue of the Monitoring Service.

Available Software Updates:

Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x64 – English
Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x86 – English

Note:

Refer to the complete list of all the available HotFixes for

XenApp 7.6 64-bit32-bit

XenApp 7.5 64-bit32-bit

Microsoft HotFixes (including links to Microsoft HotFix list)

Windows Server 2012 R2 contains most of the following hotfixes (exceptions noted inline). Microsoft has published the following KB article specific to Remote Desktop Services: Available Updates for Remote Desktop Services (Terminal Services) in Windows Server 2012 R2. For Microsoft Hotfixes applicable to the Windows Server 2008 R2 and the Windows 7 platforms, see the “Microsoft Hotfixes” section in the following article: CTX129229 – Recommended Hotfixes for XenApp 6.x on Windows Server 2008 R2.

Note: The descriptions of the Microsoft fixes listed in this article (CTX142357) might not match the descriptions in the Microsoft articles for the following Microsoft fixes. This is not an error. The issue description listed by Citrix in the following matrix was resolved by an earlier version of that file however it has been superseded by the article/fix currently listed.

KB Number Issue description
KB3033929
  • UPM driver load breaks if this KB is not applied.
KB3078676 – NEW
  • This article describes an issue in which even 1530 is logged, and user profile service (ProfSvc) leaks paged pool memory and handles in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. This issue occurs if the ProfSvc service loads and then unloads a user profile. Additionally, the following event is logged in the Event viewer: Event ID 1530. Description: Windows detects your registry file is still in use by other applications or servers. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required.
KB3127673 – NEW
  • The Stop error 0x000000C2 might be caused by an error handling issue in the win32k.sys file.
  • The Stop error 0x0000003B might be caused by a synchronization issue in the dcgkrnl.sys file.
  • The parameters in Stop error messages may vary, depending on the configuration of the computer.
  • Not all “Stop 0x000000C2” errors or “Stop 0x0000003B” errors are caused by one of these issues.
KB3055615 – NEW
  • A windows Server 2012 R2 Server becomes slow and unresponsive if update 2927901 is installed.
  • You have update 2927901 installed on a Windows Server 2012 R2 server.
  • You have users who frequently log in and log off the server through Remote Desktop.
KB3013769
  • Memory leak occurs when you create or delete CSV snapshots by using a VSS hardware provider
  • IIS crashes occasionally when a request is sent to a default document in Windows 8.1 or Windows Server 2012 R2
  • You receive Stop error 0xD1 in Windows Server 2012 R2 or Windows 8
  • Device does not exist error after you reinsert a USB COM port device
KB2978367
  • Remote Desktop session freezes when you run an application in the session in Windows 8.1 or Windows Server 2012 R2.
KB2967077
  • A network printer is deleted unexpectedly in Windows
KB2895698
  • Users who have the remote audio setting enabled cause the RD Session Host servers to freeze intermittently in Windows Server 2012 R2 or Windows Server 2008 R2 SP1
KB2896328
  • You are logged on with a temporary profile to a remote desktop session after an unexpected restart of Windows Server 2012
KB2852483
  • Memory leak occurs in the Dwm.exe process on a Remote Desktop computer that is running Windows 8 or Windows Server 2012
KB2995388
  • Memory leak occurs when you play mp4 files in Windows 8.1 or Windows Server 2012 R2
  • Computer freezes when you switch to another account in Windows 8.1 or Windows Server 2012 R2
  • An NTFS volume is flagged as dirty after each restart, and CHKDSK can find no issues
  • Print jobs are intermittently processed slowly through Windows 8.1-based or Windows Server 2012 R2-based printer servers
  • Network printers that use TCP/IP port cannot print after first document has printed in Windows

Related:

  • No Related Posts

Error: “The remote session was disconnected because there was no terminal server license server available to provide a license”

Windows 2003 Terminal Servers do not recognize the Windows 2000 Licensing server and the following error occurs:

“The remote session was disconnected because there was no terminal server license server available to provide a license.

User-added image

The following event ids are logged:

Event ID 1004: No Terminal Server licenses available.

Event ID 1011: There are no Terminal Server licenses available.

Users cannot log on to a session using either ICA or RDP.

Background

Microsoft stated that Windows 2003 Server serves the Windows 2003 Terminal Server licensing. In the old licensing scheme, the licensing was on an Active Directory controller but in Windows 2003 this is no longer a requirement.

Refer to Q279561 Microsoft technote to install a Windows 2003 Server and point all Terminal Server users to the installed license.

Note: Windows XP and pre-release client OS requires TS License of 2003. Vista, Windows 7 and later require license from 2008 Terminal Server.

Related:

  • No Related Posts

Error: “No Audio Available, Could Not Open An Audio Device For Playback” In ICA Session

Complete the following steps on Win 7 and 2008 R2.

  1. First check if RDP- Tcp and ICA- Tcp does not have audio disabled. Go to Administrative tools-> Remote Desktop Session Host Configuration-> RDP-tcp-> Right click-> Properties-> Client Settings. Audio option should be unchecked. Similarly check for ICA-Tcp connection.
  2. Allow Citrix client audio redirection policy in studio console.
  3. Run gpupdate /force on the VDA server.
  4. Verify that Receiver setting for audio is enabled in connection center.
  5. We should be able to get audio working in ICA session.

Steps to be followed on Win 8 and 2012 R2 and above.

Due to the changes in Server 2012 R2, there is no option to modify RDP listener in RDMS (Remote Desktop Management Server) GUI, hence to enable this Audio Redirection in 2012 R2 server, follow the below steps:

  1. Choose Start, choose Run, enter regedit, choose the OK button, and then set the value of the following registry key to 0.
  2. Go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp, Edit or create

Value: fDisableAudioCapture

Type: REG_DWORD

Data : 0

Related:

  • No Related Posts

Error: “No Audio Available, Could Not Open An Audio Device For Playback” In ICA Session

Complete the following steps on Win 7 and 2008 R2.

  1. First check if RDP- Tcp and ICA- Tcp does not have audio disabled. Go to Administrative tools-> Remote Desktop Session Host Configuration-> RDP-tcp-> Right click-> Properties-> Client Settings. Audio option should be unchecked. Similarly check for ICA-Tcp connection.
  2. Allow Citrix client audio redirection policy in studio console.
  3. Run gpupdate /force on the VDA server.
  4. Verify that Receiver setting for audio is enabled in connection center.
  5. We should be able to get audio working in ICA session.

Steps to be followed on Win 8 and 2012 R2 and above.

Due to the changes in Server 2012 R2, there is no option to modify RDP listener in RDMS (Remote Desktop Management Server) GUI, hence to enable this Audio Redirection in 2012 R2 server, follow the below steps:

  1. Choose Start, choose Run, enter regedit, choose the OK button, and then set the value of the following registry key to 0.
  2. Go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp, Edit or create

Value: fDisableAudioCapture

Type: REG_DWORD

Data : 0

Related:

  • No Related Posts

Error: “No Audio Available, Could Not Open An Audio Device For Playback” In ICA Session

Complete the following steps on Win 7 and 2008 R2.

  1. First check if RDP- Tcp and ICA- Tcp does not have audio disabled. Go to Administrative tools-> Remote Desktop Session Host Configuration-> RDP-tcp-> Right click-> Properties-> Client Settings. Audio option should be unchecked. Similarly check for ICA-Tcp connection.
  2. Allow Citrix client audio redirection policy in studio console.
  3. Run gpupdate /force on the VDA server.
  4. Verify that Receiver setting for audio is enabled in connection center.
  5. We should be able to get audio working in ICA session.

Steps to be followed on Win 8 and 2012 R2 and above.

Due to the changes in Server 2012 R2, there is no option to modify RDP listener in RDMS (Remote Desktop Management Server) GUI, hence to enable this Audio Redirection in 2012 R2 server, follow the below steps:

  1. Choose Start, choose Run, enter regedit, choose the OK button, and then set the value of the following registry key to 0.
  2. Go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp, Edit or create

Value: fDisableAudioCapture

Type: REG_DWORD

Data : 0

Related:

  • No Related Posts

Error: “No Audio Available, Could Not Open An Audio Device For Playback” In ICA Session

Complete the following steps on Win 7 and 2008 R2.

  1. First check if RDP- Tcp and ICA- Tcp does not have audio disabled. Go to Administrative tools-> Remote Desktop Session Host Configuration-> RDP-tcp-> Right click-> Properties-> Client Settings. Audio option should be unchecked. Similarly check for ICA-Tcp connection.
  2. Allow Citrix client audio redirection policy in studio console.
  3. Run gpupdate /force on the VDA server.
  4. Verify that Receiver setting for audio is enabled in connection center.
  5. We should be able to get audio working in ICA session.

Steps to be followed on Win 8 and 2012 R2 and above.

Due to the changes in Server 2012 R2, there is no option to modify RDP listener in RDMS (Remote Desktop Management Server) GUI, hence to enable this Audio Redirection in 2012 R2 server, follow the below steps:

  1. Choose Start, choose Run, enter regedit, choose the OK button, and then set the value of the following registry key to 0.
  2. Go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp, Edit or create

Value: fDisableAudioCapture

Type: REG_DWORD

Data : 0

Related:

  • No Related Posts

Error: “No Audio Available, Could Not Open An Audio Device For Playback” In ICA Session

Complete the following steps on Win 7 and 2008 R2.

  1. First check if RDP- Tcp and ICA- Tcp does not have audio disabled. Go to Administrative tools-> Remote Desktop Session Host Configuration-> RDP-tcp-> Right click-> Properties-> Client Settings. Audio option should be unchecked. Similarly check for ICA-Tcp connection.
  2. Allow Citrix client audio redirection policy in studio console.
  3. Run gpupdate /force on the VDA server.
  4. Verify that Receiver setting for audio is enabled in connection center.
  5. We should be able to get audio working in ICA session.

Steps to be followed on Win 8 and 2012 R2 and above.

Due to the changes in Server 2012 R2, there is no option to modify RDP listener in RDMS (Remote Desktop Management Server) GUI, hence to enable this Audio Redirection in 2012 R2 server, follow the below steps:

  1. Choose Start, choose Run, enter regedit, choose the OK button, and then set the value of the following registry key to 0.
  2. Go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp, Edit or create

Value: fDisableAudioCapture

Type: REG_DWORD

Data : 0

Related:

  • No Related Posts

Error: “No Audio Available, Could Not Open An Audio Device For Playback” In ICA Session

Complete the following steps on Win 7 and 2008 R2.

  1. First check if RDP- Tcp and ICA- Tcp does not have audio disabled. Go to Administrative tools-> Remote Desktop Session Host Configuration-> RDP-tcp-> Right click-> Properties-> Client Settings. Audio option should be unchecked. Similarly check for ICA-Tcp connection.
  2. Allow Citrix client audio redirection policy in studio console.
  3. Run gpupdate /force on the VDA server.
  4. Verify that Receiver setting for audio is enabled in connection center.
  5. We should be able to get audio working in ICA session.

Steps to be followed on Win 8 and 2012 R2 and above.

Due to the changes in Server 2012 R2, there is no option to modify RDP listener in RDMS (Remote Desktop Management Server) GUI, hence to enable this Audio Redirection in 2012 R2 server, follow the below steps:

  1. Choose Start, choose Run, enter regedit, choose the OK button, and then set the value of the following registry key to 0.
  2. Go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp, Edit or create

Value: fDisableAudioCapture

Type: REG_DWORD

Data : 0

Related:

  • No Related Posts