Feature Request: System-wide folder for VPN-Bundles (macOS)

[ChChwill]

Hello!

Would it be possible to add a feature for Viscosity, that checks VPN-Bundles from system-wide folder (eg. /Library/Application Support/Viscosity/OpenVPN)? Or at least add it as a fallback.

This would help enterprise installations/configurations a lot. Especially on devices that has multiple users.

At the moment Viscosity checks VPN-bundles from user-specific folder (/Users/$USER/Application Support/Viscosity/OpenVPN).

[James]

Hi ChChwill,

I've moved this to the Mac version support section, as Viscosity actually already has such a feature. The trick is to use the "Managed" installer template (from the Jamf/Munki guides) which handles machine-wide (rather than per-user) deployment:
https://www.sparklabs.com/support/kb/ca ... nterprise/

It's recommend to use the installer template, as it automatically handles all the tricky stuff for you (helper install, permissions, launch at login setting, etc.). However if you do want handle things yourself manually, you can use the directory "/Library/Application Support/Viscosity.Managed" for your bundled data.

Cheers,
James

[ChChwill]

Hello James,

Thank you very much, I somehow missed that it was under Munki instructions.

Building Viscosity via managed template seems to work fine. However, it seems that Viscosity copies the bundles from "/Library/Application Support/Viscosity.Managed" to user space when you first run Viscosity after the installation. I was wondering what triggers this, and is it possible to trigger this "manually"? Eg. a scenario where you have made changes to Viscosity.Managed folder, and want to update those changes to all users.

Thank you in advance!

[James]

I was wondering what triggers this, and is it possible to trigger this "manually"? Eg. a scenario where you have made changes to Viscosity.Managed folder, and want to update those changes to all users.

Viscosity uses the creation date (not modification date) of the managed bundle directory to determine if an updated version has been deployed. The managed installer template will take care of updating the creation time (along with helper updates etc.), so it's generally recommended to use a built installer where possible.

Cheers,
James