Cisco Secure Client VPN auto reconnect issues

[TEAM-ind]

I am trying to configure a profile for end users that will simply not try to reconnect after Secure Client VPN disconnects. 

I have Auto Reconnect unchecked, but client still attempts to reconnect after client resumes from sleep or other similar situations.  This is fine as long as the client in not our network.   However, if the client is onsite, and should not connect, the Secure Client still attempts to connect and causes an error.  This would still be OK, but for some reason the MX local config page is presented to the end user, and is in the foreground and prevents the end user from manually disconnecting, causing considerable frustration.  

Anyone seeing a similar issue with Secure Client VPN reconnect behavior?

[PhilipDAth]

In your profile, try something like:

<AnyConnectProfile xmlns="http://schemas.xmlsoap.org/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/encoding/ AnyConnectProfile.xsd">
<ClientInitialization>

...

  <AutoReconnect UserControllable="false">true
    <AutoReconnectBehavior UserControllable="false">DisconnectOnSuspend</AutoReconnectBehavior>
  </AutoReconnect>

[PhilipDAth]

You could also play with this setting (not sure if it should be true or false):

<SuspendOnConnectedStandby>false</SuspendOnConnectedStandby>

[TEAM-ind]

Thanks for the suggestions.  The issue I am seeing is that many of the settings in the profile do not seem to be applying.  I know the profile is in the correct folder location as things like site names and so forth are applying, but preferred settings like these and others are not applying the way that they should be, much like the discussion here:  (1) Solved: Re: AnyConnect Captive Portal - The Meraki Community  In this case the issue was resolved by editing the user preference XML.  However, I believe the profile can and should be applying these settings rather than having to edit at the user level.  So, I am trying to figure out why some settings are not applying as they should from the profile.  I have a case open with Meraki, and the support engineer assigned to the case has been able to replicate what I am seeing.  I am waiting for next steps.