Update: I am able to get Pulse Secure to connect now.  I restarted, so perhaps that was necessary to completely update the service.  However, the permission issues seems like something that the installer should be handling. ... View more

FYI, I tried:   sudo chown root:wheel /Library/LaunchDaemons/net.pulsesecure.AccessService.plist sudo chmod o-w /Library/LaunchDaemons/net.pulsesecure.AccessService.plist sudo launchctl load -w /Library/LaunchDaemons/net.pulsesecure.AccessService.plist   After which the Pulse Secure window suddenly showed the previous connections that I used to have...   Doesn't this mean the installer is incorrectly installing itself on macos 11.0.1?     Unfortunately, this doesn't seem to solve the problem, because now when I try to connect to one of my previous connections, I get a "waiting to connect" message, which includes "Details: Network Error" ... View more

sudo launchctl load -w /Library/LaunchDaemons/net.pulsesecure.AccessService.plist Password: /Library/LaunchDaemons/net.pulsesecure.AccessService.plist: Path had bad ownership/permissions Load failed: 122: Path had bad ownership/permissions   I just upgraded to macos 11.0.1.  Any ideas? ... View more

sudo launchctl load -w /Library/LaunchDaemons/net.pulsesecure.AccessService.plist Password: /Library/LaunchDaemons/net.pulsesecure.AccessService.plist: Path had bad ownership/permissions Load failed: 122: Path had bad ownership/permissions   Any ideas?  It stopped working just after I upgraded to macos 11.0.1 ... View more