- Pulse Secure Community
- :
- About te6
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
07-24-2015
te6
Occasional Contributor
10
Posts
2
Kudos
0
Solutions
02-25-2022
07:36:AM
1 Kudo
This worked for me. Not a very elegant solution, but a solution nonetheless.
... View more
08-24-2021
07:56:AM
This is the kb for privs necessary to join to ad domain. my question is, in the steps where checkboxes are checked, is it implied that none of the existing checked boxes get unchecked? Or are the listed items the only items that should be checked?
... View more
Labels:
08-06-2021
01:01:PM
but you will probably have to download the latest defender updates and run a full scan before you connect... (on my machine this takes 4.6 hours)
... View more
08-06-2021
01:00:PM
contact your vpn admin and tell them that ESAP 3.8.2 breaks hostchecker for machines protected only by Windows Defender. Rolling back to 3.8.1 will resolve this issue.
... View more
08-06-2021
12:56:PM
1 Kudo
I upgraded 3 psa devices this week from 9.1r11 to 9.1r12, and updated the ESAP package from 3.8.1 to 3.8.2 last night. Since the 3.8.2 update, no machine with Windows Defender have been able to pass the Host Checker (AV policy). rolling back to 3.8.1 fixes this problem. looking at the release notes for 3.8.2, PRS- 401804 is noted as resolved, it appears not to be.
... View more
10-05-2020
01:55:AM
Good, that means its not me.
... View more
- Tags:
- reply
09-30-2020
12:40:PM
It appears that if the logged in user doesn't have local admin rights, upgrading from 9.1.8.3143 to 9.1.8.3999 fails with the error "you do not have proper privileges to install this application". The upgrade from the previous version to 9.1.8.3143 did not cause any errors, as far as I know. With 3143 installed, and logged into windows 10 as a user with local administrative rights, the prompted upgrade to 3999 works just fine. Has anyone else seen this issue. Our current resolution is to reselect 9.1.8.3143 under Users -> Pulse Secure Client -> Components
... View more
07-17-2020
01:49:PM
That may have been your GPO admin adding a setting that tells chrome to add a 'save checkbox' to the dialog box. I've done that for a group that I manage so that they don't have the extra step every time they launch a rdp session from a bookmark.
... View more
07-26-2019
07:23:AM
They changed the default behavior of the Pulse client (but I don't recall which version). Formerly, the Pulse client would not disconnect if you were using remote desktop and disconnected from your remote desktop session, but now, when you disconnect the remote desktop session, the pulse client drops the tunnel. the 'logic' behind this is that there's no way for the Pulse client to determine if you've reconnect, or if a different use logs in. If you were to reconnect, then there wouldn't be any security issues, but if a different use logs in, they'd be able to use your existing tunnel because there's no ?simple? way in windows to limit connections via network interfaces to specific users. I think they should have implemented this so that you can only establish a connection if a single user is logged in,. also if a connection is active and that user disconnects, the tunnel /should/ remain active until 1) it times out or 2) any other user remote desktop session is activated. My solution to this is to use two machines like so: 1) from my desktop, i connect via rdp to pc1 2) from pc1, i rdp to pc2 3) from pc2, i use the pulse client to connect to a remote vpn. 4) if i disconnect the connection from my desktop to pc1, the connection from pc1 to pc2 remains active and thus my pulse secure session stays active until it times out.
... View more
03-06-2019
06:56:AM
(incorrect statement removed) What am I doing wrong? answer: reading.
... View more
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
