PrinterLogic Components

PrinterLogic is comprised or four main components that eliminate print servers while maintaining the functionality they used to provide. Certain components manage the print environment and release print jobs, while other components enable end-users to install drivers on their workstation, or the administrator to manually update drivers already installed on workstations. The following sections provide further details about each of these components.

Admin Console

The Admin Console is the management platform that gives the administrator centralized management of every printer in your organization - all from one location, regardless of whether you have one physical location or a hundred sites across as many countries. The following image is a sample of the Admin Console interface with callouts identifying the various interface features.

PrinterLogic Client

The PrinterLogic Client is software installed on the end-users' workstations. To say the Client performs several important functions would be an understatement. The Client creates a "connection" between the workstation and the PrinterLogic server. This "connection" enables the Client to:

  • Install printers on the workstation
  • Install or update drivers on the workstation
  • Collect metadata for successfully submitted print jobs
  • Hold print jobs in a Print Queue
  • Release held print jobs to a destination printer

The reason the Client is such an essential piece of the overall PrinterLogic picture is that when the administrator makes changes (through the Admin Console), those changes need to be pushed out to the workstations. In other words, there needs to be a sync between the drivers and profiles in the Admin Console and the drivers and profiles configured and installed on the end-users' workstations.

For example, let's say HP releases a new driver for several of your printers, and your PrinterLogic administrator would like to automatically update the existing HP driver that is already installed on end-users' workstations. The "connection" between PrinterLogic and the installed client(s) is what enables the driver update to occur. In short, after the administrator updates the driver, the client(s) will "see" that there is an updated driver and the HP driver already installed on the workstations will automatically be replaced with the new driver.

NOTE: The client runs in the background on any workstation that has it installed and should not require any intervention on the part of the end-user.

The client can be installed manually through the Admin Console with a Windows startup script, with a third-party application (like Landesk), or with a GPO (Group Policy Software Installation Package) on workstations with a supported Windows, Mac, or Linux operating system. For more information, see Install Client on Windows.

NOTE: The recommended best practice is to use the tool your organization currently uses to make deployments for software, other agents, etc.

When the Client is successfully installed on a workstation, the Start menu may or may not be populated with a new PrinterLogic section as shown below.

The appearance of these Start menu items depend on whether you, the administrator, makes them available to the end-user in the Admin Console. Click Tools > Settings > Client and navigate to the Shortcut Options section as shown below.

Similarly, the Windows System Tray may or may not be populated with the PrinterLogic icon.

The appearance of the icon in the Windows System tray are also dependent on whether they are made available through the Admin Console Shortcut Options, also shown below.

If the icon does appear in the Windows System Tray, the end-user can click it to open the Self-service Portal, which enables the end-user to install printer drivers without requiring IT assistance. Right-click the icon in the System Tray and then select from a number of different options to add printers, delete printers, select a default printer, open the Release Portal, and others.

The client is set, by default, to check in with the PrinterLogic server every 240 minutes, but you can change this timeframe in the Admin Console by clicking Tools > Settings > Client and then selecting Client Check-in.

NOTE: Even though there's a check box to the left of the Client Check-in feature, you cannot disable the client check-in process.

The Client will, at a minimum, check in during startup and login. The Client on the end-user's workstation also provides the Refresh Configurations option, which enables the end-user to manually check-in with the PrinterLogic server. This feature can be especially useful when you have an update ready, and you want to install the update immediately. You can deploy the update to your end-users' workstations, but you would have to wait for the client installed on the workstations to check-in. Otherwise, the end-user could refresh the client to see the update immediately.

Consider an example in which a company does not allow self-service printer installation. Rather, they allow only printer deployment assignments. In this case, when the administrator has the deployment assignment ready for deployment, nothing happens until the client checks in (or the end-user forces the refresh from their workstation).

Self-service Portal

If you have ever worked in an unfamiliar environment, and you wanted to print a document, you know it can be a painful process to figure out where the drivers are located and whether you have permissions to install them. What if you could simply open a web page to install drivers for the printer just down the hall from the conference room in which you are working? Well, that's what the Self-service Portal does - it enables you to install drivers without asking anyone for help. The following image is a sample of the Self-service Portal.

Release Portal

The Release Portal does exactly what its name implies - it enables an end-user to release print jobs to a printer when that person is ready to release them. Any device with browser access (either through Wi-Fi or mobile connectivity) can be used to release print jobs through the Release Portal. The following image is a sample of the Release Portal with a couple of print jobs waiting for the end-user to release them.