Revu 2018 Administration Guide – Bluebeam Administrator

3. Bluebeam Administrator

This article applies to:

  • Revu 2018

Jump to other versions:

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.

Further information can be found in the Bluebeam Administrator Help Guide, but one example of how your Revu clients can be configured is through the available parameters on the Net Configuration (Net Config) tab.

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.

Unmanaged Net Configurations

In a typical Revu installation, the Unmanaged option is enabled by default. In this instance, the assets and settings are in various locations within the user’s Windows profile under C:\ProgramData.

Managed Net Configurations

To configure your Revu installations to access all settings and assets from a centralized server location:

  1. Select a computer to use as a “staging” machine and copy any custom settings or assets into their corresponding default locations listed when the Unmanaged option is enabled.

    You can easily open the default folder locations by double-clicking on their corresponding folder paths.

  2. When you have finished copying the items, enable the Managed Net Configuration option.

    A dialog will open, where you can either browse to an existing network folder you want to use as the centralized location or create a new network folder.

  3. In either case, choose the folder and click Select Folder.

    When the Copy All Files dialog opens click one of the following three choices:

    Copy All, which creates folders for the asset type or setting in the server location, and copies everything to the correct location.

    Merge, which takes all locally defined settings and resources and merges them with any existing items in the shared location.

    No Copy,which points to the network folder, but does not copy or integrate anything into the folder.

Once the operation has completed, the Net Config tab will display the locations of all assets and settings.

If you want to prevent your end-users from making changes to the centralized network folder, you can set the folder permissions to “Read Only.”

Centralizing Selected Assets

If you only need to centralize certain items, for example, just your custom stamps, you can do so by following the steps listed below:

  1. Select a computer to use as a “staging” machine and copy any custom settings or assets into their corresponding default locations that listed when the Unmanaged option is enabled.
  2. Open the default Stamps folder by double-clicking the folder path, copy your custom stamps into it, and then close the folder. A dialog will open where you can either browse to an existing network folder you want to use as the centralized location or create a new network folder. Choose the folder and click Select Folder.

  3. When the Copy All Files dialog opens click one of the following choices:

    Copy All, which creates folders for the asset type or setting in the server location, and copies everything to the correct location.

    Merge, which takes all locally defined settings and resources and merges them with any existing items in the shared location.

    No Copy,which points to the network folder, but does not copy or integrate anything into the folder.

Now all your Revu assets and settings – except for your stamps – will still be in their default locations.

Deploying a Managed Configuration

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.

You can deploy this registry file to individual workstations to quickly apply the managed configuration.

When distributing a Managed Net Configuration as part of an MSI deployment, the changes will not take effect until the client machine is restarted. However, a restart is not needed when manually configuring an individual machine.

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