Still, now that we have the payload, we reached out to Palo Alto once again for documentation on how to configure their stuff, and I feel bad for the engineer, who was very helpful, even though he ended up finding this same article.
Until this weekend when we upgraded from Jamf Pro 10.13.1 to 10.22.1 (yeah, I know). So Moving to 5.1.4-45 was supposed to fix this issue, except that at the time our version of Jamf didn't support the System Extension payload and there was little or very hard to find documentation for Mac on Palo Alto's site.
One user got this from his ISP (COX Communications) along with his system warning him of his apps running out of memory. Microsoft confirmed that they use Webkit in their apps, Apple said, hey we'd love to help (and I don't know what behind the scenes things might be happening, but there is no partnership that I know of between Palo Alto and Apple, so its a crapshoot?) We opened a case with Palo Alto, Microsoft, and Apple. I imagine that most users will just bypass autosave and save locally, which defeats the purpose of having OneDrive. Some days it was impossible to work, so I was able to disable VPN, but for end users, it's set to be always on. If the Gateway was changed or the GPCS was refreshed then the behavior briefly went away until the Gateway reconnected. We started having issues with 5.0.8-4 and Catalina where any O365 traffic was having issues with Autosave (Word, Excel, PPT), syncing with OneDrive, Sharepoint (sites not loading), websites not loading completely, and Teams not sending messages.
0 kommentar(er)
