unfortunately, the "best" is up to you for your users & your environment and how you want to handle the upgrade. the client is backward & forward compatible; for this particular set of issues, you may want to do the server first, as recommended by @Pulsar, and set the active pulse version as what you have installed in your user base currently and slowly rollout the client through SCCM for controlling the number of users that have the new client, so you can watch for any unexpected issues with connectivity. then, if a pilot group does not show issues, release it to all users through SCCM or enable automatic upgrade on the client and set the active client version to the most-current. does that help with trying to plan for it? alternately, you can reach out to your account team for professional services or deployment services engagement to get more enterprise-specific guidance ... View more

Below are the contact numbers for Pulse Secure.  However, you will need whoever manages the Pulse Applaince to open this ticket as they will have the serial number for the actual appliance.  Our customer care team will need to validate the support contract on that appliance and then can dispatch the ticket to our support team.   https://support.pulsesecure.net/support/support-contacts/   Thank you Craig ... View more

Hi Venki, Thanks for the details,    If the user needs to enter any details like OTP, then this is not supported. We understand it was working fine before, however, it was a bug and now it stands corrected. If, the user doesn't need to interact like entering OTP and if still the issue occurs, Please open a Support ticket as it needs detailed investigation along with certain set of logs.   Regards, Pulse Secure. ... View more

This needs a detailed diagnosis, please open a Support case with Pulse. ... View more