Migrating and Upgrading PrintPath

Windows Server 2012 R2 is the last supported OS of PrintPath. Windows Server 2016 has known issues operating PrintPath.

Instructions

Step-by-step guide to migrating and upgrading PrintPath:

  1. Download the new PrintPath version to the new server.

  2. Note the current Windows PrintPath installation folder path as you will need to maintain the original folder path (i.e. if the path was “E:\PrintPath”, then there needs to be a hard drive assigned to drive letter “E” on the new machine with enough space).

  3. Find the existing database instance using the PrintPath Server Manager by going to "Start > Programs > Prism Software > PrintPath > PrintPath Config"

  4. Stop the PrintPath services and backup the PrintPath and FollowPrint databases listed in the PrintPath Server Manager within SQL.

  5. In the Windows Services list, locate the PrintPath services. To modify the login properties, right-click on the selected service, go to Properties, and the "Log On" tab. Make note of the Log On properties (including any specific user account and password information) as you will need to reconfigure this information after the installation:

    1. PrintPath Service - This is the main service of PrintPath and communicates to the SQL Database Server and Active Directory. This services should be set with log on credentials with Automatic Startup Type.

    2. PrintPath Printer Monitor Service - This service communicates with the Print Spooler and should be set to LOCAL SYSTEM with Automatic (Delayed Start) Startup Type.

    3. PrintPath FollowPrint Service - This service handles FollowPrint / GuestPrint/ Scan / BrowsePrint functions and should be set with log on credentials with Automatic (Delayed Start) Startup Type.

    4. FollowPrint KMBS Service - This service facilitates the communication between the PrintPath Server and the KMBS MFP's and should be set with log on credentials with Automatic (Delayed Start) Startup Type.

    5. Prism Authentication KMBS Service - This service handles the authentication communication between the MFP and the PrintPath Server / Active Directory and should be set with log on credentials with Automatic (Delayed Start) Startup Type.

  6. If you are moving SQL as well, install SQL to the new server and add a copy of the PrintPath and FollowPrint databases backup to the new SQL instance.

  7. Run the "PrintPath Server.exe" installer as an administrator on the new server. Follow the wizard prompts until the PrintPath Config window appears.

  8. Verify the SQL Server, instance, and databases are correctly set to the correct PrintPath & FollowPrint database, and then click INSTALL DATABASE to update the database.

  9. After the database update completes, click CLOSE and then complete the install.

  10. Enter the log on credentials into the services as they were on the previous server, noted in step 5.

Printer Monitor

If you are monitoring print server(s) in addition to the printers shared from the PrintPath Server, you will need to update the remote PrintPath Monitor Service on the print server(s):

  1. Run the "Remote Printer Monitor Service.exe" as an administrator.

  2. Point the PrintPath Printer Mornitor Service back to the new PrintPath server when the wizard prompts..

  3. Start the PrintPath Printer Monitor Service.

Notification Agent

For users who require notifications and responses to print jobs handled by the PrintPath Server (such as Account Codes, Rules, Redirects, etc.), update their PrintPath Notification Agents:

  1. Run the "PrintPath Notification Agent.exe" on user workstation.

  2. Enter the PrintPath Server URL and new PrintPath server name when the wizard prompts.

  3. Restart all the services, starting with the PrintPath Service on the PrintPath server to ensure connectivity and print tracking is restored.