Word on the street is the content team is working on resolving the issue, I would expect a fix in the next 24 hours.
Also its always worth setting a delay on the download/install just to protect yourselves against this sort of issue. We set a 24 defer period on our estate. Saved us a few times
We ran into the same issues with content 729. Rolling back to 727 resolved our issues.
I'm thinking that delaying it by 24 hours sounds like a good idea. I saw a post above stating that they waiting 72 hours inbetween updates.
By waiting to long it seems we run into a chicken and the egg scenario. What are the dangers where Threats and App-ID are not updated? I assume there could be a window where new Vulnerabilities may not be addressed or changes by the vendors for App-ID may not be properly identified correctly by Policy rules.
We also had this problem and committed an Any on the Service for AD to work. We were about to test what the issue was when we saw the PA update on 729. We are reverting to 727 and deleted 729.
Written by Edward Millington
Please refer to the following Palo Alto Networks Customer Advisory available at:
Our Palo partner suggested a 72 hour delay on content updates. Interestingly you don't seem to be able to configure a delay in Panorama only on the devices themselves.
FYI on panorama 7.x.x and above I think this option is available. It may be available prior to that release but I cannot confirm,.
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!