Specific tasks during migration

During the migration process, it is very important to make sure that all objects are correctly backed up and your initial configuration is correctly restored. Therefore, these sections list all important areas where you should take extra steps for an accurate migration process.

Samba software and configuration for /ipdata and interoperating

If the source pdserver that must be migrated is interoperated with another server, you must set up the interoperating environment on the new server.

To find more information about this procedure, follow the instructions from Configuring InfoPrint systems for interoperability.

If job ticketing is used, you must configure the /ipdata folder. For more information about this task, see the Using the InfoPrint Submit Express Client section in RICOH InfoPrint Manager for Windows: Getting Started.

Associated installed products and InfoPrint Manager features

PPFA
If you have this feature installed, you must install it from the InfoPrint PPFA Feature DVD on the new server. If you have customized PPFA source files, you need to copy them to the new server for later processing.
AFP Resource Installer
This is an independent Windows application. You need to make sure that the resources used by the InfoPrint Manager objects are available on the new system.

Custom auxiliary-sheets

If the output shows more than the default sheets that come with InfoPrint Manager (64xx, accounting-log, blank, brief, full, job-ticket and none), ISMU automatically copies the customized sheets to the new server. The customized user-exits from <install_path>\usr\lpp\psf\exits\psf are also copied.

IPPGW configuration

Make sure that the service is started by following these steps:

  1. Go to Control Panel ⇒ Administrative Tools ⇒ Services.
  2. If the service InfoPrint Manager IPP Gateway is started, start it on the new server too.

    To do it, follow these steps:

    1. From the Management Console, select Edit ⇒ Service Configuration.
    2. Select the Automatically start IPP gateway.. option.
    3. To verify that the gateway is working, open a browser and enter the following address, replacing serverhostname with the DNS hostname of the system where the IPP gateway daemon is running: http://serverhostname:631/printers.
      Note:
    • IPPGW can be run only with the default port which is 631.
    • Only a person with root user authority or the InfoPrint Manager user can run this command.

Custom exits for ACIF and MVS Download

If there are any ACIF exits, you need to copy and restore all the MVS Download exits located in \bin\mvsdsubm.exe and \exits\mvsd (source files and objects) to the right location on the target server. Also, you need to copy all the ACIF exits located in \bin\ (apk*.dll, asciinp*.dll and dbblank.dll) and the source files located in \exits\acif\ directory.

Windows port monitors

To check for Windows port monitors, enter this command:

# pdls -c destination -r attachment-type -U <server_name>

If there is a destination with attachment-type=other-driver, you need to complete these migration steps for the port monitor:

  1. Enter this pdls command: 
    # pdls -c destination -r device-name -U <server_name>:<ADname>
  2. The output shows the name of the port where this DSS sends the data.
  3. From Windows Printers and Faxes, right-click one of the printers, select Properties, and then select the Ports tab.
  4. From the list of ports, you need to locate the one that was returned by the previous pdls command. Select it and press the Configure Port button to get all the details of the port monitor used (port monitor type, IP address, and so on).
  5. Install the same port monitor on the target machine and create a port with the same properties identified in Step 4.

Registry data about psfin

You need to check first if the psfin data contains the default values. To do it, follow these steps:

  1. Open the Management Console.
  2. Go to Options ⇒ Customize Input Manager.
  3. Check if these values are the default ones:
    • Directory for segment lists: %APPDATA%\RICOH\InfoPrint Manager\var\psf\seglist
    • Directory for segments and percent usage threshold: %APPDATA%\RICOH\InfoPrint Manager\var\psf\segments
    • Workspace management: automatic
    • Default segment size: 5000
    • Percentage of workspace for retained segments: 5
    • Enable trace: unchecked
  4. If the values match the default ones, no work needs to be done; otherwise, you need to modify the defaults on the new server to match the ones from the source server.

Custom fonts paths

If you use other fonts than the ones shipped with the product, you have to migrate them.

