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.
HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\Client
DWORD fClientDisableUDP 1
A reboot of the machine was not needed, after closing the RDP session and reconnecting, TCP was being used. You can check which protocol is being used by clicking the symbol at the top:
References:
https://www.michaelmaw.com/how-to-fix-remote-desktop-freezing/
https://community.spiceworks.com/topic/2269433-remote-desktop-randomly-freezes-up
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):
Install-Module MsOnline
Connect-MsolService
Link the objectGUID with the immutableID of the Cloud user:
$upn = “aku.test@ajni.it”
The objectGUID needs to be in Base64 format.
$id = [system.convert]::ToBase64String((Get-ADUser -filter {userprincipalname -eq $upn}).objectGUid.ToByteArray())
Set-MsolUser -UserPrincipalName $upn -ImmutableId $id
Now move the on-prem user to an OU that is synced to the Cloud and run a manual ADSync:
Start-ADSyncSyncCycle -PolicyType Delta
The user is now synced:
References:
https://jasonhowe.net/2019/08/11/convert-office-365-user-from-cloud-to-ad-synced/
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
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
Select x64
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…
https://www.catalog.update.microsoft.com/Search.aspx?q=HP%20LaserJet%202800
References: