UNIPRINT SUITE 9.0 R2 SERVER MIGRATION TOOLS
Pharos supplies three small command line tools to help in the process of migrating the Pharos Database in a Uniprint Suite install to a new server:
- DatabaseMigrationTool.exe - this tool copies the Pharos Database from its current server to the new one and upgrades it to version 9.0 R2 of the Uniprint Suite if necessary.
- PrintMigration.exe - this tool identifies the devices that are to be upgraded from older version and updates printers network address in Pharos Database. It is needed when upgrading from Uniprint 8.2 or earlier. It can be obtained from CD from '\server\printsvr\printmigration' folder.
- NameSyncTool.exe - this tool configures the Pharos Database and registry with the hostname details of the new server, and optionally propagates these changes to the other dependent servers.
To migrate the Pharos Database to a new server, ensure that you have met all the requirements outlined in the Pre-install section of this document, and then run the database migration tool on the new server. When the database migration tool completes, it automatically runs the name synchronization tool to update the Pharos Database with the new server's name. The name synchronization tool can also be run by itself if the server's name is changed after the upgrade. For more information on how to use these tools, see "Migrating the Pharos Database" and "Updating the Database Server Name" sections below.
Migrating to a new Print Server
For systems where the Print Server is installed along with the Database and Principal Services, the suggested procedure for migrating:
- Migrate the existing Uniprint database to the new server by running the DatabaseMigrationTool.
- Migrate the Print Server’s printers and queues using the Microsoft Print Migrator tool (Microsoft Windows Server 2003 or older) or using the Printer Migration Wizard (Microsoft Windows Server 2008 or greater). Microsoft Print Migrator tool sometimes sets the printers status to offline. Make sure to set the printer status to online in Control Panel/Printers. Re-start the Uniprint Services and run Pharos PrintMigrationTool to migrate the printers network address to Database, since 9.0 supports only network printers.
- Shutdown the old server.
- Rename the new server to use the old server's Windows name.
- Update the Pharos Database and Registry following the name change by running the NameSyncTool.
Renaming the new machine back to the name of the original Database & Print Server will mean that no other servers or clients will need to be altered to maintain connectivity with the server.
Before running the server migration tools, take note of the following requirements:
- Install the Pharos Database and Principal Server on the new server. You must install Uniprint Suite 9.0 R2 on the new server. Do not install any other components at this stage.
- The old server must be running one of the following Uniprint versions: 5.0, 5.1, 5.2, 5.3, 6.0, 6.1, 7.0, 7.1, 7.2, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, or 9.0 R2.
- The old server must be running SQL Server 2000 or later.
- Enable TCP/IP protocol in old server using SQL Server Configuration Manager.
- Database version on new server should be the same or newer than the DB version on old server.
- The new server must be running SQL Server 2008, SQL Server 2012, or SQL Server 2014.
- When running the tools, you need to be logged on as a user with administrator rights on both servers (typically a domain administrator).
- The tools, along with all the deployment files, must be copied to the new server and run from there.
- Ensure the old database has remote connections enabled. Ensure the firewall on the old database will allow the connection from the new server.
Note: The Migration Tool does not prompt regarding significant Database changes in the way that the in-place GUI upgraders do. A list of feature changes/removals between versions is available in the Knowledge Base. It is recommended that prior to running the Migration, the list is reviewed for any changes that may have an impact on the current configuration: Uniprint Deprecated Features.
Migrating the Pharos Database
Note: The Database Migration Tool should be run on the server where the Database Service is running and not on the machine where the Database itself is housed, if the Database Service and the Database are not on the same machine.To migrate and upgrade your database using the Database Migration tool, follow these steps:
- Stop all active Pharos Services on both hosts.
- Copy the ServerMigrationTools folder and included files from the \tools\utils folder of the CD image to the newly installed Principal Server.
- Install the Principal Service and the Database Service on the new server.
- Run the Database Migration tool from the command line on the new server:
DatabaseMigrationTool.exe -OS oldservername [-OU oldsqluserid] [-OP oldsqlpassword] [-NU newsqluserid] [-NP newsqlpassword] [-R] [-?]
- oldservername is the host name of the old server
- oldsqluserid is the SQL Server Login username of an account with sysadmin privilege on the old server
- <oldsqlpassword is the SQL Server Login password of an account with sysadmin privilege on the old server
- newsqluseridis the SQL Server Login username of an account with sysadmin privilege on the new server<
- newsqlpassword is the SQL Server Login password of an account with sysadmin privilege on the new server
- -R - attempts to propagate the changes to all Pharos Servers.
- -? - displays Help
Note: If new instances of Print Services and Print Center Services (PharosAPI) happen to be installed before migration, and these servers/service instances did not exist in the old database, users will not be able to log in to the Pharos Print Center or use MobilePrint, as the service entries will be lost when the old database is copied across and replaces the newly installed database. In such a case, you must uninstall the new Print Services and Pharos API Services, run the Database Migration Tool, then reinstall these services.Note: If no SQL Server authentication details are supplied, Windows authentication is used. In order to have required permissions to perform the database migration operations successfully, please logon to the machine with a Domain Administrator account. The Domain Administrator account should also have login account on SQL Server.The Database Migration tool will attempt to detach the database from your old host, copy it to the new host (replacing the freshly installed database), perform the upgrade on the database, and update the server details in the database. It can also update registry keys on remote servers so they point to the correct Principal server afterward. This last step will assume remote registry access for the logged in user, so servers with separate account databases may not be changed and will need to be adjusted manually.Note: Once it has copied the database, it will reattach the database on the original server, leaving the earlier version in an operational state.A log file for the migration operation is created in the Pharos\Temp directory.
Updating the Database Server Name
The Database Migration tool will run the Name Sync tool as part of its operation, but the Name Sync Tool can also be used as a standalone tool. The tool requires remote registry access for the logged in user, so servers with separate account databases may not be changed and will need to be adjusted manually.To update the Database Server name using the Name Sync tool, run the Name Sync tool from the command line on the new server:NameSyncTool.exe [-S sqlserver] [-U userid -P password | -W] [-R] [-?]The following options can be specified:
- -S - sqlserver to connect to <including instance name> e.g. <sqlserver>\<instance name>
- -U userid -P password - use SQL Server authentication (where userid and password are the logon details for the sa account)
- -W - use Windows authentication
- -R - update other Pharos servers remotely (to use this new name for the database server)
- -? - display Help
Updating the printers' network address
The Pharos PrintMigration tool performs a compatibility check on all Pharos devices ports. It operates in two modes namely '-check' and '-upgrade'. When the tool run as '-upgrade' mode, it updates the devices network address in Database and additionally the device's windows printer object is deleted provided it is not shared.PrintMigration.exe The following options can be specified::
- -check - this mode enables to audit existing device configuration and returns a list of devices that cannot be upgraded successfully (this mode can only run on the older server). You will need to run the Microsoft Visual C++ 2010 Redistributable Package (x86) on the old server before the PrintMigration check can be run. You can find the package in the Pharos disk image, under
- You are still required to run the 32-bit runtime even if you are on a 64-bit operating system.
- -upgrade - this mode will update the printers network address in Pharos Database and returns a list of un-supported devices (this mode can only run on the new server).
A file for the print migration operation is created in the current working directory.
Copyright © 2015 Pharos Systems International