Migrating Gespage v8 to v8 (Windows Server -> Windows Server)

You can check your Gespage's version by accessing the admin login page. Your current version is specified at the bottom.

You'll have to update Gespage on your currently running server to correctly prepare the migration.

Updating resets some things, it is crucial to make some verifications first.

If it currently is in 'C:\Program Files\Gespage\GespageCore\server\lib\deploy', then nothing specific has to be done while migrating regarding this file. However, if it's current directory is 'C:\Program Files\Gespage\GespageCore\server\lib\deploy\external', this configuration has to be replicated on the new server (copy/paste the file one level deeper)

Deployed on the standard port (7180)	Deployed on another port (7181 ou 443 usually)

For your Gespage re-installation, knowing where your database runs is extremely important. More often than not, it is local to the server.

An installer for PGAdmin is embedded into Gespage's executable. The default installation folder is 'C:\Program Files'. If a folder named 'PostgreSQL' exists, it means your DB is installed locally.

If no folder is found, it probably means it was installed somewhere else, or that it is using a non-default configuration.

You'll have to find your database if you decided not to use the one Gespage could have installed. Getting thoses parameters for the new server will only be possible by you or someone else that knows your company's network architecture.

/!\ WARNING /!\

It is highly recommended to backup your whole Gespage directory or to take a snapshot of yoserver. If the new version happen to be incompatible, you'll have a way to go back to it's old state.

You'll now have to download the correct version of Gespage (the .exe works for both installs and updates).

Standard Version	Standalone Version

Updating is mandatory since you'll need a save from the same version to migrate a server and import data from the old to newer server.

Once your original Gespage has been updated, your next steps consists in making a save file that'll contain most of your data.

To do so, head to your old server's Gespage admin web page and go to 'Server > System > Backup/Restore'.

The save can be found at 'C:\Program Files\Gespage\GespageCore\db\postgresql\save'

To restore a previous DB save, you first need to make sure the save file comes from the same gespage version. Your old server needs to be updated if you used this opportunity to install the last gespage available on your new server.

The save file created during step 1.4, a DB save dump, is to be send on your new server. Once copied, head to gespage's admin page and go to 'Server>System>Backup/Restore' to fully restore your DB.

To make sure everything went smoothly, you can load the Account and Printer pages and confirm you didn't lose any data.

It is strongly advised to keep the same server IP address on your new server. Doing so, you avoid thoses next steps:

• Change the Server ip address in the 'Server' tab.
• Change the Server ip address in the 'Server>Advanced parameters>Embedded FTP'
• Connect on every Brother, Canon, Epson, Kyocera, Lexmark, Ricoh, Samsung and Sharp to change the server ip address where it appears.
• Push every Toshiba, Xerox, Konica Minolta, Epson and HP eTerminal.

(eTerminal manuals can be found at support.gespage.com, each brand has it's own.)

Then you must copy the following files/folder from the old server to the new one:

This step is not necessary if your Gespage server and the print server are separate servers.

After migration, the MFPs and virtual printers present are those of the old server. At this stage, you need to add the printers on the "Print management" side, a Windows Server tool for print servers.

Once the printers have been added, a restart of the GespagePrintService service is necessary.

In gespage, the visible printers are now those of the old server and the new one. You will be able later to clean the interface but for practical reasons, it is better to keep the information as long as possible on the new server before deleting any duplicates.

You now need to configure the new MFPs like the old ones (rules, terminals, group of printers, etc.).

Depending on the mode of operation of the MFP, eTerminals will either:

• Be redeployed via the Gespage interface (Toshiba for example)
• The links will have to be modified directly on the web interface of the copier (ex: Sharp or Canon)
• Be reinstalled (Ricoh)

For Toshiba Brand:

Go to the Gespage administration interface, in the list of all terminals.

Identify the affected terminal:

Then, put again the MFP admin credentials and click 'Validate' to redeploy the e-terminal.

It will be necessary to refresh the screen of the copier so that it takes the modification into account.

Do not hesitate to give support a call, or send an email to support@gespage.com, if you are not sure of the best way to redeploy your terminals.

Among the configuration of the old server which does not rely on the DB, we will also find the temporary directory used by the advanced scan.

On admin page, go to 'Server>Document flow>Scan profiles>Settings'.

If a network folder is specified, and it is still shared on the old server (test done with Windows Explorer), you will need to make sure to recreate a shared folder on the new server.

Moreover, if OCR processing is present, tesseract will also have to be installed on the new server.