Migrating multiple installations to a new license

Applies to:

  • Revu 20

Problem

Your organization has Revu installed and registered on multiple computers, and you need to switch them to a new license (serial number and product key) for the same version and edition.

Solution

The process involves running a script which automatically un-registers, and re-registers the installations with the new serial number and product key.

Although this can be done for any Revu license type, this solution is most useful for an organization consolidating multiple Perpetual Licenses to a single license or migrating a Perpetual License to an Enterprise or Open License (Revu eXtreme 2015.5 and above).

You can run the script from the Command Prompt if you want to.

This process only works if there are available seats on the new license.

All versions of Revu are supported, but the version number of the current software on the computer must match what's listed on the new license. For example, a license for Revu 20 will only register other Revu 20 machines.

You don't need to reinstall Revu if the new license is for the same edition (Standard, CAD or eXtreme) that's installed on the machine.

The Script

Although the complete text of the script must be typed on a single line, it does have two parts. The first section "calls up" the Bluebeam Administrator. For Revu 20, you'll type:

"%ProgramFiles%\Bluebeam\Software\Bluebeam Revu\20\Revu\PbMngr5.exe"

The second part of the script tells the Bluebeam Administrator what action to take along with information it needs to use. In this instance, it will use the /register switch to register the installed software, along with the version number, serial number, and product key listed on the new license you're moving to:

/register [<version> <serial number> <product key>]

You do need to type the quotation marks, but the brackets [ ] and < > in the text above are there for illustrative purposes only, and should not be included in the script.

Also, please remember that letters in the Product Key must be entered as upper case, and the version number listed on the new license must match what's currently installed on the computer.

A single Open License uses a single serial number for all version numbers, with the Product Key signifying the differences.

In an example where someone wants to migrate their Revu 20 installations to a new Revu 20 license, where the serial number is 1234567 and the product key is ABCD3-5FGHIJK. In this case they'd enter the following on a single line, as if it were a complete sentence, including the quotation marks:

"%ProgramFiles%\Bluebeam\Software\Bluebeam Revu\20\Revu\PbMngr5.exe" /register 20 1234567 ABCD3-5FGHIJK
Delayed Authorization

If you don't want the registration process to occur until after the user has logged into the machine, you can add the "NoAuth" switch to the end of the script as shown below:

"%ProgramFiles%\Bluebeam\Software\Bluebeam Revu\20\RevuPbMngr5.exe" /register 20 1234567 ABCD3-5FGHIJK NoAuth
Delayed Authorization isn't available or necessary for Open Licenses because the license server is only contacted at the time Revu is opened.

More Information

See the Bluebeam FAQ page for additional information about Enterprise or Open License options.

Setup

Revu 20

Installation

Licensing & Registration

If your organization has Revu installed and registered on multiple computers, and you need to switch them to a new license for the same version and edition, this article describes how you can.