- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-16-2021 10:03 PM
Our current version in clients is 5.2.7. Now I have activated 5.2.8 but clients doesn't upgrade. Our setting for upgrade is allow transparently. Client machines shows pop up that GlobalProtect agent upgrade is in progress please wait etc... but nothing happens.
Previous update to 5.2.7 couple of month ago went smoothly. This is first time this kind of behavior.
11-18-2021 08:36 AM
Figured out the problem for my environment. The agent download was failing (found by opening GP Agent -> Settings -> Troubleshooting -> Agent Logs)
Internal DNS records for our GP Portal were incorrect. Fixed them up so the portal was reachable from inside the network, then the upgrade immediately started working.
11-17-2021 03:08 PM
I get the same issue trying to upgrade to 5.2.8. Endpoints get a message about the upgrade in progress, but nothing ever actually happens. Are there some logs we can find to tell us what's going on?
11-17-2021 04:16 PM
I didn't get the same issue when I activated 5.2.8 from 5.2.7. However, several users failed to upgrade the GP client, so they followed the following KB. The typical uninstallation/installation GP client didn't work in this case.
Error: Failed to find PANGP virtual adapter interface when connecting to GlobalProtect
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm5eCAC&lang=en_US
Hope this helps!
11-17-2021 04:24 PM
I have macOS Catalina, and I ran into the same issue. So, it is not the issue in the KB article for Windows. Previous upgrades worked fine. For 5.2.8, I would get a popup, then nothing. I chose to download the software from the portal and manually upgrade. That process worked fine.
11-18-2021 08:36 AM
Figured out the problem for my environment. The agent download was failing (found by opening GP Agent -> Settings -> Troubleshooting -> Agent Logs)
Internal DNS records for our GP Portal were incorrect. Fixed them up so the portal was reachable from inside the network, then the upgrade immediately started working.
11-16-2023 12:26 PM
Did you use the internal portal IP address for DNS? We're using a loopback address and are having a similar issue and I'm wondering if it's a misconfigured DNS entry.
11-16-2023 12:32 PM
Hi @MikeSangray2019 ,
I run into a similar issue with many customers. After you connect via GP, your endpoint no longer uses an external DNS server. You need to create an internal DNS A record for your GP public IP address. Then the upgrade will work fine.
Thanks,
Tom
11-17-2023 09:47 AM
Thanks, Tom! This got it working for us.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!