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.
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..