Tarantella Administration Guide > Printing > Printing from a Microsoft Windows (SCO Merge) application server

Printing from a Microsoft Windows (SCO Merge) application server

To print from a Microsoft Windows application server using the SCO Merge Windows protocol, you have to configure a Tarantella printer on the UNIX server running SCO Merge. You do this from the UNIX command line and from Windows. To configure a printer:

1. Configure a Tarantella printer on the UNIX server running SCO Merge. This printer must direct print jobs to the primary Tarantella server in the array.
2. As root on the UNIX server, insert the Tarantella printer into the doslp class by typing:

   lpadmin -p tta_printer -c doslp

3. Run the Windows Add Printer Wizard on the application server to configure the new printer.
4. When prompted, choose the printer model and manufacturer that most closely matches the client device's default printer. If there's no close match, choose a PostScript printer.
5. When prompted, choose doslp from the list of available ports.

Limitations when printing from a from a Windows application server using the SCO Merge protocol

You should note the following limitations of printing from a Windows application server using the SCO Merge protocol:

• no multiple printer support - you can only print to the client device's default printer. It is not possible for users to select a printer. If a user needs to print to a different printer, they have to log out of Tarantella, change their default printer and then log in again.
• print jobs may be deleted - when a print job is transferred from the application server to a Tarantella server, the user's Tarantella name is needed to identify which client device to sent the print job to. With Windows and the SCO Merge protocol there is no direct way to associate print jobs with Tarantella users. If Tarantella cannot identify which user has printed a particular job, the print job is deleted. This might happen, for example, if two users log in to the application server with the same name.
• distributed printing is not available - all print jobs are directed through the primary server in a Tarantella array.

Next steps in configuring Tarantella printing

• Configure another application server:
  • UNIX application server
  • Windows 2000/2003 application server
  • Windows NT 4 application server
  • Windows NT 3.51 application server
• Configure the Tarantella server to accept remote print requests.
• Configure printing if you use the Common UNIX Printing System™ (CUPS).
• Configure printing for UNIX clients.
• Configure Tarantella print job conversion.
• Test that printing works. If you have trouble printing, follow the steps in the printing troubleshooter.