Does anyone know where the information to create the C:\Program Files\Common Files\Juniper Networks\connstore.dat file comes from for a particular user?
If I delete it and the .bak file it gets recreated with all the old settings next time I start Pulse.
I'm troubleshooting a Location Awareness issue some users are experiencing and for these users file is missing the "connection-policy:" setting and the settings don't seem to get updated when they connect to the appliance so I would like to understand where the data may be stored locally.
If this file is not getting updated when connecting to the SA device, this could be a a configuration issue. There is a few options that must be enabled for the connection set to be pushed to Pulse client.
If this does not resolve the issue, was the Junos Pulse client originally downloaded from a SA device or was this pushed via the preconfiguration file? Also, are there multiple SA devices the end user connects to with Pulse?
I don't think it is a configuraiton issue at the SA end as the same configuration is working for most people. Which is why I am digging into the local files. I was hoping to take the configuration files from a user having the problem remove the user setting and copy it to my machine to test but it keeps restroing my configuration
As some background. We are going to migrate from Network Conenct to Pulse so we have created a package the pre-deploys Pulse with a configuration with Location Awareness off but mapping roles associatd with a connection set with it turned on. This means the the first time they manually connected the configuration gets updated. For 95% of pilot users this worked but for a handful it failed.
That should be where it is stored.
If you remove Pulse & then re-install, does the same behavior occur?
Is there anything obviously different about these failing users and those that work (e.g. corporate build version, AV/FW settings)?
I've found the cause of the issue. Basically what I'd done was taken the exported configuration file and deleted the line with he location awareness configuration and used this in our deployment package. The issue was that the version number of this file matched that of the configuration the boxes so Pulse didn't update it. We have duplicate configurations for our different AD domains and for one the Pulse configuration had been "touched" after the export so its version number was different and so Pulse did pull down the full configuration. In the other domains people who were working had had other issues so we'd refresh the connection by deleting the connection installed by the package and then login in via a web browser to pull down the connection (this pulled down the full configuration including the location awareness). So to fix it for every one we just need to touch all the connection configurations to update the version number of the box.
Thanks for all the help on this it certainly pointed me in the right direction to find the fix.