Starting 8.2R3, an option called Assume Ownership
will appear in the Pulse Secure Client Connection menu. This option was added to help ease managing multiple connection sets across multiple Pulse Connect Secure devices.
As a best practice, it is recommended to make all changes to a connection set on one Pulse Connect Secure (Owner) device, then push these changes to all other devices via push configuration or manually by XML import/export. This will ensure the connection guid for each connection set are identical across all devices and Pulse users will get the latest update regardless of the device they are connecting to.
Additionally, the following values were added to help the PCS administrator to identify the owner of the connection set:
- Owner - This will been the hostname of the device (Under Network > Overview) where the connection set was created from
- Last Modified - The time and date the connection set was modified
If the hostname of the device does not match the Owner of the connection set, connection set will be greyed out and will be read-only. The following message will appear when attempting to modify a connection set where the hostname and owner do not match:
This appliance does not have permission to edit this connection set,
because it is not the current owner of the connection set.
The current owner is XX.XXXX.XXX.
For step-by-step instructions how to take ownership, please refer to KB40578 - Failed to update connection set after the upgrading to 8.2R3+ with the message "This appliance does not have permission to edit this connection set, because it is not the current owner of the connection set. The current owner is unknown."
The PCS administrator should consider taken ownership under the following conditions:
- The hostname of the device was changed due to replacement or RMA
- Change of the master Pulse Connect Secure device
Assume Ownership will only change the Owner of the connection set. Connection GUIDs and Server ID will not be changed.