Having issues with users reconnecting a disconnected Citrix Virtual Apps and Desktops session? These keys might help you. Citrix support confirmed, that they help starting at Server 2016 VDA.

Fastreconnect is a feature that was introduced by Microsoft to enhance session reconnect through RDP, but through Citrix ICA it seems that is does not improve anything.

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Reconnect
FastReconnect REG_DWORD 0

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\GroupPolicy
EnforceUserPolicyEvaluationSuccess REG_DWORD 0

References:

https://www.reddit.com/r/Citrix/comments/x6frfq/ltsr_2203_disconnected_sessions_are_lost_upon/

Having grey screen issues with CVAD 2203+ and higher on Windows Server 2022 Terminal server? I had this issue occurring on Citrix 2212. Try running this script. It might help you out. Do a VM backup or snapshot before running the script, just to be sure.

$iddHwId = “VEN_5853&DEV_1003”
$pnpDispDevPath = “HKLM:\SYSTEM\CurrentControlSet\Enum\SWD\RemoteDisplayEnum”

try
{
    $iddDevEntries = Get-ChildItem -Path $pnpDispDevPath -ErrorAction Stop| Where-Object Name -Match $iddHwId
}
catch
{
    Write-Output “Failed to query remote ID device entries”
    Write-Output $_
    return
}

if ($iddDevEntries.Count -eq 0)
{
     Write-Output “No remote ID device entries found.”
     return
}

$iddDevEntries | ForEach-Object {
    
    $devName = ($_.Name -Split “\\”)[-1]
    
    try
    {
        Remove-ItemProperty -Path $_.PsPath * -ErrorAction Stop
        Write-Output “Cleared values for $devName”
    }
    catch
    {
        Write-Output “Failed to clear values for $devName”
        Write-Output $_
    }
}

This saved my day:

https://discussions.citrix.com/topic/417832-cvad-connectionfailure-after-install-ltsr-2203-cu2-on-server-2022/page/3/

Having odd issues with the task bar/random task bar freezing on Windows Server 2022 RDS? Or explorer.exe using around 10% of the CPU for every user that is logged in? This might save your day. This issue occurs if you have MS Teams installed on the RDS.

First of all, export the registry path HKLM\SYSTEM\Software\Microsoft\TIP\TestResults\27641370 and look at the file size. If it is around 40MB in size, then you have the same issue.

To resolve the issue, delete the key and disable the TabletInputService service (Touch Keyboard and Handwriting Panel Service). Afterwards, take ownership of C:\Program Files (x86)\Common Files\Microsoft Shared\ink\TabTip32.exe and C:\Program Files\Common Files\microsoft shared\ink\TabTip.exe and rename both executables into TabTip32.exe.orig/TabTip.exe.orig.

After that, reboot your server.

References:

https://learn.microsoft.com/en-us/answers/questions/909494/windows-2022-server-rds-laggyslow-taskbar.html

https://learn.microsoft.com/en-us/answers/questions/752491/server-2022-and-teams-bloats-hkey-local-machinesys.html

Just recently I learned that Microsoft ClickOnce Applications are a pain in the ass and cannot be published as Published Applications the usual way through Citrix Virtual Apps and Desktops.

Usually the message below shows up before starting or installing the application (which is on a user basis – I absolutely hate that. Thanks for that Microsoft and Developers). If you try to publish the file ending with .application nothing will happen.

Creating a BAT file and publishing that bat file will show the prompt and the desired application will start:

cd /d “C:\Windows\Microsoft.NET\Framework\v4.0.30319”

start dfsvc.exe

start “C:\Program Files (x86)\Internet Explorer\iexplore.exe” “http://webserver/app”

This does also work:

start “C:\Program Files (x86)\Internet Explorer\iexplore.exe” “\\fileserver\share$\bestsoftware.application”

Kudos:

https://www.nomadit.xyz/clickonce-prompt-for-citrix-published-app/

When trying to install the Teams system-wide on an RDS, you might get this error stating that no VDI environment was detected:

msiexec /i “Teams_windows_x64.msi” ALLUSER=1

This is because the installer checks if these registry entries are present on the system (Citrix or VMware):

HKLM\Software\Citrix\PortICA DWORD ALLUSER 1

So the solution is easy: just manually add the Citrix key you are good to go. Teams should work just fine on a RDS that is not provisioned by Citrix or VMware Horizon (why shouldn’t it?).

References:

https://www.masterpackager.com/blog/mst-to-install-microsoft-teams-msi-vdi-to-regular-windows-10