I'm converting my NetConect users to Pulse, but find managing the Pulse client difficult. How do I get the Pulse Client to auto shutdown when the users logout?
Aplogies if I've overlooked a setting or FAQ. I did search Juniper's site, and the Internet for an answer first.
AFAIK Pulse will shutdown the session once the user logs out of Windows.
I could be wrong about that but we haven't run into this in our use of Pulse. Will see if I can do a test to verify if this is or is not true.
Just did a test and the following was true:
Login to a system as myself, login to Pulse
Logout of Windows, login as local administrator, login to Pulse as myself
Logout of WIndows, login as myself and Pulse is still running
Looks like Pulse stays running across user logouts in Windows.
Not sure how you would go about changing this behavior aside from training users to logout of Pulse before leaving Windows or some other more esoteric Pulse setting on the IVE.
Are you talking about the pulse automatically reconnecting whehn users sign out of the browser.
If it is the same issue,this issue is not seen in 7.3r3 and 7.4r1 pulse i.e pulse 3.1r3 and 4.0r1.
how are you logging out: disconnect from the Pulse client or web?
are you seeing that Pulse is showing as already logged in or "just" running and still requiring you to login?
Not sure if is directed at me or the OP.
In my test I did what a user might do - logout of Windows without telling Pulse to disconnect or exit.
When I signed in to Windows as a different Windows user and went to Pulse I am prompted to log in and then informed that I already have a session running (since I logged in as myself to Pulse in each Windows profile).
Session notice was from the IVE when after I authenticated in Pulse. Pulse itself showed nothing as far as connected/disconnected