![]() However, in past months, it now seems that due to security changes in macOS, we can no longer silently uninstall the AMP client. Then I'd circle back with another Jamf policy to force install AMP, and the machine would be back in working order with zero faults. pkg that's included in AMP's application folder, or manually removing it via Cisco's documentation. So in years past, I could accomplish this fault-clearing process silently & without my desktop support guys visiting machines simply by running and/or pushing the AMP uninstaller. They don't apply retroactively, but they're ready to go & work fine with a full reinstallation of AMP. ![]() ![]() Uninstalling/reinstalling typically clears these up quickly, as these items they're supposedly faulting for are approved with our aforementioned Jamf profiles. ![]() Inevitably, due to bugs or interruptions or whatever quirk of the day, we wind up with some small number of devices with faults due to "lacking" disk access or extensions, or extensions not being loaded. We pre-approve disk access and extensions with Jamf config profiles for silent AMP endpoint client installations on our macOS devices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |