Bluebeam Auto Registration
Hi All
I am trying to deploy Bluebeam 2017 to my environment using SCCM 2012. The deployment and install of the software works fine. The problem is that it does not auto register as they claim it should. The install will enter my SN and Product ID and what should happen is that the software will auto register when the user saves a PDF for the first time.
Well, it just doesn't do that. I even tried to edit the MSI with Orca to set up the delayed registration, that still didn't work. I don't want to have to tell my 200 + users that they need to press the 'Register' button on their Bluebeam install.
Bluebeam support has been useless, going as far as to having me send them my event logs and them telling me I needed to correct some issues on my test system that had NOTHING to do with the software install or the registration.
Here's my script:
"%~dp0dotnetfx45_full_x86_x64.exe" /q /norestart
CALL "%~dp0Uninstall_Previous_Versions.cmd"
msiexec.exe /I "%~dp0Bluebeam Revu STANDARD x64 17.msi" BB_SERIALNUMBER=******* BB_PRODUCTKEY=******* BB_EDITION=0 DA=1 /qn /norestart
***** = my product key but I don't want the world to register their systems with my license.
Anyone have any suggestions?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
five.
7 years ago
I ran into an issue with GMS that stores the serial number in the HKCU key, which means everytime a new user logs in the info would have to be re-entered. This was a lab environment, where new users are the norm. Could that be your problem? That it is using HKCU instead of HKLM?
In my case, I solved that issue using Active Setup.
One thing you can do is use procmon.exe while you are pressing the register button doing the manual way and see what registry keys are updated.
In my case, I solved that issue using Active Setup.
One thing you can do is use procmon.exe while you are pressing the register button doing the manual way and see what registry keys are updated.
Posted by:
Mat666
5 years ago