Problem with printing services on a 2008r2 terminal server running high for Sage 100

I have all my users connecting to Sage from a 2008R2 terminal server with the Sage 100 app installed. The server shows spoolsv.exe running and printerisolationhost.exe running cpu nearly all times throughout the day. The only users which connect to this terminal server are those running Sage and 99% use the remote application function of terminal services rather than logging on to mstsc.exe.