Installing and Configuring on Windows Server Clustered Print Server.

Print Manager Plus and later support tracking of a clustered print spooler running within a Microsoft Fail Over cluster.

In this installation example we will be installing on an existing Clustered Print Server named 'ClusterVMPS' running on two physical servers named 'Node1' and 'Node2'.  The Primary installation and database are running on a third server named 'ARAEL'.

Note: A restart of each node will be required for the initial installation.  This can be done one at a time however to ensure your clustered services remain available.


The clustered print server, and primary installation of Print Manager Plus must already be setup and installed prior to installing and configuring on the Nodes of your cluster environment. 

  • Fully Configured and Operational Clustered Print Spooler:
    Print Manager Plus does not configure your Fail Over Cluster for you in any way. It should be properly configured and tested before continuing.
    Microsoft Technet: Failover Cluster Step-By-Step Guide

  • A Completed Primary Installation of Print Manager Plus:
    The Print Manager Plus Primary Installation must be done on a system other than one the nodes to be used within the Fail Over Cluster environment.

  • Database:
    The database cannot be hosted on a local SQL Express instance and must be one of the two options.

    • Remote SQL Instance:
      A remote Clustered or Standalone Microsoft SQL Instance running SQL Server 2008 through 2019.
    • Local Clustered SQL Instance:
      A local instance running on the same physical nodes is supported when it is setup in a Failover Cluster.
  • Licensing:
    Unlike previous versions of Print Manager Plus, installing and configuring on a Fail Over cluster is available for all editions, including Basic, Standard and Premium licenses.


 Installing on Each Physical Node:

Print Manager Plus need to be installed on each physical node as an Additional Server. Its recommended to limit features installed to 'Tracking & Printing Services Only'.

  1. Launch the Install:
    Run the installation media and confirm the installation location and accept the agreement.

  2. Choose Additional Print Server with Advannced Options

  3. Enable only Tracking and Printing Services
    While the Administration Interface and Print Client will function on the physical node, its recommended to manage all aspects from the Primary Server, or workstation instance of the Administrator.

  4. Select your SQL Server:
    This can typically be done by specifying the name of your Primary Server, or manually specifying the instance.

  5. Service Logon:
    This service logon will not be the one used to track your Clustered Print Spooler.  This will be used to track any locally installed queues you may have
    It requires local administrative rights on the Node, and full control of the Print Manager Plus database.

  6. Run the install and Reboot the Node:

  7.  Repeat Installation on All Physical Nodes that are part of the Cluster

Creating a Clustered Service on Each Physical Node:

Print Manager Plus uses a command line wizard which needs to be run on each physical node to create a specialized service that can be added to your Clustered Print Spooler.

  1. Launch the 'Cluster Service Creation' from the Start Menu

  2. Specify the Virtual Network name of your Clustered Print Server:
    In our example this is ClusterVMPS

  3. Service Account / Password:
    Next you will prompted for the service account and password for the cluster service to run as. This account has the following requirements:
    Domain Account in DOMAIN\User format
    Local Admin Rights to the Physical Node
    Admin Rights to the Clustered Print Spooler
    Full Control of the Print Manager Plus Database

  4. Service Installed:
    The service will now be installed and listed within services.
    Note: Do not attempt to start, control or edit the service from here. It is designed to be controlled from the Failover Cluster Manager only.

  5. Repeat Service Creation on All Physical Nodes that are part of the Cluster


Create the Generic Service Resource

Now that each node has a clustered tracking service created, it can be added to the cluster as a 'Generic Service'.  This only needs to be one time within the Fail Over Cluster Administrator and can be done from any Node.

  1. Add a new Generic Service Resource:
    Within the Failover Cluster Manager, select your clustered print spooler and right click and choose the 'Add a Resource' > '4-Generic Service' Option.

  2. Select the Print Tracking Service for your Cluster:
    There will be a service listed specifically referring to your cluster for Print Tracking and Control.  Ensure the service matching your clusters name is selected.

  3. Configure Service Properties:
    You will need to configure the new clustered service to depend on the Print Spooler.  

  4. Set Dependency on Print Spooler
    Within properties, go to the 'Dependencies' tab and add the 'Print Spooler' as a dependency.
    Click [Apply] before continuing.

  5. Set Network Name:
    On the General tab, check the box titled 'Use Network Name for computer name'

  6. Bring the Resource Online:
    Finally you are ready to start the Generic Resource.

 Verifying Successful Tracking

There are a few steps that should be followed to ensure the service is successfully running and tracking.

  1. Ensure Resource Shows Online
    Within the Failover Cluter Manager, the resource should list as Online 

  2. The Cluster Service will show within Services:
    Next you should print a test page, or other job to one of your clustered printers, and verify that both the service, and the job appear within your clustered service on the Services tab.

 Tracking Multiple Clustered Spoolers (Active\Active Configuration)

Starting with Print Manager Plus 9.0, this scenario is fully supported.  Simple repeat sections listed below for each Clustered Print Server you have running.

Creating a Clustered Service on Each Physical Node
Create the Generic Service Resource
Verifying Successful Tracking


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk