6.3 Migrating from 1.1 to 2.1

You can migrate from iPrint Appliance 1.1 to 2.1 using a configuration file (iprintconfig.zip).

Ensure that the copy of the configuration file (iprintconfig.zip) of the earlier version of the appliance is available before performing migration.

  1. Create a copy of the configuration file (iprintconfig.zip) of the earlier version of the appliance. For more information, see Exporting the Configuration File.

  2. Shut down the earlier appliance. The new appliance will be configured with the same IP and network settings.

  3. Deploy iPrint Appliance with any virtualization software that can run the .ovf, .vhd , or .xen file formats. For more information, see Configuring Virtual Environment.

  4. When the appliance is powered on, click the Console tab. Ensure you provide the same network configuration, passwords, and time zone as that of the earlier version of iPrint Appliance from which you exported the iprintconfig.zip configuration file.

    The iPrint Appliance installation is now complete.

  5. On a Web browser, use either the host name or the IP Address to access the Management Console. For example, or http://iprint.example.com/admin.

    Ignore the security certificate warning, and continue to the iPrint Appliance Management Console. To avoid the security warning prompt every time you access the iPrint Appliance Management Console, you can add the certificate to the trusted certificates list on your browser.

  6. Specify vaadmin or root as the user name.

  7. Specify the password, then click Log in.

  8. Click Migrate Existing iPrint Appliance.

  9. In the Configuration File option, click Browse..., then select the configuration file exported from a previous copy of iPrint Appliance. For more information about the iprintconfig.zip, see Exporting the Configuration File.

  10. Specify the iManager password that was used to configure the earlier version of the iPrint Appliance.

  11. Click Finish.

    The time taken to complete the configuration depends on the size of the earlier version configuration file. On successful migration, the appliance reboots the VM.