Skip to main content
Question

Computers enrolled but not pulling configuration profiles or software after...

  • December 18, 2020
  • 5 replies
  • 125 views

Forum|alt.badge.img+6

I have had this happen a few times in the past month but a computer will get enrolled, installed the MDM profile successfully, and show up in JAMF Pro but will be under the serial number rather than the hostname like it should. Also, all profiles and software to be pushed to the device will be pending forever. The JAMF command doesn't install on Terminal either. I'm not sure what is holding the machine back from receiving everything else from our server. The machine is connected to the VPN and has worked plenty of times in the past.... Any help would be greatly appreciated!

5 replies

Forum|alt.badge.img+6
  • Contributor
  • December 21, 2020

I would take a look at the "Managed:" attribute/field in the general inventory section. I have seen this before and had to manually add the management account for everything to kick-off properly. If you have a randomized management account password, this will be a problem, as you will be required to add the management account password to set the "managed by" attribute.


Forum|alt.badge.img+11
  • Contributor
  • December 23, 2020

Kburns what if you don’t have a randomized password on your management account? We are running into a similar situation with new computers. We create a management account in our PreStage that does not have a randomized account


Forum|alt.badge.img+4
  • Contributor
  • January 5, 2021

We've started having this issue over the past month as well. We also don't use a randomized account. It's not every computer but it's often enough to be annoying. We've just started installing our quickadd.pkg when it happens because that will kickstart the rest of the process.


Forum|alt.badge.img+3
  • New Contributor
  • February 10, 2022

Hello!

Did you ever find a resolution to your issue?


sgreilick
Forum|alt.badge.img+3
  • New Contributor
  • October 25, 2024

Still being haunted by laptops that were deployed with this bug. Had many support calls with jamf, and the result is always that the machine needs to be wiped. 
Hopefully, someday, there will be a workaround.