To migrate the fonts, follow these steps:

  1. Open the Management Console.
  2. Go to Edit ⇒ Service Configuration.
  3. Locate the Default font search path filed.

    If it has a value different from the default one (\fontlib), make sure that the same path is set on the new server, that it exists, and that it contains the same fonts as the one on the original server.

  4. If you have set the resource-context or resource-context-font attributes for any actual destination to point to a custom path, you have to migrate the custom path.
  5. If you have set the above attributes for a default document object, you need to have the path and fonts on the new server too.
  6. To check the values of these attributes, use the following pdls commands: 
    #pdls -c destination -r resource-context <server_name>
    #pdls -c initial-value-document -r resource-context <server_name>
    #pdls -c destination -r resource-context-font <server_name>
    #pdls -c initial-value-document -r resource-context-font <server_name>
  7. Copy the font folders pointed to by the attributes listed above to the new server. Also, set the Default font search path field in the Management Console to match the one from the original server.

Multi-server environment and credentials (user/password)

The Management Console Registry can be seen by opening the Management Console and selecting Edit ⇒ Service Configuration. There are 8 paths listed there. The default values for them are:

  • Install path: 
    C:\Program Files\RICOH\InfoPrint Manager
  • Base namespace path: 
    C:\ProgramData\RICOH\InfoPrint Manager\var\pddir
  • Remote namespace folder: none
  • Workspace path: 
    C:\ProgramData\RICOH\InfoPrint Manager\var\pd
  • AFP support workspace path: 
    C:\ProgramData\RICOH\InfoPrint Manager\var\psf
  • Default fonts search path: 
    C:\Program Files\RICOH\InfoPrint Manager\fontlib
  • Default resource search path: 
    C:\Program Files\RICOH\InfoPrint Manager\reslib
  • Shared client path: none

If you have modified any of these paths, you need to make the same changes on the target server:

  1. On the new installation, stop the pdserver and open the Service Configuration dialog.
  2. Change the paths that were customized to match the ones from the original server.
  3. Copy the contents of the font and resource folder from the original server to the new one.
  4. Start the pdserver.

Management Console Edit ⇒ Service Configuration checkboxes

  1. Open the Management Console.
  2. Go to Edit ⇒ Service Configuration.
  3. Check if the following checkboxes have these default values:
    • Automatically start server during system startup = checked
    • Automatically start IPP gateway during system startup = not checked
    • Confirm object delete = checked
    • Run notification server on this system = checked
    • Run InfoPrint Manager LPD service = checked
  4. If any of these values do not match, open the Service Configuration dialog on the new server and check the same checkboxes as on the original server.

“Communication Ports” Management Console registry

  1. Open the Management Console.
  2. Go to Edit ⇒ Service Configuration.
  3. Check if the following fields have these default values:
    • Server interface port numbers: 6880 through 6889
    • Client interface port numbers 6874 through 6877
  4. If any of these do not match, open the Service Configuration dialog on the new server and make the same modifications as on the original server.

Windows Gateway printer definitions

Check if Windows Gateway printers are installed on the source system:

  1. Open the Management Console and select Objects ⇒ Windows Gateway Printers.
  2. If there are printers defined, then you need to migrate them:
    • In the Management Console, look at these Gateway Printer normal settings (share name, target destination, Windows driver name, poll interval, and so on) and the Advanced settings and write them down.
    • On the target system, install the printer driver used by each gateway printer and then go to the Management Console and create the gateway printer with the same settings from the first step.

DPF and MVS Download settings

If there are folders in the \var\pd\dpf\receivers directory, these folders must be copied to the new server. Each of these folders represents one DPF Host Receiver.

After that, check if the configuration of the receivers was customized:

  1. Open the Management Console.
  2. Go to Options ⇒ Preferences.
  3. Check these default values:
    • The field "MVS Download receivers view interval" is by default 0.
    • The field "DPF Host receivers view interval" is 30.
    • "DPF Resources view interval" is 0.
    • The "Disk Usage for Jobs/Resources directory" is unchecked.
    • All three checkboxes for "Optional DPF Resource columns to display" are checked.
  4. If the existing values are different from the defaults listed above, make the same changes on the target server.
  5. For every receiver from the Management Console ⇒ MVS Download Receivers, follow these steps:
    • Double-click on each receiver and write down the settings of the receiver.
    • On the new server, recreate each receiver from the Management Console ⇒ MVS Download Receivers by right-clicking it and selecting New.
    • Use the same settings that were previously written down.
    • Also, for each receiver you check the file from the “Destination Control File” field. The default file should be \var\pd\mvsd\mvsdmap.txt. If this is not the default file or if the default file has been customized, copy it to the same location on the new server.
    • For each receiver in the Advanced properties window, check if the field “Exit Program Name” points to a file. If it does, copy this file at the same location on the new server.
Parent topic: Manual process