Pulse Location Awareness Configuration Not being pushed to client

[dcvers_]

I am doing some testing with Pulse as preparation for an upgrade from 7.1R10 to 7.4R4.

In 7.1R10 if I login via a web page Pulse gets installed and the full Pulse Connection configuration associated with her role gets pulled down in appears in the connstore.dat file  as  configuration with a connection-source of "preconfig".

If I do the same in 7.4R4 a get a configuration with connection-source of "dynamic" that just has the uri (the "friendly-name" is also just the URL). In particular it is missing the connection-policy setting used to enable location awareness.

I've tried using the Pulse Connections converted from 7.1R10 by the upgrade and creating a new one after the upgrade with various options but I never get a location awareness enabled configuration pushed to the client.

A lot seems to have change between the two versions on the Pulse/NC side so maybe I'm missing something.

How do I get a location awareness enabled configuration to automatically download to the clients?

[Kita_]

Is 7.1 and 7.4 two separate devices?  If so, you will need to ensure you export the Junos Pulse connection sets from 7.1 to 7.4 using XML import/export.  This will ensure the server-id in the connstore.dat are the same.  When the server-id matches, this will push down the pulse configuration to the pulse client.  If this does not match, this will only create the connection on the pulse client, but will not push any additional configuration within the connection set.

This was designed so only the "home" device pushes pulse configurations.  Any additional connection to any other SA device will only create the connection.