Employees working via RDP on a Windows 2016 server have printers falling off, how to fix it?

Question

Windows

There was a problem. Employees who work via RDP on Windows server 2016 have their local printer on a remote desktop falling off. Moreover, there are no problems on the local PC, it is logical that the problem is in the server. After long observations and screening out causes and errors, I found out that printers fall off RDP when one of two errors occurs (photo below):
1) Error

spoiler

Information

spoiler

spoiler

2) Error

spoiler

Information

spoiler

spoiler

Following these errors, services fall off in a row:
The Windows Driver Foundation Service - User Mode Driver Platform Runtime terminated unexpectedly. This happened 1 time(s). The next corrective action will be taken after 120000 ms: Restart the service.
The Diagnostic System Host service terminated unexpectedly. This happened (once): 2.
The Remote Desktop Services User Mode Port Forwarder service terminated unexpectedly. This happened 1 time(s). The next corrective action will be taken after 60000 ms: Restart the service.
The Storage service terminated unexpectedly. This happened 1 time(s). The next corrective action will be taken after 300000 ms: Restart the service.
The Smart Card Reader Enumeration Service terminated unexpectedly. This happened 1 time(s). The next corrective action will be taken after 300000 ms: Restart the service.
The Program Compatibility Assistant Service ended unexpectedly. This happened 2 times. The next corrective action will be taken after 60000 ms: Restart the service.
The Network Connections service terminated unexpectedly. This happened 1 time(s). The next corrective action will be taken after 100ms: Restart the service.
The Network Connection Broker service terminated unexpectedly. This happened 2 times. The next corrective action will be taken after 5000 ms: Restart the service.
The Data Sharing Service service terminated unexpectedly. This happened 2 times. The next corrective action will be taken after 10000 ms: Restart the service.

spoiler

Perhaps all these errors are related to this one. It occurs at 2 o'clock in the morning:

spoiler

Information

spoiler

spoiler

The problem is very acute, since most of the work is tied to printing.
Temporarily, this can be treated either by completely resetting the user account (the printer is re-pulled via RDP) or by deleting all ports associated with the printer in the register.
Registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\##?#ROOT#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}
After a simple shutdown account with "Word" open. Reconnect and the printers pulled up. The registry rewrites the ports for this RDP connection.

Answer 1

cure svchost.exe.
after its failure, the services, one way or another working with the network, also fall.

Answer 2

The problem is not completely isolated.
1. Are there users who do not have such a problem?
2. Are there any printers with which there are no problems?
3. The problem occurs only with certain users and it does not matter which printer they use or all users of the same printer have the problem.
4. Do all users of the problem printer have the same printer driver version?
5. Do all users have the same bit depth of the system?
6. Etc.
It is necessary to cut off all possible combinations. At one time I had 2 old terminal servers, there were quite a lot of users, about 50-60 simultaneous connections, they worked in K +, through the company's internal helpdesk, requests "the printer is not forwarded" / "it is forwarded, but does not print" daily poured into me .
A particularly stubborn comrade before me "solved" the problem by connecting the printer directly to the terminal server, which naturally added problems with printing to a printer in a neighboring city.
We managed to isolate the problem, it turned out that the problem clients for some reason were sitting on winXP, no one expected this, because. Officially, all jobs should have been transferred to win7 for about a year.

Answer 3

Do not use a hellish zoo of various printer drivers on terminal servers. There such unpredictable bugs can be caught, which then it will be easier to rearrange the system on the server than to joke around.
Use something like tricerat screwdrivers.

Answer 4

Two magic phrases usually help - enable printer driver isolation and enable easy print (by default, if all printers work through it, and as an option, if not all).