Who Me Too'd this topic

We rolled out a vpn solution with “on-demand” login. This has proved successful and we now wish to convert the configuration to be “always on”

I have changed the portal configuration to “prelogon always on”, but the clients do not pick up this config change unless they manually initiate an “on-demand” connection first. Then the portal config changes get pushed to the client.

What I am looking for is a way to force the client config to update to be always on without the user initiating a manual on demand connection to pull the new config.

How can I achieve this?