GoPrint Server Migration The following steps walks you through migrating a current GoPrint system to a new Windows server focusing on migrating the current database as well as keeping the same server name. This helps to make the migration as seamless as possible and gets the system back up and running with minimal downtime. Supported Operating Systems: Windows 2016, Windows 2012 R2, Windows 10 System software and hardware requirements guide http://www.goprintsupport.com/goprint_system_requirements.pdf Steps overview: 1. 4.1# 4.2.2: upgrade: Upgrade your current system to 4.1.19 or higher to match current supported Windows Installers. 2. 4.2.2# to 4.2.2.8120 upgrade: If currently running some version of 4.2.2 you must upgrade to the latest version of 4.2.2 which is 4.2.2.8120 using the System Web Update Tool. 3. Recommended: If using the default PostgreSQL database platform currently installed on your GoPrint server, Backup your existing DB and then Restore it on your new server. Doing so, saves all GoPrint Configuration items allowing for minimal downtime. If using a remote MS SQL Server database, a Backup and Restore isn t required, a simple connection to the database and to the server is re-established during the db connection attempt from the GoPrint Node center: https://localhost:7767 Tip: you must know your Postgres user password or the MS SQL Server db user account and password prior to attempting the migration. See the Node at https://localhost:7767 4. Install the print queues on the new server Prior to migrating and installing GP on the new box. Make sure to Share the print queues and use the manufacturer drivers. Do NOT use the built-in Windows Class drivers now available under the latest versions of Windows. Note: Windows no longer publishes various manufacturer drivers replacing them with Windows Class type 4 drivers. These drivers are NOT designed to be Shared and will crash your spooling system. 5. Once GP is running on the new server, rename the new server to match the sever name it s replacing and change the cfg files. Saves having to remap print queues on client machines and save s all printer configuration. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 1
6. Create inbound and outbound ports on the Windows server Firewall for ports 7767-7773 7. SSL Certificate: if a SSL certificate is installed for the web client pop-up, then backup the gtx.keystore file and the JRE cacerts keystore file. These steps eliminate the need to reimport the SSL certificate. The cacerts keystore is located: \GS4\jre\lib\security Step 1 Make note of the database server settings Navigate to the Server Node to make note of your current database settings: especially using a MS SQL Server platform. You will need to know the password for the Postgres user account and the MS SQL Server database username and its password as well as the servername and instance. Node: https://localhost:7767 PostgreSQL: Hint: typically, passwords are: xxx123 or Go123srv (based on installation guide). If something different, then a staff member created a unique password. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 2
MS SQL SERVER It s very important to make note of: 1. the MS SQ Server name and the appended instance, if one is attached. 2. Database name 3. MS SQL User ID and password. If you do not know this information you must obtain it prior to re-connecting to the database on the new server. Write this information down! MS SQL Server (cont) Due to new Microsoft licensing requirements, they no longer allow 3 rd party applications to package the MS JDBC jar file so you must manually download the jar file and place it in the GS4\Lib directory prior to making the db connection or you will see the following error. JDBC driver can be downloaded here: http://www.gprintsupport.com/jdbc41.zip Or https://www.microsoft.com/en-us/download/details.aspx?id=54670 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 3
Step 2 Upgrade System It s important when migrating to a new server, that the server version is compatible with the required upgrade path. The correct path is at follows: 4.1.19 required to upgrade to 4.2.2.8120 4.2.2.# some version to 4.2.8210 1. Check your server version There are numerous ways to check your version. The simplest is from the Control Center Login page. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 4
Running 4.1.# If running some version of 4.1.#, you must upgrade to 4.1.19. To do so use the Web Update Tool. 1. System - Web Update 2. Download the 4.1.19 update and when completed restart the GS4 Services from MS Services or restart the Node: https://localhost:7767 Upgrading from 4.1.19 to 4.2.2.8120 Once updated to 4.1.19 navigate back to the Web Update Tool to obtain the instructions (PDF) for upgrading to 4.2.2.8120 1. Prior to updating you must manually update your servers (GTX, and Agents) and print release stations JRE to JRE 8. This is the JRE that comes embedded with GoPrint. Follow the instructions in the update guide to download the required JRE 8 zip file and to apply. 2. Manually download the 4.2.2.812 update zip file and place the zip file into your GTX servers GS4\Updates folder. 3. Restart the GS4 Services Note: remote Agents and Release Stations are designed to automatically pull down the updated GoPrint version. Additionally, you can download the upgrade instructions here: http://www.goprintsupport.com/gs4-update-4.1-4.2.pdf Upgrading from some version of 4.2.2 to 4.2.2.8210 If currently running some version of 4.2.2 and want to upgrade to 4.3.0# you must first upgrade to the last version of 4.2.2 which is 4.2.2.8120. Depending on your current 4.2.2 you may use the System Web Update Tool. If the option to download the 4.2.2.8210 update, then you re running a older version of 4.2.2 that doesn t support this update process and must then manually download the 4.2.2.8120 update and apply it. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 5
To do so: 1. Download the update http://software.goprint.com/webcheck/updates/gs4-updf-4.2.2.zip 2. Drop in the servers GS4\Updates folder (Do not extract the zip file) 3. Restart the GS4 Services Important: for migrating purposes, upgrading to 4.3.0 isn t required and should only be completed using the Web Update Tool after the server migration is completed. Do not upgrade to 4.3.0 prior to migrating!!! Step 3 - Backup the GoPrint Database (PostgreSQL Server 8.1 10.0) Important: It s assumed you followed the prior steps to upgrade to 4.2.2.8120 Navigate to: Step 1 - Start menu Programs PostgreSQL 8.2 pgadmin III Note: or PostgreSQL 9 + 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 6
Pgadmin III tool should open: Note: if prompt for a password enter: xxx123 or Go123srv or the password you created when originally installed PostgreSQL. Step 2 Double-click the PostgreSQL Database Server to expand and to view the goprint database. Step 3 Click the goprint database to enable it 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 7
Step 4 Right click on goprint and scroll down and select BACKUP The Backup dialog box appears Leave ALL default items checked! Step 5 Press the Button to select what you want to name the backup and its location on the local server 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 8
Step 6 Give the backup a name and save it Give it a name corresponding to the month and date the backup was performed. Navigate to the current Backups Folder located on the Desktop of the GoPrint Server 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 9
Step 7 - Select COMPRESS (Do not select Plain) Leave other defaults checked Pre-postgresql 9.0 screenshot PostgreSQL 9.0+ screenshot 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 10
Step 8 Press OK or Backup to start the backup process The backup process begins: Note: will take a number of minutes to complete depending on size of database Click Done Step 9 Copy the backup to the new server Install PostgreSQL and GoPrint on the new server At this point, it s assumed you followed the Windows Server Installation guide to install GoPrint and PostgreSQL onto the new server. Also, assumed the Windows print queues have also been installed. http://www.goprintsupport.com/windows_server_install_guide.pdf Windows Installers: http://software.goprint.com 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 11
Important: Install PostgreSQL 9.6.10 (current supported version) https://www.enterprisedb.com/downloads/postgres-postgresql-downloads Create a new Database to Restore the backup Pgadmin III for PostgreSQL 9+ If using Pgadmin 4 and PostgreSQL 10 see instructions at end of document. Hint: try to use the same database name, but not required. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 12
Restoring a Backup Step 1 - Scroll down to the Restore option Pgadmin III for PostgreSQl 9.0 + screenshot Step 2 - Enter a path to the backup file 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 13
Press ok when completed Connect to the Restored Database Step 1 Open the Node interface: open a browser to: https://localhost:7767 Step 2 - Click on Configure database Make the necessary changes: JDBC Driver: JDBC PostgreSQL Server: localhost (localhost is required!) Database Name: should be the same! User ID: postgres Password: should be Go123srv or whatever you created when you installed PostgreSQL based on the Windows Server Installation Guide. Step 3 Press Apply Step 4 Press Test Connection A Connection Successful message appears! DO NOT PRESS CREATE DATABASE! 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 14
MS SQL Server Prior: place the MS JBDC driver into the GS4\lib directory Enter: 1. JDBC Driver: Microsoft SQL Server 2. the MS SQ Server name and the appended instance, if one is attached. 3. Database name 4. MS SQL User ID and password. 5. Press Apply 6. Press Test Connection A Connection Successful message appears! DO NOT PRESS CREATE DATABASE! 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 15
Failed to locate the JDBC Driver error: Due to new Microsoft licensing requirements, they no longer allow 3 rd party applications to package the MS JDBC jar file so you must manually download the jar file and place it in the GS4\Lib directory prior to making the db connection or you will see the following error. JDBC driver can be downloaded here: http://www.gprintsupport.com/jdbc41.zip Step 5 - Click on Services from the Node navigation menu 1. Start the GTX service Service GTX failed to start: null appears: This happens when the database connection previously existed, and a change was made. To resolve, restart the GS4 Services from MS Services. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 16
Once the GTX service appears as running, press the GoPrint Control Center option to bring up the admin login page. GoPrint Configuration and renaming the new GoPrint Server Once the migration was successful you must rename the new to server to match the hostname of the server it s replacing. Two Agent servers will appear. The old production server appears with a red dot stating it s offline and the information is being pulled from the database. Expanding the arrow next to the red dot expands all of the printers. Once you physically rename the server and make two configuration changes the server status will change to the desired server. In this example, the localhost server displays as green and the ricksredhat.localdomain server in red. At this point, you can delete the printers under ricksredhat.domain server and finally the server itself. Note: you cannot delete a server with printers attached to it. Steps to Rename the server 1. Physically rename the server 2. Edit the goprint.cfg file to reflect the new name 3. Delete the gtx.keystore and restart the services 4. Optional: SSL Certificate. if previously using a ssl certificate for the web client popup, you can copy the backup of the gtx.keystore file and replace it here. This file is where your ssl certificate it stored. Doing so, eliminates the need to reimport the ssl certificate. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 17
Navigate to the GS4 installation directory and open the goprint.cfg file in Notepad. Look for the line: gtx.hostname: and change the name. Save changes 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 18
Delete the GTX.KEYSTORE FILE SSL Certificate Import IMPORTANT: If using an SSL Certificate for web client secure communication, drop the backup of your gtx.keystore file here. This step eliminates the need to reimport the certificate. Tip: you may also need to delete the gtx.keystore file on remote Agents if they re having issues reconnecting: displaying a message stating cannot connect to host or something similar Restart the GS4 Services and a new gtx.keystore reflecting the new name is created. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 19
Delete Reference To The Temporary Server 1. Delete Printers: manually delete each printer and then the server itself. 2. Delete Server: once all printers are deleted, you can click the Pencil icon next to the server name and then delete the server. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 20
New server migration has been completed! SSL Certificate issue Troubleshooting If using a SSL Certificate, sometimes the certificate authorities Root certificates do not exist in the Java cacerts keystore, especially if using LDAP over SSL. If you followed the directions and backed up your JRE cacerts keystore, you can drop it into the folder corresponding directory. C:\GS4\jre\lib\security This step is required if using LDAP over SSL and port 636. 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 21
PostgreSQL 10 ONLY PGADMIN 4 Restore Option It s recommended to upgrade to the latest version of Pgadmin 4 version 3.1 or above before attempting the Restore. If you see the following message follow the instructions by clicking the here link to upgrade or read the provided instructions at the end of this document. Create a new database 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 22
Scroll down the Restore option 1. Leave default of Custom or tar 2. Select path to the backup file 3. Press Restore 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 23
Additional information Upgrading PGADMIN 4 to 4. 3.1 or above If you see the following message following the here link to download the Windows update Pgadmin download page https://www.pgadmin.org/download/ 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 24
2018 GoPrint Systems, Inc. All rights reserved. Server Migration 25
Download the current version Run the installer Accept all the default prompts 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 26
2018 GoPrint Systems, Inc. All rights reserved. Server Migration 27
That s it you ve successfully upgraded PGADMIN Hint: after upgrading a new version of PgAdmin 4 appears as a standalone option under Programs 2018 GoPrint Systems, Inc. All rights reserved. Server Migration 28