Printers attached locally on workstations
Network printers
Preconditions
- ThinPrint Engine is installed on the central print server
- The following are installed on the local print server:
- Printers
- ThinPrint Client Windows (TCP/IP type)
- The following are installed on the Windows workstation:
- ThinPrint Output Gateway + AutoConnect + possibly Printer-Self-Service (via custom installation of the ThinPrint Engine)
print data route: workstation→ central print server→ local print server→ printer
Procedure
The installation procedure is the same as that described for network printers in Praxis: Running applications on remote desktops. In this case, however, the group policies don’t relate to the terminal servers or virtual desktops, but to the workstations. And finally, AutoConnect will be started with the same script when logging on to the workstation.
- Log on locally to a workstation, and perform test prints on the automatically created printers.
Printers attached locally on workstations
Preconditions
- ThinPrint Engine is installed on the central print server
- The following are installed on the Windows workstation:
- Printers
- ThinPrint Client (TCP/IP type)
- ThinPrint Output Gateway + AutoConnect + possibly Printer-Self-Service (via custom installation of the ThinPrint Engine)
print data route: workstation→ central print server→ workstation→ printer
Procedure
The installation procedure is the same as that described for Printers connected locally to workstations or thin clients in the section Praxis: Running applications on remote desktops.
However, in this case, AutoConnect requires a script-controlled on the startup workstation, as follows:
- Create logon scripts for all users – with the following content:
c:
cd C:\Program Files\Common Files\ThinPrint\
tpautoconnect -d
tpautoconnect -a %computername%
- Perform an update of the group policy for the workstation.
- Log on locally on the workstation, and perform test prints on the automatically created printer.