We have a process setup that allows one of our vendors to print from a windows application back to a printer on our network. Our problem is that our vendors internet connection becomes saturated and connectivity starts to become intermittent. The telnet and Citrix apps seem to be designed to handle this, but the windows print queue does not.
The windows print queue acts like as soon as can't reach the remote Q the first time it gives up. All the remaining print jobs just seem to sit in the print Q on the users machine.
Does that windows print Q have parameters that are adjustable ?
Can we set the Q to keep retrying every minute until successful ?