- Pulse Secure Community
- :
- About caleb.bontrager
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
03-16-2020
01-13-2022
caleb.bontrager
Occasional Contributor
6
Posts
1
Kudos
0
Solutions
05-02-2021
05:47:PM
I'm dumb - dupe post AND, found that the "Pulse Secure Installer" via the downloads page includes these components, so should just be a matter of extracting the msi to get those individual components..
... View more
05-02-2021
05:47:PM
1 Kudo
I'm dumb - dupe post AND, found that the "Pulse Secure Installer" via the downloads page includes these components, so should just be a matter of extracting the msi to get those individual components..
... View more
05-02-2021
05:17:PM
Hello, We're testing the upgrade to PCS 9.1.R11.3 containing the code signing certificate fixes. In testing, it seems that after a client has uninstalled and reinstalled the new PAL and SetupClient components, the client is able to successfully connect to both PCS servers running 9.1R11.3 as well as prior version with older setupclient versions (i.e. our existing non-upgraded PCS instance). Based on this, I'd like to position our desktop folks to be able to script pushing the uninstallation, followed directly by installation of newer client components so that user impact is greatly reduced upon upgrade. But I need the setupclient packages to be able to give them to push out in advance. The PAL can be downloaded from the Pulse install for pushing out via SCCM or other tools. But I don't see where the SetupClients are available in the same way. Am I overlooking something or do we need to figure out a way to grab the setupclient install packages from the client during the web delivery process? And of course, the real prep this is for is to upgrade asap to 9.1R11.4 when it drops. I appreciate any insight.
... View more
05-02-2021
05:13:PM
Hello, We're testing the upgrade to PCS 9.1.R11.3 containing the code signing certificate fixes. In testing, it seems that after a client has uninstalled and reinstalled the new PAL and SetupClient components, the client is able to successfully connect to both PCS servers running 9.1R11.3 and prior version with older setupclient versions. I know the PAL is included for download and able to be distributed to clients via SCCM or other tools. But I don't see where the SetupClients are available in the same way. Am I overlooking something or do we need to figure out a way to grab the setupclient install packages from the client during the web delivery process? Bottom line, I'd like to position our EDL folks to be able to push out the uninstall, followed by installation of newer client components so that user impact is greatly reduced upon upgrade. But I need the setupclient packages to be able to give them to push out in advance. And of course, the real prep this is for is to upgrade asap to 9.1R11.4 when it drops.
... View more
05-19-2020
10:25:AM
Checking to see if anyone has had success in figuring this out. After enabling hostchecker on a realm, we're beginning to see this behavior on some Windows clients when logging in from the Web to the IVE. In what I've observed, if the Pulse client is closed, then the PSAL is able to launch the client and the L3 tunnel completes successfully. Until I log out of the PSA connection and attempt to log back in. However, if the connection is initiated directly from Pulse, the connection works every time - the issue only occurs if logging in via web browser that initiates the L3 connection with hostchecker enabled. Also of note, Windows Event Application log has an msiinstaller error coinciding with the failed login/connection attempt. The pair of messages is to the effect that the Pulse Secure Installer Service - Installation Failed, and "You do not have sufficient privileges to complete this installation for all users of the machine. Log on as administrator and then retry this installation." I've been able to reproduce this on test machines where I am the admin user, as well as testing on a non-domain endpoint with the same result. Just checking if there's any insight as I also work to open a ticket.
... View more
03-16-2020
05:23:AM
While Ansible does ordinarily use ssh for configuration management, it also can make use of REST api's to do config management - beginning with the generic uri module. There are a plethora of networking vendors that have built and publish Ansible modules for managing their devices via REST api - for example FortiOS - https://docs.ansible.com/ansible/latest/modules/fortios_vpn_ssl_settings_module.html#fortios-vpn-ssl-settings-module. Creating and publishing modules for managing PSA via the REST api is definitely something that Pulse should be looking at doing as well.
... View more
Latest Tags
No tags yet
© 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.
