Description: 1/2 the time that I need a user to Self enroll, due to having a non pre-stage enrolled computer, or failling to enroll properly before assignment, I'll have them self enroll, and then they'll show up in Jamf, but without much of the usual data: Check in, inventory, Policies, OS. This is mostly a case with some of my most difficult users, a team of devs I have overseas and somehow it's turned out to be the hardest ones to get responses or help from - but I've self enrolled a computer many times before and it's not like it asks you for permissions that someone could decline or anything. It just installs the profile. So why do some self installed enrollment profiles give me full enrollment and accept application deployments and policies, but some do not? I've tried to have a few of these people do a Jamf Recon before, a Jamf Check, but nothing fixes it except a full computer reset. Is this the only way to correct this? Is there something I can do to prepare an already-deployed computer to accept the enrollment properly?
Jamf self enrolled computers not showing all data
+3
+26When you allow BYOD you allow a lot of variables. It could be any number of things causing problems from previously installed security clients, network configurations and so on.
My suggestions is to get the Jamf logs off one of the devices and dig through looking for communication or access issues. Any access issues would be admin related not PPPC related.
+3When you allow BYOD you allow a lot of variables. It could be any number of things causing problems from previously installed security clients, network configurations and so on.
My suggestions is to get the Jamf logs off one of the devices and dig through looking for communication or access issues. Any access issues would be admin related not PPPC related.
If it hasn't installed. Does the computer need to have the management profile removed and reinstalled?
+26If it hasn't installed. Does the computer need to have the management profile removed and reinstalled?
If the Jamf binary is installed, which it looks to be as you can run recon (assuming that recon is finished). I would no suggest removing and readding the MDM profile unless you are trying to reinstall the Jamf Framework.
Check the jamf logs on the device, and the jamf logs on the jamf server as those should tell you what is going on. If you need more direction, you probably want to open a ticket with Jamf. However, my guess is your problems are security posture and/or network related.
Jamf Check will check most network ports/hosts, but it has not been updated in a year and may not be current. Jamf Check also cannot check device configuration issues like a security client preventing something specific from happening.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.