GlobalProtect App Dynamic Configuration misses information for 'show-system-tray-notifications'

[HW-ChrisME]

Problems came with the update from 8.0.x to 8.1.13.

This workaround worked for me today.

[RichUpshaw]

Just a bit more insight into this issue.  3 portals were showing the message so I wanted to see what change the recommended solution in this thread was making.

Portal 1 - Went to agent settings, clicked ok and noticed the commit link went blue.

It appears that the xml was not in the correct order and this "OK" click rearranges it.

[spellm]

I had the same issue come up today, and the previous fix worked.  just going in and opening each agent configuration and clicking ok for all of them and then comitting fixed it. 

[ice-quake]

(4/4/2020) Beginning with Applications and Threats content release version 8252, the dynamic configuration for System Tray Notification in the GlobalProtect app is removed (this option was deprecated starting in GlobalProtect app 4.1). You should expect to see a commit warning message ("GlobalProtect App Dynamic Configuration misses information for 'show-system-tray-notifications'") after you update to this or a later content release version. To permanently dismiss this warning message when it first appears, run the following CLI command in configuration mode:
delete global-protect global-protect-portal "<portal name>" client-config configs "<agent-config-name>" gp-app-config config show-system-tray-notifications

[nhinman]

Did not work for us.  We are on 8.1.13.  3020 HA pair.

[mark.naumowicz]

Just to qualify, what specifically worked for me, was the following;

Open each Portal Configuration>Network tab>GlobalProtect>Portals>click on each Porta>click on Agent>open the Agent listed under Configs>from the Configs window click on OK, then click OK to close the Portal Configuration screen>Commit changes to device.

Hope this helps someone.

[shawnhafen]

This solution seemed to do the trick for me on the 220, will try this on the 5050s as well. thanks!

[NateNewman]

We were able to resolve this by performing a content update and then committing.

[emre.ozel]

Do not worry, you can follow the link below for the solution:

Yes, the solution is that simple

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PPUTCA4 

[MP18]

Seems PA have this KB now for  how to fix this issue from CLI and GUI

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PPUTCA4