![]() ![]() #2 Use Orca to modify the Pulse.msi and change SHAREDINSTALL from 0 to 1. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Juniper Networks\Device Id If you already have users that have the Pulse client installed, I recommend doing two things. ![]() Screenshot of Connstore.dat and Registry (click to zoom) If multiple connections are sending the same machine identifier, the PCS device will terminate the oldest session for security reasons. The Pulse Connect Secure device identifies each user sessions by the local machine identifier and expects this value to be unique. When a Pulse Secure Desktop client connects to the PCS device, some session data is sent including the local machine identifier in the connection store file. If this is true, the local machine ID stored in the connection store file may be the same on multiple machine. This issue will occur when Pulse Secure Desktop client is preinstalled on a base image which is used to deploy to multiple machines. There is no specific interval when this issue will occur as it will depend if the multiple user are attempting to login to the computer with the same machine guid. Multiple users report intermittent disconnects with the Pulse Secure Desktop client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |