If you are noticing seemingly random RDS session freezing on Windows 10/11 clients, this registry key might help. It disables the UDP protocol for RDP connections, which Microsoft enabled by default since Windows 10 1809/1909. I have had this issue occur on Windows 10 21H2.
Having two logins for the same user isn’t practical for both the user and administrator. That’s why you should use this guide to convert a cloud user into an Azure AD Synced user. Having an Azure AD Synced user is very handy, because the user can then use one password for all the services he might need, plus you can combine login with Seamless Signon.
So you basically have this user in the Cloud:
That should be replaced by this on-prem user:
First of all, make sure that the on-prem user is not being synced.
Then connect to Microsoft Online through PowerShell. If you don’t have the module, install it first (hit y twice):
Link the objectGUID with the immutableID of the Cloud user:
Having issues with print redirection on Citrix Workspace for Mac OS? Try installing the HP Color LaserJet 2800 Series PS print driver on your terminal server (Server 2019 and newer). It sounds dumb, but Citrix Universal Print Driver (UPD) uses Postscript data that is developed by HP. You can read more about this in the Citrix article at the end of the page.
To install this print driver, open printmanagement.msc on your VDA. Open up Print servers > Servername > Drivers > Add Driver
And then Windows Update to check for drivers through Windows Update service.
If you don’t find the driver, manually download it through Windows Update Catalog, extract it with Winzip or 7Zip and select Have Disk…
Migrating the Citrix Site database to a new database server is pretty straight forward but needs to be planned since there is a downtime when making the switch.
First of all, take a backup of the database with SQL Server Management Studio and restore the database on the new server:
Select the file that has just been backed up.
Run a new query with CTRL + N and add the DDC’s (Delivery Controller) computer account:
create login [domain\ctx1$] from windows
Make sure the computer account has proper roles under Security > Logins > domain\ctx1$ > right click > properties (the computer account needs to have all permission ending with _ROLE in all three databases).
Step 1 is to remove the old database connection string:
Step 2 is to check whether you are able to connect to the new database server. If that does not work, the SQL Server Ports (UDP 1434 for SQL Server Browser and a high port for the SQL server instance) need to be enabled in Windows Firewall. You might also need to enable TCP/IP in SQL Server configuration manager if you are using SQL Server Express.