Careers    Contact

Close this search box.
Close this search box.

Facebook    LinkedIn    YouTube     

The Revu 21 Deployment Process

When it comes to installing an application, many are familiar with the countless windows that require a button to be pressed for the installation to progress. With the release of Revu 21, the new process for creating and managing deployment has been modified. A deployment is recommended for organizations requiring mass installment over their network. This blog post is meant for IT managers with a basic understanding of deployments, command lines, and MSI file types.


Below, we’ll take a look at the new Revu 21 deployment process.


Some notable facts about Revu 21

  • The need for Markup Mode and View Mode is not required, as the features and functionality are now determined by the Subscription tier login.

  • Due to the simplicity associated with Subscription and Deployment, there is no longer a need for the Configuration Editor.


First, download the deployment package that contains all the files necessary for a successful installation. This package can be found on Revu’s webpage. 



Once you have the installation files, you can begin exporting your preferences to embed in the installation. This is located under Revu > Preferences. Once your preferences are saved, you can export the .xml for future use.



Uninstall script

Within the deployment package, an uninstall script is included to run a clean uninstall of all previous Revu products. Make note that this file is updated with every release of Revu. Changing the file type from .txt to .bat is the only requirement.

You can save this file to the deployment server and run the script as your first deployment step. Below is an example of what that command line will look like.



install script

Once all previous versions are uninstalled, you can begin creating the installation step for the deployment. Below are some example installation scripts and an explanation of the options we have.

Note: The OCR feature is a separate install line.

/i – Tells the windows install to call up the msiexec.exe to run an installation

/qb – Tells the windows install to run in an unattended mode but displays a progress bar

/qn – Tells the windows install to run in both an unattended and silent mode

msiexec.exe /i “MySeverBluebeam DeploymentRevu 21Bluebeam Revu x64 21.msi” /qb

msiexec.exe /i “MySeverBluebeam DeploymentRevu 21Bluebeam Revu x64 21.msi” /qn

msiexec.exe /i “MySeverBluebeam DeploymentRevu 21BluebeamOCR x64 21.msi” /qb


Customizing Your Deployment Script

Optional Properties Command Lines:

Enable or Disable in-app update notifications: Enabled (default) = 1, Disabled = 0. See notes.

Enable or disable sending application usage info to Bluebeam. Send (default) = 0, don’t send = 1.

Set as the default application (default) = 1, Do not change the default = 0

Bluebeam Revu desktop shortcut (default) = 1, No shortcut = 0

Bluebeam Stapler desktop shortcut = 1, No shortcut (default) = 0

Disables various Revu features: All Features Enabled = 65535 (default). (See Enabling and Disabling Revu Features on the deployment page)

Install and enable = 1, Disable (default) = 0

Enter the UNC or fully-qualified path to your custom. jobOptions file.

Enter the UNC or fully-qualified path to your managed NetConfig folder.

Enter “A4” to override the default page size for the Bluebeam PDF printer.

Disables the Revu HTML Welcome page and Workflow Training Videos page. Enable (Default) = 0, Disable = 1
Creates a registry entry ComputerHKEY_CURRENT_USERSoftwareBluebeam Software21Revu and DWORD named WorkflowsInitialized“.

Enter the UNC or fully-qualified path to your RevuPreferences.xml file.

Disable Check for Pending Reboot = 1, Check for Pending Reboot = 0

Determines which of the Bluebeam plugins are enabled. The default value of 1023 enables all of them. (See Enabling the Bluebeam Plugins on the deployment page)

Customized Deployment Script Example

In the example script below, we are using the install command (/i) as well as a couple of others. The “Disable Welcome” screen option is enabled with an assignment of one. Our preferences will also be applied since we are pointing to a preference file in an example server location. Lastly, the unattended option with a progress bar is enabled with the /qb command.

msiexec.exe /i “MySeverBluebeam DeploymentRevu 21Bluebeam Revu x64 21.msi” DISABLE_WELCOME=1 BB_PREFERENCES=”MySever\Bluebeam DeploymentRevu 21″ /qb

Share This Article

Join the Conversation

Share your thoughts, questions, and insights with us. Your contributions drive the dialogue.

Leave a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Explore Related Bluebeam Content

Let’s Get Started

Reach out today to take your business to the next level.