2 ms·
The issues you experienced are squarely on the shoulders of your Jamf admins. It doesn't have to suck, but it usually does because the people put in charge of
by xyzzy_plugh 5y ago
The issues you experienced are squarely on the shoulders of your Jamf admins.
It doesn't have to suck, but it usually does because the people put in charge of it are incompetent, or at best, semi-competent. Most self-respecting engineers run fast from this sort of thing.
- tehalex 5y agoHaving worked with JAMF's API... I don't like it, but yeah, this is not normal and something as to how your company is using JAMF. The people in charge of this are usually more of the IT than 'self respecting engineers'