Completing the upgrade process

After you upgrade RICOH ProcessDirector, you must do a few more steps to make the transition easier.
If you upgraded on the same computer, the upgrade process converts your objects to versions that are compatible with the new RICOH ProcessDirector version. All your existing users and groups exist, so your users can log in using the same names and they have the same authority levels. When you log in, you see all of your printers, input devices, and other objects.

If you upgraded on a different computer, you should be able to log in and see all the objects that you imported. However, there are still some manual steps required to finish the migration process.

To complete the upgrade process:

  1. If you upgraded to a different computer with Migration Assistant, take these actions:
    1. Re-enable any antivirus and security software that were disabled during the migration process.
    2. The Migration Assistant cannot import TLS configuration information; you must configure it on the new system again.
    3. If you migrated your primary server from one operating system to another (especially from Windows to Linux or vice-versa), check and update all paths used in your workflow steps.

      Make sure all directory paths are updated to the directory structure of the new system. If you are migrating from RICOH ProcessDirector AIX to Linux or Windows, this step is essential.

    4. Review the log for any errors, including objects that failed to import.
      Objects the use Private key credentials fail to import because the credentials do not exist. Recreate your private key credentials on the target system, then create those objects manually.
    5. Copy all your configuration files to the right locations, so your jobs can find them.

      Restore any configuration files that you store outside of the /aiw/aiw1 file system.

    6. Recreate the visual mechanisms used to help distinguish between RICOH ProcessDirector from another. Use the System identification settings on the System Settings page to set a background color or configure a tab in the banner.
    7. If you created a custom portlet on a RICOH ProcessDirector system prior to version 3.10.2, you cannot import it to a system with RICOH ProcessDirector version 3.12 or later. Create the custom portlet again on the source system.
    8. Update your secondary and application servers, then make sure the migrated objects can connect with the upgraded system.

      See Setting up application and secondary servers for more information.

      • Verify that all input devices and printers connected to the secondary and application servers are functioning properly.
      • Verify that all applications running on these systems, such as Avanti, PitStop, and Ultimate Impostrip®, are able to connect.
    9. If you use the RICOH Supervisor Connect feature, the Migration Assistant copied some settings, but cannot complete the connection process.

      Refer to the procedure Setting up to send data to RICOH Supervisor to connect to RICOH Supervisor.

    10. If you use custom document properties that were created in RICOH ProcessDirector prior to version 3.11.2, copy /aiw/aiw1/config/docCustomDefinitions.xml to the target system and run the docCustom utility to activate them. Custom document properties created in RICOH ProcessDirector 3.11.2 using the Custom properties page migrate just as any other properties do.
    11. Before putting the new system into production, set the value for “Smallest job number” from System Setting to synchronize your job numbering.
  2. Update any secondary and application servers to the new level.
  3. Before they log in for the first time, tell your users to clear their browser cache.

    Information that is stored in the browser cache can cause errors when users try to use the newer level. Clearing the cache prevents those errors.