Bluebeam Revu X64 20
Danel Potvin
Bluebeam Perpetual Licensing registers Revu Standard, CAD and eXtreme on a per workstation basis using a serial number and product key, which is sent to our licensing server during the initial registration.
Although registration and activation usually takes place during either an Enterprise or manual installation, you can manually register an individual Revu installation by following the steps listed below:
To help you keep track of your license usage, we offer a License Key Lookup page where you can generate a report of currently registered machines, and determine the number of available seats. All you have to do is enter the serial number, product key, and the email address listed on the license, then click Get Info.
You can find the serial number by clicking Revu in the top menu (Revu > About). A new dialog will open, displaying the serial number in the upper-left, below the title and version number.
Communications between the computer and licensing server are conducted over an HTTPS connection, and include the Revu version number, serial number, product key, computer ID (the security ID), and the username.
We understand that fully upgrading software throughout an entire organization takes time. So when you upgrade your Open License, your previous versions of Revu will remain usable and share the same pool of seats. You will also see that the new version of Revu is given a new Product Key that is tied to your original Serial Number. This means that the same Serial Number for your Open License can be used across multiple versions with each version having its own unique Product Key. This allows for ultimate flexibility when your environment requires incremental upgrades.
Enterprise License management is done through the Bluebeam Gateway. Detailed instructions for using this web portal can be found in the Bluebeam Gateway User Guide, and as with an Open License, you can perform various tasks related to licenses such as tracking, reporting, revoking, and reissuing (Revu 2015.5 through 20).
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 Revu Installations to a New License.
As of Revu 2019, if the application is registered, Revu will check for computer name changes on launch. If the computer name is changed, Revu will detect the change the next time the application is opened, or any of its associated plugins are initialized. Revu will then unregister the system from our license server (if connected to the internet).
If you are on Revu 2018 or older, you could go to the Revu menu and unregister the computer (Revu > Unregister), change its name, and re-register it. A quicker method is to change the comouter name and then use the following script:
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 Console application (PbMngr5.exe) and tells it to update the registration server with the new machine name.
If you or your users have further questions about using Bluebeam Studio, please refer to Bluebeam.com, as well as the Bluebeam Support site where you can find information about various aspects of the technology including:
The Bluebeam Administrator lets you configure and control Revu using the functions and features on the various Tabs as described in the following sections. These settings can be pushed out to your end-user machines as a means of standardizing your post-deployment customizations.
All Revu editions will list the plugins for Microsoft Office (Word, Excel, Power Point, and Outlook), but the plugins for AutoCAD, Revit, SolidWorks, Navisworks, and SketchUp Pro only appear on machines running Revu CAD or eXtreme.
This is where you can set the location of various Revu settings and assets. They can remain in the default local folders listed in the Unmanaged section, or they can be accessed from a centralized server location which you can set in the Managed Net Configuration section. However, you can also configure Revu to use a combination of local and network locations based on folder paths you define in the Unmanaged section.
The Bluebeam Administrator creates a registry file named Netcfg.reg containing all affected registry keys. This file is located in the root of the managed folder (U:\netconfig in the preceding example), and it can be distributed as part of an MSI deployment as described in the Revu Deployment Guide.
When this is enabled, the Combine Files in Revu and Convert Files in Revu options will be available in the pop-up menu when the user right-clicks on an applicable file on their desktop or in Windows Explorer.
Clicking this button opens the Folder Options dialog which lets you select the default location where new PDF documents produced using the Bluebeam Stapler will be saved. The available options are:
In addition to displaying the printer name, driver, and printer port, the printer section is where you can select the default page size from the available list of pages sizes. You can also edit the page size list via the Manage Pages button as described below.
The PDF Type dropdown lets you decide which printer driver will be used when creating PDFs from AutoCAD.
Your choices are either the default PDF driver or the Heidi (AutoCAD HDI) driver, which are explained below:
This option uses the Bluebeam PDF printer, which supports TrueType fonts for creating PDFs from AutoCAD with searchable text. In addition to offering better image quality, this driver also lets you add more Page Sizes and synchronize them across your network for use by all of your Revu CAD or eXtreme users.
This setting can be distributed to your other Revu CAD and eXtreme clients as part of an MSI deployment as described in the Revu Enterprise Deployment Guide, or you can manually configure individual machines by following the steps listed below:
This creates new log entries that are specific to the issue. Clicking it creates a zip file (logs.zip) containing the complete set of log files for all Revu components and plugins. This is attached to a new email, addressed to sup...@bluebeam.com.
Some features that were previously found in the Bluebeam Administrator have been moved to the Revu Preferences under the Admin section, including Reset Settings, Backup Setting, Logging, and client-specific Net Config settings.
When running a Reset of the Revu Settings, the Backup.zip file is created in %Appdata%\Roaming\Bluebeam Software\Revu\20\
This applies to running a Reset from within Revu > Preferences > Admin > Reset, Bluebeam Administrator Console > Help > Reset Settings, and via the Command Line.
The default path for Stamp files is ProgramData\Bluebeam Software\Bluebeam Revu\20\Stamps. You can choose a different Stamp folder by clicking Browse and selecting the desired folder.
For example, you might go to Interface > File Access to configure a connection to Microsoft SharePoint or Bentley ProjectWise, which you will then deploy to your user population.
If you would like to use a set of Revu Preferences across all or part of your organization, you can click Export in the lower left of the Preferences dialog and save them to a network share. The RevuPrefences.xml can be distributed by following the process outlined in the Revu Deployment Guide.
Complete instructions for managing, exporting, and importing Revu Profiles can be found in the Revu Manual, but once a Profile is created, configured, and saved, it can be exported to a central location by clicking Export in the Manage Profiles dialog. After this, it can be deployed by following the process in the Revu Deployment Guide.
You can also import a profile into a Revu installation by navigating to its location and double-clicking the .bpx file. Alternatively, you can also import it by clicking Import in the Manage Profiles dialog, selecting the file, and clicking Open.
All tool sets are saved as .btx files that can be copied to a network drive or sent directly to users. As with Profiles, tools sets can be imported directly into Revu by double-clicking on a .btx file, or from the Manage Tool Sets dialog.
To export a Tool Set, open the Manage Tool Sets dialog, select the Tool Set, and click Export. When the Save As dialog opens, select the destination folder you want to export it to, and click Save. If your users will be sharing this Tool Set, you will need to save it to a network location they can access.
A locked Tool Set appears in the Tool Chest with a blue padlock located to the right of its name. As the Administrator, you can grant any user write permissions to the file and set others to read only. A user with write permissions to the Tool Set will be able to check the file out and add changes. Any changes made to a Tool Set will affect all users sharing that Tool Set.
Revu includes several standard Hatch Patterns used for filling in markups, which can be exported, imported, or added in the same manner as Tool Sets. Along with this, these Hatch Pattern (.bhx) files can also be exported to a centralized network location from where they can be deployed to your Revu installation.
You can find details about deploying Hatch Patterns within your organization in the Revu Deployment Guide. Information about managing exporting, importing, adding, or otherwise working with your hatch patterns can be found in the Revu Manual.
Revu has direct integration with Microsoft SharePoint and Bentley ProjectWise document management systems (DMS). You can check-in, check-out, and view files from either a ProjectWise DataSource or SharePoint Document Library from the Revu interface.
c80f0f1006