BarTender Web Print Server: Quick Setup Guide for IT AdminsBarTender Web Print Server is a component of Seagull Scientific’s BarTender suite that enables users to print labels and documents through a web browser or integrated web application. This guide walks IT administrators through planning, installation, configuration, security hardening, and basic troubleshooting to get Web Print Server up and running reliably in an enterprise environment.
What this guide covers
- System requirements and planning considerations
- Step-by-step installation and deployment options
- Configuring BarTender Integration and Web Print Server components
- Printer and driver setup best practices
- Security and access control recommendations
- Monitoring, maintenance, and troubleshooting tips
1. Planning and system requirements
Before installing, verify compatibility and plan capacity.
- Supported OS: Windows Server (check the current BarTender compatibility matrix for specific versions).
- Processor & RAM: depends on expected load; for small teams a dual‑core CPU and 4–8 GB RAM may suffice, larger deployments should scale accordingly.
- Disk: ensure space for log files, label templates, and spool data; 100 GB recommended for moderate use.
- Network: reliable LAN connectivity between Web Print Server, BarTender server (if separate), and printers. Ensure necessary ports are open (HTTP/HTTPS and any BarTender-specific ports).
- Browser support: modern browsers with JavaScript enabled for users.
- Database: if using BarTender Enterprise features, ensure SQL Server availability for central logging and user data.
Capacity planning tips:
- Estimate peak concurrent print requests. Add CPU and RAM headroom (50–100% depending on burstiness).
- For high availability, consider load balancing Web Print Server instances behind a reverse proxy or load balancer.
2. Installation overview
There are two common deployment patterns:
- Combined installation: BarTender and Web Print Server on the same machine (simpler for small environments).
- Distributed installation: BarTender Engine/Server on one machine, Web Print Server on another (recommended for larger or security-segmented networks).
High-level steps:
- Install BarTender on the designated server.
- During or after installation, install the Web Print Server component.
- Configure IIS (if required) and any reverse proxy for HTTPS.
- Register printers and test print flows from a browser.
3. Installing BarTender and Web Print Server
Step-by-step (typical):
- Obtain the current BarTender installer and license keys.
- Run the BarTender installer on the server. Choose the appropriate components: BarTender Designer, BarTender System Database (if used), Print Server, and Web Print Server.
- If using a separate Web server machine, install only the Web Print Server component there.
- During installation, provide service account credentials if prompted. Best practice: use a dedicated domain service account with minimum required privileges to access network printers and SQL Server (if used).
- After installation, open BarTender Administration Console to verify services (BarTender System Service, BarTender Print Service, Web Print Server) are running.
IIS and reverse proxy:
- Web Print Server may host its own web service; for HTTPS and enterprise scenarios, it’s common to place it behind IIS or an enterprise reverse proxy (e.g., NGINX, F5). Configure TLS certificates at the proxy and forward traffic to Web Print Server over secure internal channels.
4. Configuring Web Print Server
Initial configuration tasks:
- Access the Web Print Server admin UI (URL provided during install; often http://
:port/ or via the BarTender Administration Console). - Set authentication mode: options typically include integrated Windows authentication, forms-based authentication, or integration with BarTender security. For enterprise SSO, integrate with ADFS/LDAP/SAML where supported.
- Register printers: ensure printers are installed on the server with correct drivers. Map printers to BarTender label templates so users can select correct devices in the web UI.
- Configure print queues and default settings for label stock, orientation, and number of copies.
- Set up template/library access control so users only see templates they are permitted to use.
Service account notes:
- The Web Print Server will impersonate a service account to access printers and resources. Grant this account printer permissions, and read access to template folders and the BarTender system database if used.
5. Printer drivers and best practices
Printer driver selection:
- Prefer manufacturer-recommended drivers or Windows native drivers for stability. If using BarTender’s driverless or direct printer integrations (e.g., Seagull drivers), validate compatibility.
- Avoid user-installed drivers on clients; centralize drivers on the server hosting Web Print Server.
Testing printers:
- Create a simple test template and print from the server to each target printer to validate feed, orientation, and print quality.
- Check for proper behavior under concurrent print jobs; simulate load to reveal bottlenecks.
Label stock and templates:
- Store templates and assets in a central location accessible to the service account. Use relative paths inside templates when possible to avoid broken links.
6. Security hardening
Key recommendations:
- Use HTTPS for all user-facing traffic. Terminate TLS at the reverse proxy or load balancer and enforce modern cipher suites.
- Limit admin access to the Web Print Server UI via IP allowlists, VPN, or network segmentation.
- Use least-privilege service accounts; avoid using domain admins.
- Integrate authentication with enterprise identity providers (LDAP/AD/SSO) where possible.
- Audit and logging: enable detailed logs and centralize them into an SIEM for monitoring. Retain logs per policy (e.g., 90 days).
- Patch management: apply Windows updates, BarTender updates, and driver updates regularly.
7. High availability and scaling
Options:
- Scale horizontally by deploying multiple Web Print Server instances behind a load balancer. Use sticky sessions if session state is not shared.
- Use SQL Server clustering or Always On for the BarTender System Database to avoid single points of failure.
- For printers, consider distributed print servers close to the printer network to reduce latency.
8. Monitoring and maintenance
What to monitor:
- Service uptime for Web Print Server and BarTender services.
- Print queue length and average job completion time.
- Error rates and failed job counts.
- Server resource usage: CPU, memory, disk I/O.
Maintenance tasks:
- Rotate and archive logs.
- Review and apply BarTender patches and cumulative Windows updates during maintenance windows.
- Periodically test backups of templates, configurations, and the BarTender System Database.
9. Common troubleshooting
Symptoms and quick checks:
- Browser cannot reach Web Print Server: check service status, firewall rules, and proxy configuration.
- Print jobs queue but never reach printer: verify service account permissions, driver compatibility, and network connectivity to printer.
- Labels print with wrong formatting: confirm template page size, printer defaults, and units of measure.
- Authentication failures: check identity provider configuration, time synchronization (Kerberos), and certificate validity.
Useful logs:
- Web Print Server logs (check installation path).
- BarTender System Service and Print Service logs.
- Windows Event Viewer for .NET or service exceptions.
10. Example: simple deployment checklist
- [ ] Confirm hardware, OS, and browser requirements.
- [ ] Install BarTender and Web Print Server (or deploy Web Print Server separately).
- [ ] Create and configure service account.
- [ ] Install and test printer drivers on server.
- [ ] Configure Web Print Server authentication and HTTPS.
- [ ] Register templates and map printers.
- [ ] Test end-to-end printing from multiple clients.
- [ ] Enable logging and configure backups.
- [ ] Document configuration and runbook for common failures.
Final notes
This guide gives IT administrators a practical path to deploy BarTender Web Print Server securely and reliably. For product-specific steps, versions, or advanced integrations (SAML, API usage, or custom form integrations), consult the official BarTender documentation and release notes.
Leave a Reply