Which user account should I use for each service?
Services that should Run Under "Local System Account"
BarTender Print Scheduler Service - Manages BarTender print engines and intelligently assigns jobs to them while maximizing performance and maintaining print order and any serialization. It uses a single pool of print engines so that resources are used efficiently. The Print Scheduler service ensures that:
Jobs printing to a specific printer will always come out of that printer in the order the requests were received.
When documents contain embedded data that can change, such as serialized counters, they will be bound to a single print engine to ensure that they print in the correct order.
Integration Service - Used to manage and run BarTender Integrations.
Printer Maestro service - Used for network printer management and monitors printer status.
BarTender Web Print service - Used for Print Portal or custom Web application for Internet client side printing.
Seagull License Server/License service - Used for communication between BarTender clients and License Server to manage and monitoring printer licenses.
- The Print Scheduler and Integration Service utilize user impersonation. Essentially, the user account defined in the Integration file will be impersonated and run as the local system account for these services. When running with the local system account these services are able to run as if they were a different account.
Services that Need to be Set and Run under a Specific Account (if additional permissions required):
BarTender System Service (by default Local System Account)
This service is only used in Automation and Enterprise Automation editions and it is mostly responsible for connecting BarTender with the System Database for any message/print job logging and performing any reprinting using History Explorer/Reprint console.
For this service, you will need to set and choose an account that has enough rights to perform the tasks for that service with the following attributes:
- has local administrator rights
- has domain-level access
- does not change its password
- has access to the system database (if connecting to the system database using Windows Authentication)