Does anyone know where the Bartender Commander (or, in fact, the entire Bartender install) needs to reside in order to ensure label printing within Epicor from any Epicor client on the domain?
In my testing environment, I had installed the Bartender application on my own workstation - and this includes the Bartender Commander module. I have also constructed a label template that correctly connects to the Epicor DB. All of the report style and report data definition configurations have been prepared. My testing has been largely successful when issuing a “Print Labels” command from within Epicor:
However, if a print command is issued from a different workstation using the same module/report, the print job is sent back to the label printer that resides on my desk, instead of the label printer at the workstation where the print job was requested. It is helpful to note that the other workstation has its own label printer installed locally with its own set of drivers. The “Print Labels” command shells out to the Windows OS printer dialog which allows the user to select the printer he/she needs - and the user is picking the correct locally installed printer:
Sadly, the print job is sent to my label printer instead of the one at the other workstation.
This makes be believe that Bartender Commander needs to act like a “server application”, where it is installed, perhaps, on either the Epicor ERP server, or the domain’s print server in order to handle Bartender-based print requests. Also, if the only BT Commander install/presence resides on my workstation, would that not affect the general nature of Bartender printing for everyone else when my workstation is powered down? I’m guessing, yes.
What is the best practice Bartender/BT Commander install for multi-user printing requirements on the domain?