I followed the documentation to migrate the old Windows Secure Application Manager and Network Connect over to the Pulse Secure Application Manager. All devices seem to get the deployment without issue, but some it auto launches as expected for some and not for others in the same role. I assume this is nothing on the appliance but possibly something on the endpoint, but not certain what would possibly prevent that. They are all Corporate Managed Devices and deployed from the same Image running Windows 10. We are running 9.0R6.0 on a pair of PSA7000 Appliances.
Is it not auto-launching after web portal login or desktop login?
After web portal logon only, but not for all, some users it works as expected. Not certain if possibly there is a come setting or level of PC access that would prevent it from working consistently. For my test account it worked as expected so hard to troubleshoot the issue.
Do you see any errors in the browser developer tools like Console, Network sections which capturing the behavior? This would be possibly tell if the browser is not honoring the auto-launch redirect sent by the VPN server.