Best Of

Chris,

Might I suggest purchasing a single unit of each and doing to good old fashioned bench testing to see what works best for your environment.

At work I currently run a Surface Pro, but it has 32GB of RAM and an Intel i5 processor. I have not heard any testimonials of Revu running on a snap dragon yet so I'm not sure what you could expect. That said, I pulled the below from Google:

Known Limitations

• Bluebeam PDF Printer: Native ARM versions cannot use the dedicated Bluebeam PDF printer. You must print your documents using the Microsoft Print to PDF feature instead.
• Legacy Plugins: Some CAD and Office plugins may have compatibility issues when running natively on ARM architecture.

I read somewhere (?!) that more features would be added to the cloud-based version in June. Here we are in June so hoping for something soon.

We currently deploy a solution that has a powershell script that copies our company made stamps to the C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps folder. This has been working fine for a long time.

With 21.10, we noticed that our script was failing. Turns out that on new installs of 21.10 (so not an update), the permissions are broken and there is no way to access this folder. As mentioned, there is no issue with upgrades or with a clean install of 21.8 and earlier.

Is this a known issue? Also, with this being broken, is there a better way for us as a company to deploy stamps for our employees to use in Bluebeam?

Thanks in advances.

I am new to Revu, but well experienced with Acrobat. As a Civil Eng, all our work is in decimal feet. I searched the Community and see several previous discussions, but none seem to work for me on Revu 21. I want to make decimal feet with no dimesion label as my default setting for all measurements.

I'll change it for a measurement, and then right click that measurement and click Set as Default, but the very next measurement returns to ft in with a label.

TIA!

If you deploy in Intune make sure you run that in the System context, not the users.

$Path = "C:\ProgramData\Bluebeam Software\Bluebeam Revu\21\Stamps"


# Ensure the folder exists

if (Test-Path $Path) {


    # Grant Everyone (well-known SID S-1-1-0) Modify rights, recursive

    icacls $Path /grant "*S-1-1-0:(OI)(CI)M" /T /C


} else {

    Write-Output "Path not found: $Path"

}

Our users who have created their own custom stamps have now all lost access to them. I assume this was an oversight and not intentional, but it's costing us time to remediate it.

Hi everyone, thanks for raising this. In Revu 21.10, stamp storage and access behavior changed for security reasons, so Revu no longer uses the shared machine-level stamp location as the default location for user stamps.

To deploy and share a common set of stamps, we recommend storing those stamps in a customer-managed shared folder outside Revu’s default stamp location, then configuring each user’s stamp path to point to that shared location. This allows your IT team to manage access, permissions, and deployment according to your organization’s security policies.