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