2019 RD Farm with FSLOGIX Profiles Printer Issues

Question

2 Session hosts
Third server, the file & print server is the broker/gateway.

We reboot these servers each night to clear up fslogix profiles etc due to them not clearing out properly all the time. No issues with that.

The problem we have, however, is that after a full days work when the servers are rebooted, when users login to the server, no printers will enumerate and you cannot connect to any new ones.

Opening devices & printers in control panel just locks up explorer.exe and you cannot do anything to do with printers.
Restarting the spooler service will make control panel respond again but as soon as you right click any printers or anything, it will stall again.

The fix that I have found is to run a scheduled task on system boot that does the following

net stop spooler
Remove-Item -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\*" –Recurse
net start spooler

The problem then goes away and everything works fine.

I guess I'm okay with this being a permanent solution but I'd rather it not be. Any ideas?

Other stuff I've tried:

• The usual sfc /scannow and dism cleanups
• Updated every printer driver to the latest version on the print server and reinstalled the new drivers on each RD Session Host

Answer 1

HI Nick-4443,

1.Do you use fslogix in Citrix session host environment ?

Please back up the problematic server and registry key first.
https://support.microsoft.com/en-us/topic/how-to-back-up-and-restore-the-registry-in-windows-855140ad-e318-2a13-2829-d428a2ab0692

Configure the registry key and restart the terminal server 2019, finally we can check the result.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\RemovePrintersAtLogoff
Value = 0

2.Some Window Server 2019 Terminal Servers need to install the latest update to fix this issue.

============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hello
Would anyone else have any insight into this?

Answer 3

HI Nick-4443,

1.“Third server, the file & print server is the broker/gateway.”
What do you mean about this sentence?

2.When the no printers will enumerate, are there any event logs in below location on session host W2019?
event viewer\windows logs\
application
system
event viewer\windows logs\applications and services logs\microsoft\windows\printservice
event viewer\windows logs\applications and services logs\microsoft\windows\user profile service
event viewer\windows logs\applications and services logs\microsoft\windows\termininalservice-printers
event viewer\windows logs\applications and services logs\microsoft\windows\winlogon

3.When issue happen, if we logon local administrator account to problematical RD session host server, will the printers also not be enumerated?

4.Which printer policy did you deploy to problematical RD session host server?

Computer policy
computer Configuration\Policies\windows settings\deployed printers​
computer Configuration\preferences\control panel settings\printers​
​
User policy
user Configuration\Policies\windows settings\deployed printers​
user Configuration\preferences\control panel settings\printers

5.When issue happen, if we use remote access the RD session host server by using local administrator of problematical RD session host, will the redirected printers also can not be emulated on RD session host server ?

============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

HI Nick-4443,

Is there any progress on your question?

Answer 5

HI Nick-4443,

Is there anything to help you?