Globalprotect Agent for OSX - anyone else running into MAJOR UI issues?

[MydisplayNameis3]

Is anyone else experiencing poor UI issues of the Globalprotect agent for mac osx or even windows? The UI for Mac OSX is EXTREMELY difficult to navigate, let alone find the window itself sometimes as you can't alt-tab to it. Frequently the panel window is hidden behind others and the ONLY way I've found to find it is to click on the icon in menu bar and choose About. 
PS - we have provided feedback to our SE's. We're hoping the forum admins will give a heads up to the Globalprotect team to consider these suggestions.

PAN PRODUCT MANAGER FOR GLOBALPROTECT->> PLEASE HELP!!
Here's feedback direct from our end users:

• We've received non-stop employee complaints that the the agent for OSX and windows is non-intuitive, appears outdated compared to Juniper or Cisco, poorly implemented and even our engineers complain it's difficult to use.
• We're unable to get the client to pre-populate the portal address - it should be pre-populated by PAN prior to downloaded. Forcing us to give users a document describing them how to "setup" the agent after installing it. It should be very easy to pre-populate the portal but have yet to see PAN capable of doing so.
• to get status, users have to go to advanced then choose Show Panel and details.
• The troubleshooting tab is 100% useless as it lacks any diagnostics - forcing you, on a Mac, to go search for a log dump file (somewhere) whereas it should show the logs in the interface. Have you even seen Cisco Anyconnect's vpn client? It's amazing when compared to Globalprotect.
• It should be quit'able and re-openable.
• Ever since we rolled it out users have asked us to get rid of it and go back to Cisco Anyconnect. A great thought but we require the HIPS profiles thus we're forced to use Globalprotect agent. (sigh)
• You can't quit or close the agent, like you can on Juniper or Cisco Anyconnect.
• Everytime you boot your mac, the agent window pops up even though we've not enabled auto-logon.
• When you try upgrade, it downloads the upgrade to your desktop but doesn't execute or run it
• The status tab is useless - if your password is wrong it just says unable to connect. It should at least say credentials failed. We have to look on the PAN itself to find the real error message for users.
• the ability to add/save/edit multiple portal logins would be a great feature to have
• the help page is literally this graphic: (helpful, huh?)
  

[jmenon]

Thanks for the feedback. Who is the SE on your account ? I will reach out to him to schedule a feedback session between you and I , Product Manager for GlobalProtect. Feedbacks from customers is what gets us the input to continuously improve the product.

I will also encourage you to try the enhancements introduced in 6.0 release announced this week and will be available for you to download starting next week. Please refer to the what's new guide as well as the newly available most comprehensive admin guide for GlobalProtect.

There is content for default help now. This is totally customizable, you have the option to write the help specific to your environment and upload to the firewall for your users. we had also made a customizable doc available in the past  Using the GlobalProtect Agent for Windows (Customizable Version).

2.0 agent customization feature is how you would pre deploy portal address and other settings even prior to user downloading the agent.

Authentication failure message are displayed both in the settings panel as well pop up dialog. Typically you right click on the app menu and select connect if the configured connect method is on-demand and a pop up dialog is displayed to the user in case the authentication fails.

Agent pop up on system restart and upgrade trouble will be a considered a bug, please help us confirm and provide fix those by opening a support case so that we can gather details.

Typically you use single portal and multiple gateway , would like to learn the use case for multiple portal.

Different state of the app menu icon is an indicator of status; would like to learn the use case around why its not enough and what additional status you believe will be useful.

Troubleshooting logs are also available to the users via the system console app in the Mac , would like to learn the use case of duplicating it in the product UI as well.