Mass Deployment of Connect Client w/ Profile - Possible?

[scottyyyc]

I've recently deployed the AWS image of the Access Server. Got it configured quickly and working 100%. Testing so far has gone great - very fast with no complaints.

Client deployment has been another story. In searching around, there's extremely scant documentation on actual, working Windows deployment scenarios. Tons of people seem to have issues with profiles in Windows.

I've tried the latest v2 (2.7.1.104) and v3 clients (3.1.3.713) - both ultimately have the same issue: manually installing the MSI interactively on a workstation works fine... using any sort of deployment tool or script... not so much. The app installs, but no profiles.

No matter what I do or how I install the connect client with virtually any deployment tool (SCCM, MDT, Desktop Central, PDQ etc), the client installs fine, but no profile. This will mean the user will have to call the IT Helpdesk to connect - not ideal.

So my questions are:

1. Is there a known method of mass-deploying the MSI (v2 or v3) client in bulk WITH a profile intact?
2. If not, how would one auto-import a profile? Where do the profiles go? I've tried all the "documented" profile locations, none of them seem to work (the client never detects the profile).
3. Is there any third party OpenVPN-compatible client that can accomplish this? I'm not married to the connect client specifically.

The basic goal here is to deploy the client (v2 or v3, don't care) with the profile in place, so users can simply hit 'connect' without needing to know server details.

[rinzler]

I have the same problem. Did you manage to solve it?
Thank you in advance for your response.

[chipconnection]

I'm also looking for a solution to this. I need to upgrade about 50 clients from 2.7.1 to 3.2.0. The silent install works, but no profiles.

[novaflash]

Connect v3 is quite a different program from Connect v2. It doesn't upgrade v2 to v3. It's a separate program. So no importing of data happens.

At the moment Connect v3 has almost all of the features that Connect v2 had, but also a bunch of new features. One thing missing however is command line support. This is coming in a future release of Connect v3. With that version, it will be possible to use the command line to script importing files.

You can use command line tools on Access Server to generate installer files for OpenVPN Connect v2 or v3 with a profile already bundled inside of it. You just install that and you're done. Profile already present. I would recommend doing that. You can find that information here:
https://openvpn.net/vpn-server-resource ... r_creation