The following list of system checks helps you prevent problems that might hinder you during installation and testing.  For more questions on how to implement the LPS in a specific environment, call a Loftware System Analyst to help you go over key points in your implementation strategy and/or help you architect the best solution for your needs.

Network Assessment

Assess the network speed and network protocols you plan to use to support the LPS solution.  Ensure you have proper network interface cards to support required protocols and throughput.  See the "Performance Considerations" section for more information on this matter.  Most standard LAN/WAN configurations work fine.

Hardware Selection

Desktops/Servers/Workstations - It is important to make sure you have a PC or server powerful enough to handle your printing needs.  Again, refer to the “Performance Considerations” section.

Print Servers - If you are using hub based Print Servers such as Extended Systems, HP, Intel, or Castelle to connect your printers to the network, ensure that they support the network protocols you are running and that you set their TCP/IP address.  The preferred method is to use printers that already have built in Network Interface Cards (NIC’s).

Printers - Select a printer that has the power and ability to support your overall needs as well as the network connections you require.  We recommend printers with parallel ports or internal NIC cards.

Printer Cabling - In addition to the selection of a printer, it is extremely important to have the right cables and adapters that allow you to connect and operate the printers on your network.  Identify the specific cabling requirements and read your printer manufacturer’s installation guide for specifics on printer cabling for your printers.

Dedicated TCP/IP Addresses for Peripherals and PC Hardware

It is important that Servers/Desktops and Workstations running the LPS have a dedicated TCP/IP address.  It is recommended that you not use DHCP as a means to configure a dynamic address.  This applies for all Print Servers running in the network that support print spooling operations.  All TCP/IP devices must have addresses assigned by a network administrator.  Communications must be verified to all Ethernet adapters and print servers.

Operating Systems (2000/XP Professional/2003)

2000/XP Professional/2003 - Ensure that all services start properly and there are no hardware conflicts or service control manager errors.  Also, make sure the network has properly started and your machine has an established machine account in the domain.

Print Server Setup (where applicable)

2000/XP Professional/2003 - Using the Administrator Account, install the TCP/IP and Windows Drivers for the print servers on the Desktop/Workstation/Domain to allow you to capture printer ports during printer setup.  See the manufacturer’s installation guide and Chapter 2 of the LLM User’s Guide for more complete instructions.  This only applies to devices which do not have an internal Network Interface Card (NIC).

Mapped Drive Letters vs. UNC

LPS runs in memory as a service; therefore, most mapped drive letters, due to new stringent security standards, will not be accessible. When configuring additional scan directories, instead of using M:\drop, for example, use \\ws1\drop .

Connector/Sockets/FTP vs. Polling

Pushing report files to LPS is recommended over polling. Uses of Samba shares, though useful to quickly allow the LPS access to the report files, are often riddled with security and are unable to work with programs that run in memory as a service (without additional configuration). Because of this, Loftware recommends using one of our Connector solutions, opening a socket or FTP'ing the report file to the LPS computer.

Use of Privileged Account

Installation, Configuration, and Service Packs of the Loftware Print Server should be performed using the same account that will Stop / Start the LPS as a service. The account must be part of the Local Administrators group to be able to have Print Manager and Read/Write access to the registry, Windows and system directories, as well as the ability to Stop / Start services. Because files and printers are maintained across a domain, the account is often a member of the Domain Administrator group. If a reboot is required for install or service pack, make sure to log back onto the server with the same account to allow post boot finalization of the install.