Revu 2018 Administration Guide – Revu Licensing

1. Revu Licensing

This article applies to:

  • Revu 2018

Jump to other versions:

Software authorization usually takes place during deployment process by means of Delayed Authorization, as described in the Revu Deployment Guide. This process is compatible with all three of Revu licensing options (Perpetual, Open, and Enterprise) described on our website.

Switching from Perpetual to Enterprise or Open Licensing

If you need to change your Revu licensing scheme from Perpetual to Enterprise or Open Licensing, you can do so by following the procedure explained in “Migrating Multiple Bluebeam Revu Installations to a New License.”

Licensing and Computer Names

Please consider the following when registering Revu installations on new or re-imaged machines.

  • If your new machines are all based on a common disk image, or are part of a Virtual Desktop environment, you will need to change the machine name before trying to register Revu. If this is not done, you will be in a situation where you are trying to register Revu on multiple instances of the same computer, regardless of IP or MAC Address.
  • If you are re-imaging or installing a new system drive in a computer without changing its original machine-name, our license systems will “view” it as the same computer, as if nothing had changed at all.

Renaming a Registered Machine

There may be a time when you’ll want or need to rename an existing machine that Revu is already installed on. In this instance, you need to “let the licensing system know” about the name change and update the registration.

Although you could go to the Revu menu and unregister the machine (Revu > Unregister), change its name, and re-register it, a quicker method is to change the machine name and then use the following script:

"%ProgramFiles%\Bluebeam Software\Bluebeam Revu\Pushbutton PDF\PbMngr5.exe" /update

You can run this on individual computers using a batch file or push it to the machines in question using deployment tools or login script. In either case the script calls up the Bluebeam Administrator (Pbmgr5.exe) and tells it to update the registration server with the new machine name.

The Bluebeam Administrator must be able to run with elevated privileges, and your firewall and proxy server should not prevent it from connecting to the internet.

Virtual Environment Licensing

Please refer to "Revu in a Citrix Environment" for licensing information within virtual environments.


Bluebeam, Revu, and Bluebeam Studio are trademarks or registered trademarks of Bluebeam, Inc.

All other trademarks or registered trademarks are the property of their respective owners.

© 2018 Bluebeam, Inc. All Rights Reserved.

 

Related Articles