Is the introduction of easy print worth it?

Question

Printers

Good day, I'll start a little from afar.
There are 2 domains, domain1 where the office of employees and domain2 in the DC where the terminal servers, the actual print server (windows server 2012r2) is on the side of the DC, printers from the domain1 office are connected to it, and the users themselves work with their printers in the terminal in domain2, print server distributes printers to everyone using a self-specified GPO.
Printers often fall off in rdp, locally I have not observed such problems and the introduction of easy print solved someone's problems?
Also, if the printer is connected to two print servers, does this create some kind of conflict or other problem?
Thank you for your attention.

Answer 1

Administered two terminal servers, both on WindowsServer 2008R2. Printers logged into the session were connected individually, periodically buggy, and the problem with a driver error is usually treated by restarting the print service. Restarting the print service would reset connected printers and all user sessions had to be restarted. Perhaps we did something wrong.
Then we moved to WindowsServer2012R2, where we tasted the joys of EasyPrint and the absence of most of the usual failures. The only problem is the ancient printers from 2007-2009, their support ended long before Windows 8 (and Server 2012), you will have to suffer with them or abandon them.