Post-Installation: Optional Customization Deployment | Revu 2018

3. Post-Installation: Optional Customization Deployment

This article applies to:

  • Revu 2018

Jump to other versions:

There are two Bluebeam configuration files containing application settings which can be deployed: the RevuPreferences.xml file which can be deployed at any time, and the UserPreferences.xml which can only be deployed once a new Revu installation has been finished.

RevuPreferences.xml

This file contains all settings configured in the Revu Preferences dialog (Ctrl+K). Clicking Export in the dialog window lets you save the RevuPreferences.xml file to any location, such as a centralized folder on a server. Although it can be deployed as part of an MST or passed as an MSI Command Line you can also do so post-installation using a command line option that calls up the Bluebeam Administrator. This allows you to automate changes within the Bluebeam Administrator.

Setting an Offline PIN Requirement

Revu 2018 lets users setup and Offline PIN for accessing Studio files when they're not connected to Bluebeam Studio. Although this isn't a default requirement, you can make it so by editing the Studio section of the RevuPreferences.xml file on your staging and export it to a staging location on your network. Typically this is the same location as the MSI you are deploying.

The RevuPreferences.xml modification consists of:
         <Studio>
         <RequireOfflinePIN>True</RequireOfflinePIN>
         </Studio>

This can be deployed using the BB_REVUPREFERENCES MSI property.

When this preference is set, Offline PIN creation will be required for all new and existing Studio users. They will not be able to log into Bluebeam Studio without doing so.

Merging Revu Preferences

If you only want to add new settings, you should first open the RevuPreferences.xml file in a text editor and add Merge=”True” to the beginning of the file, before staging it for deployment.

You can find an example of an edited RevuPreferences.xml file this later in this section, but here’s what the header should look like:

<RevuPreferenceDictionary Version="1" Merge="True">

After you have done this we recommend that you delete all the other settings that you do not want to change.

You can also copy or push the RevuPreferences.xml file to:

C:\ProgramData\Bluebeam Software\Bluebeam Revu\<RevuVersion>\Revu
When Revu launches, it will search for the RevuPreferences.xml. When it finds that it’s newer than the UserPreferences.xml file in the user’s %appdata% folder, it will merge the contents into the existing UserPreferences.xml.

UserPreferences.xml

This file contains settings for an individual Revu user. Although this file cannot be deployed to existing installations, it can be deployed to a new one, prior to their initial launch, by pushing a modified UserPreferences.xml to the following location on each machine:

C:\Program Files\Common Files\Bluebeam Software\Bluebeam Revu\RevuVersion#\Revu
Assuming you have already gathered your custom assets such as Profiles and Tool Sets while planning your deployment, you can also copy them to this location.
The first time Revu is launched, the files are automatically copied to the following location in their roaming Windows User Profile:
%APPDATA%\Roaming\Bluebeam Software\<RevuVersion#>\Revu
The RevuPreferences.xml file in this location will be the default for the software. This means Revu will be configured according to the information in this file the first time it is launched or whenever it's reset via Reset Settings.

Deploying Custom Extensions via the Revu.exe Command Line

Revu.exe Command Line Switches

The following switches allow you to select how the import process runs, as well as which assets you want to copy into a user’s default local %appdata% Revu roaming folder:

Importing assets or settings copies them as described above, whereas “Adding” them creates a reference (link) to a shared asset located in a network or other non-default location.
  • /s – You’ll notice this switch in the example shown above, which turns off any on-screen prompts that usually appear during the import process.
    The /s switch does not make the installation "silent."
  • /bpximport:[File] – Imports and activates a profile.
  • /bpxdir:[Path] – Lets you specify a folder path if you want to designate a new profile directory. This is the path to a network shared location where Profiles are located and shared across an organization.
    To prevent users from making changes to the Profiles in this directory, set its Folder Permissions to “Read Only.”
  • /bpxactive:[Name] – Designates a specific Profile as Active in either the users local %appdata% Revu roaming folder, or in a shared Profile directly if you have used /bpxdir: to specify a shared Profile directory in a network location. Make sure the Profile you set as Active is in the specified directory.
    Setting a Profile as Active suppresses the initial "Select a Revu Profile" and “Studio Sign-in” dialogs that appear the first time a new Revu installation is opened.
  • /btxadd:[File] – This tells a Revu installation to use a Tool Set located in a non-default location without importing it.
  • /btximport:[File] – Imports a Tool Set into the current profile directory.
  • /bhxadd:[File] – Tells Revu to use a Hatch Pattern set located in a non-default location without importing it.
  • /bhximport:[File] – Imports a Hatch Pattern set into the current profile directory.
  • /blxadd:[File] – Tells Revu to use a Line Style located in a non-default location without importing it.
  • /blximport:[File] – Imports a Line Style set into the current profile directory.

ARP Modifier

As mentioned earlier in this guide, the MSI Installation package includes an Add-Remove-Programs (ARP) Modifier, in case you want to display the Edition of your Revu software, in addition to the product name and version number.

Note: ARP renaming is determined by the BB_EDITION flag that was set during installation process, and not the Serial Number. You can find further information in the ReadMe file included in the MSI Installation Package.

Default is to run the file without an Edition parameter.

Example:
ARP_Modifier_currentversion.exe

Optional command line arguments let you customize the behavior of this utility.

Examples:

Forces product name to include “Standard”:

ARP_Modifier_currentversion.exe 0
ARP_Modifier_currentversion.exe standard

Forces product name to include “CAD”:

ARP_Modifier_currentversion.exe 1
ARP_Modifier_currentversion.exe cad

Forces product name to include “eXtreme”:

ARP_Modifier_currentversion.exe 2
ARP_Modifier_currentversion.exe extreme

Restore the product name without the edition (Standard, CAD or eXtreme):

ARP_Modifier_currentversion.exe -1
ARP_Modifier_currentversion.exe clear

Calls up the file from a script where the ARP Modifier is located in a network, and sets the installed Edition as eXtreme:

"\\MyServer\Bluebeam Software\ARP_Modifier_currentversion.exe" 2

Bluebeam, Revu, and Bluebeam Studio are trademarks or registered trademarks of Bluebeam, Inc. Microsoft, SharePoint, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

AutoCAD is a registered trademark of Autodesk in the United States and/or other countries.

© 2018 Bluebeam, Inc. All Rights Reserved.

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

 

Related Articles