Worked with Jamf as we were seeing this as well, and found that it was
due to 2 computers in our fleet that were assigned to invalid user
objects. If you are seeing this and are not on Jamf 10.21 yet, it might
be related to PI-008061. Jamf gave us a ...
