This is related to only one login issue
Check event logs, by filtering with warnings and errors on citrix delivery controller. When you check event logs, if you see a profile related error, goto profilestorepath\profile\userid\upm_profile. Look for ntuser.dat file. You will also have ntuser.dat.lastgoodload file. In citrix delivery controller event viewer, if you see any error for profile redirection, you can backup and remove ntuser.dat file, rename ntuser.dat.lastgoodload file to ntuser.
Receiver Cleanup Utility:
You might want to uninstall existing receiver version and install same version or a newer version of citrix receiver in user’s machine. In this case, you can uninstall citrix receiver directly from add or remove programs but that might leave some registry keys, and folders back. So, it is always recommended to use citrix receiver cleanup utility to remove existing citrix receiver from a user’s machine.
Receiver cleanup utility is available for download from citrix support site, but each citrix receiver setup has receiver cleanup utility in it.
Some of the steps to troubleshoot citrix issues
Case 1:
Reset user’s profile. Check if application is using any share path to write any settings/values. Reset profile from that path, like any share path is mounted in application and user’s profile is created there. Check what shared drives are mapped to user’s profile. Open dsa.msc and check if there is any path provided under “profile” tab for home folder or user profile.
Issue: We recently came across an issue where users access netscaler gateway URL, login successfully, and click on their VDA icon. DesktopViewer.exe opens successfully and it shows a gray screen forever. They can only login after their VDA is restarted. Eventviewer is filled up with tdica errors as shown below:
1002: The Citrix ICA Transport Driver is waiting for connections on port 1494.
1002: The Citrix ICA Transport Driver is waiting for connections on port 2598.
Citrix policies with powershell: If you want to create multiple policies with lot of settings, that would be a difficult task for administrators while doing it manually. Studio is not that fast while responding to each setting. So, it would take lot of time and effort in doing it. How about automating policies creation task? Lets see how we can do it. Download and install latest citrix scout. I did not provide scout link as it might change time to time.
Exclude users from citrix policy:
Normally when we create a citrix policy, you have option to choose specific citrix/AD entities like shown below:
Assignment Name Assignment Description Access Control Applies a policy based on the access control conditions through which a client is connecting. Citrix CloudBridge Applies a policy based on whether or not a user session is launched through Citrix CloudBridge. Client IP Address Applies a policy based on the IP address (IPv4 or IPv6) of the user device used to connect to the session.
To know about LHC check out my post: https://www.knowcitrix.com/posts/local-host-cache-in-xendesktop/
To enable Local Host Cache, open powershell and enter:
Set-BrokerSite -LocalHostCacheEnabled $true -ConnectionLeasingEnabled $false
This cmdlet also disables the connection leasing feature. Do not enable both Local Host Cache and connection leasing.
To determine whether Local Host Cache is enabled, enter:
Get-BrokerSite
Check that the LocalHostCacheEnabled property is True, and that the ConnectionLeasingEnabled property is False.
To disable Local Host Cache (and enable connection leasing), in powershell console, enter:
Local Host Cache(LHC) was introduced back in citrix from 7.12 with new improvements. LHC is used to provide apps and desktops to users incase of database failure, with an exception of pooled VDIs. Users can connect to all their applications and VDIs(non-pooled VDIs, MCS and PVS) until database is back. Citrix also brought a new feature called connection leasing but LHC has more features than CL.
Local Host Cache is supported for server-hosted applications and desktops, and static (assigned) desktops; it is not supported for pooled VDI desktops (created by MCS or PVS).
Concepts of publishing
Master image A master image is an image used by the provisioning technology to create virtual machines (VMs) for your users. Depending on the provisioning technology used, the master image can also be used to create a machine to host applications and desktops. The master image, created and stored on your hypervisor, contains the operating system and common applications and settings you are providing to your users, such as:
Recreate LHC on the Delivery Controller by the following steps:
1. Download PsExec on the Delivery Controller
PsExec - Windows Sysinternals https://docs.microsoft.com/en-us/sysinternals/downloads/psexec
2. Stop Citrix High Availability Service
3. Run PsExec on Command Prompt and switch to Network Service account
> psexec -i -u “NT AUTHORITY\NETWORK SERVICE” cmd
> whoami nt authority\network service
4. Move to the path with SqlLocalDB
> cd “C:\Program Files\Microsoft SQL Server\120\Tools\Binn”
5. Stop/delete CitrixHA (LocalDB)
