Evening all,   We just finished the upgrading the appliance and I wanted to document my steps.  We were able to upgrade the appliance, uninstall the apps, reinstall the new Pulse Secure Application Launcher without needing to elevate admin priveleges against multiple test devices.  I need to redact some information and I can't send any screenshots for compliance reasons but I hope this helps.   Backed up configuration/user files for out for node1 and node2 Backed up the user/event logs. Dumped these log files to speed up the install process. Disabled the “Enable web installation and automatic upgrade of Pulse Secure clients” (Maintenance -> System -> Options)  **Pulse highly recommended this and I think this is pretty critical** Upgraded node1 first, then node2 was automatically updated as usual. We created a message on the login page that pointed users to the UninstallPulseComponents_v2.exe provided by Pulse PRIOR to logging in. After logging in we clicked on the Terminal Services link and we were prompted to download the Pulse Secure Application Launcher (the screen with the big download button.) (At this point the tests we did none of these users were admins on the machine.) We downloaded and ran the installer and we were not prompted for UAC or admin credentials. Test accounts and users were able to then successfully login. We did have one finding for users who use the Pulse Secure application on a Chromebook.  The role we were testing on had Split Tunneling enabled but for some reason I could not perform nslookups for my PC name.  I could connect to it direct by IP but hostname look ups failed.  I removed Split Tunneling from this profile and then things worked correctly.  Thsi configuration was UNCHANGED prior to upgrading through and the split tunneling networks were properly defined.  Maybe something with our CB setup or CB in general but they are a small fraction of our populace.  Once I did that connectivity restored.   I think the BIG thing is to disable the web installation and automatic upgrade of Pulse Secure clients.  I am calling it a night though.  Good luck everyone.   ... View more

And your web based users had no interactions to worry about?  Interesting.  Guess I'll find out tonight.   ... View more

Hate to drum this up but you did NOT perform the underlined following on your appliances?   Please do not use the Pulse Desktop Client that is shipped with these PCS Builds. This fix doesn't need the Pulse Desktop clients to be updated. We strongly recommend disabling "Enable web installation and automatic upgrade of Pulse Secure clients" from the PCS server (Maintenance -> System -> Options). I'm prepping to send out the Uninstaller package to 500+ users and then we are manually touching the users who do not have admin rights to their machines.   If all you did was upgrade the appliance and no end user interaction then that is an ideal scenario but..it just doesn't make sense.  Could be the anxiety kicking in though. ... View more

Appears we are having a disconnect with what you said in this thread.  User intervention WILL be required.  500+ machines that are unable to connect back home are going to need us to locally connect.   General Guidelines to install the fix : The solution would involve upgrading the PCS server as well as clearing the older Pulse Secure components on the End-User devices Note - End-Users who do not have any Pulse Secure components already installed, can skip Step # 2. 2. The End User devices that have Pulse Secure components already installed would need to follow one of the two methods outlined below: Run the attached BAT Script (UninstallPSALAndPSC.bat). Note - This would need End-users to have admin privileges. Manually remove PSAL and Setup Client components, a. Navigate to Control Panel -> Programs and Features b Select “Pulse Application Launcher” c. Right Click and Uninstall. d. Select “Pulse Secure Setup Client” e. Right Click and Uninstall. 3. Once, Step # 2 is completed, the End-Users should be able to successfully connect to the new PCS version ... View more

Anyone think this is going to be a HotFix on the appliance side or is this going to require client side updates?   I have had zero success in finding a way to upgrade the software remotely when a user is not a local admin and with 500+ people this is going to be a nightmare. ... View more

I am receiving an error currently that "An unexpected error occured." then "Detected an internal error.  Please retry.  If the issue persists, contact your administrator."  This only occurs when connecting to the Terminal Service option.  I am able to HTML5 and use an RDP client over Pulse Secure tunneling however.   I am not enforcing host checking options though so this is still related?  Happened just at the same time. ... View more

I am also confused on this.  I am not enforcing host checking and I am unable to use the Terminal Services option that goes direct to my PC.  I can use the HTML and Pulse Secure VPN Tunneling option fine and RDP that way but not all my users have this option.  Running 9.1R9.1 (build 9701) ... View more