Skip to main content

We are tearing our hair out with this problem.



Some of our Macs (random, not always the same) are not checking in with the JSS on the 15 minute Check-in Frequency set under Computer Management. This means that when a policy is available it takes sometimes hours and even days for the policy to apply to all the Macs (currently around 40 as we're still in early stages of rollout).



Our network admins say that all the ports are open to APNS. What are some of the reasons why some Macs might not be checking in? We have verified that they are turned on, plugged in (wired not wireless) and not sleeping.

For us, the solution ended up being running:

sudo profiles renew -type enrollment

on each affected computer. But the root cause was us accidentally making the management account and the automatically created user account with the same name. 

 

For us, the solution ended up being running:

sudo profiles renew -type enrollment

on each affected computer. But the root cause was us accidentally making the management account and the automatically created user account with the same name. 

 


So you have to actually get to each user and manually do something? its not the end of the world, but these folks are all over the place.  

We did, which was rough. There are some other tools you could employ if your issue is different than ours. There's a connection healing tool that jamf support walked us through that may work for you that didn't work for us.

We see this consistently. It’s more or less impossible to get devices to consistently check-in according to the check-in policy, which makes remote administration (we aren’t a school, folks aren’t on the same network, devices are sometimes across the country) completely unusable.

We are moving off of JAMF at first opportunity.

For us, the solution ended up being running:

sudo profiles renew -type enrollment

on each affected computer. But the root cause was us accidentally making the management account and the automatically created user account with the same name. 

 


But the root cause was us accidentally making the management account and the automatically created user account with the same name. 

this causes an issue?  I'd love to know more about this, since I think we've been setup that way for years!  do you have a link I can chase or anything where I can learn more?

For us, the solution ended up being running:

sudo profiles renew -type enrollment

on each affected computer. But the root cause was us accidentally making the management account and the automatically created user account with the same name. 

 


Can you expand on that? You made your local admin account the same as the users account? Im confused on that wording. 

Can you expand on that? You made your local admin account the same as the users account? Im confused on that wording. 


sorry I misunderstood - fresh eyes now and reading this properly - we are NOT making local admin account the same as the users account.

Reply


Terms & ConditionsCookie settings