Sage 100 Printing Issues in RDS Server Farm. Problem and Resolution
From the IT staff for one our out clients.
Problem
Sage 100 2017 Advanced. Sage 100 runs as an application on a Server 2012 R2 x64 virtual machine and the application is accessed from a pair of Server 2016 x64 Remote Desktop Services servers (also virtual) in a load balanced farm. Printers are deployed from a Windows 2012 R2 x64 print server via ""Print Management"" and then installed on the RDS servers via Group Policy, permissions granted to the printers via Security Groups.
The issue is that sometimes when users log into the RDS farm and then launch Sage 100, they will either only have Deferred and Export for printers or they'll have a couple of their Windows printers show up but not others, despite all of those printers accessible from other applications (BarTender, Word, Notepad, etc.) and a valid default printer being set. Closing out of Sage 100 and relaunching or logging in sometimes resolves the issue and sometimes does not. Restarting the Print Spooler sometimes resolved the issue and sometimes does not. Also they can preview the print job in Crystal Reports and then print from there without any issues.
Sage was contacted and stated that this is an issue in
Resolution
Solution is to install the Print Server role on both of the RDS servers and install the printers locally on these servers. Works all of the time. Downside is now when a new printer is installed, it must be installed on the regular print servers as well as both of the RDS hosts.