Scripting Question

Need help deploying Bluebeam Revu 12.5

08/01/2014 5337 views

Using a KACE 1000

I am attempting to deploy Bluebeam Extreme version 12.5.  I have tried deploying using the Enterprise NetDeploy package InstallSheild executable found here using the syntax below...  While viewing Task Manager I can see that the BBRevuSetup1250.exe starts then calls the BbMain1250x64.exe and soon afterwards both of them disappear from Task Manager.   I read this article that describes exactly what is occurring with me, but have also tried the .MSI route explained by Sinbad, but I think since this article is a bit old, it doesn't reference the exact install package and also it must be a older version of KACE because some of the instructions reference "Verify that registry key exists", which I don't see as an option.

I am completely new to KACE and Dell tech support and Bluebeam tech support are both scratching their heads!   I need help from a Ninja on this one!

Syntax used for InstallSheild executable:

BbRevuSetup1250.exe /z"/SN:XXXXXXX /PK:XXXXX-XXXXXXX" /s /f1"C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\54\setup.iss" /V"EDITION=2"

3 Comments   [ + ] Show comments


  • What operating system are you deploying to, and is it 32 or 64 bit? Are you getting any messages in the application event log?
  • Windows 7 with 64 bit... No error messages found in Application event logs. However, we are also wanting to deploy to Win8 plus 32 bit machines.
  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • I would reach out to BlueBeam Support and request the .MSI At that point download a freeware piece of software called "orca" this will allow you to open the MSI and add the license information etc to it and resave. Zip everything together and upload to the k1000 and reference the following as an example in your override default installation full command line: msiexec.exe /qn /i BluebeamRevux6415.msi (or whatever your .msi filename is). I succesfully deployed this to a production environment, Windows 7_x64, dont beleive Windows 8 would be a big deal.

All Answers



I have found that Managed Installs don't always meet my needs for software deployment. Have you considered running pushing a script to complete the install of Bluebeam? This is what I have done in the past to resolve this problem.

I first build the full command line to install BB, determine if the PC gets NetConfig or not, uninstall previous BB versions, then install BB12.

Answered 08/05/2014 by: bulletcatcher
Orange Belt

  • The script grabs the file from a file server. Is it possible to have the script run in the kbots_cache folder and use KACE to send the file via the agent? I have several users that are not on our local network so deploying these files to them would require them to sign in to our VPN client and that is a bit cumbersome. I've tried editing the script to accomplish this, but I am afraid I've just hacked it to pieces trying to get it to work. Any help you could give me is greatly appreciated. Thank you!
This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.

Hi brad.buckles.

I hope I'm not too late with this reply.
You're right. I was using Kace 5.5 and haven't upgraded for almost a year because we've moved on to System Center in my organisation. However, we still had the old Kace server running and after reading this post I went and upgraded the Kace version to see the options for the install scripts. It is now 5.5.90548.

First you'll need to add the Bluebeam zip file to Inventory, under Software.
Then you go to Distribution and Add a New item, find the new Bluebeam application in the list. It's possible to type bluebeam in the filter field, just to make sure it will only list Bluebeam applications. Select the newly added version.
After this, you will be able to create a Script under the Scripting section, using this new installation package.

What I did was to create an Offline KScript. I made sure that the Status was Production and also that the correct Windows versions were selected. My guess is that version 12.60 should have support for Windows 8.1,but please correct me if I’m wrong.

After this, just below Dependencies, you edit Task 1.The first instruction should be Verify. This is where you Add the first condition, to see if there is already an installation of Bluebeam Revu.

The rest is still working as the guide for version 11.Just make sure you download the MSI package from Bluebeam if you want to beable to edit the settings with Orca.
The Installshield setup is chained with another setup file, which in turn callsan msi. This process makes it very complicated and I have a feeling I think that Windows 7 has a default policy that doesn't allow chaining in silent installation. If this is true, I will need to change some local policy settings to test that as an automated installation.
Iwill need to get back on that after some experimenting.

Reading through the instruction from Bluebeam, I notice that the 12.6 requires .Net 4.5 and if you want to have it installed, it will not work with the msi approach. But the msi will still automatically upgrade from a previous version, if the previous version is 12.1 or higher (I think that's what the guide said).
If you want the setup to download and install .Net 4.5, you will need to use the Installshield setup. On the otherhand you can download it manually and add it to the Zip. Then use Kace to set your own conditions and check if it’s already installed. If .Net Framework 4.5 is not installed on the computer, use Remediation to install it, otherwise (If Success) you continue with installing Bluebeam.

Answered 11/16/2014 by: Sinbad
Senior Yellow Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