The Remote Desktop Terminal services in Windows operating systems make use of printer redirection to conduct print jobs inside the terminal sessions. If you install or share a printer so that it works with a local computer, it gets rerouted to the remote desktop session host. Within the RDP session, this shows up as “redirected printer”. It is possible for users to utilize such a printer by directly sending it print jobs.
You can configure the redirection of the printer using Microsoft Easy Print, or alternately installing the drivers for the printer into the server. The latter is more preferred in big companies, because it is faster, and also produces more precise print jobs. However, it is seen to crash the printer spooler on the RD session host. If you get the local print spooler service not running error, you can do the following.
There may be no permanent solution to the problem, and Microsoft has not given out any information on supported printers for RDP redirection. One way to figure out which models work is by testing each one. If the host spooler has already crashed, use the below steps to fix it.
After you have successfully removed the printer driver from the system, the spooler service should begin to work normally. The application event log can be checked every once in a while for spooler errors; usually, spooler crash is represented by event ID 1000. The problem can also be avoided by only getting drivers, which match the client computer.