Skip to main content

Hello,
on Friday we update our Jamf to the 10.47 version and this morning we got an issue that any newly assigned computer during PreStage with Enrolment customization will be pushed to Site: None.

So, in PreStage enrollments settings, Enrollment Site is defined and the Automatically assign new device option is enabled. This is all working fine.

But as soon as we enable Enrollment Customization Configuration, which is a simple text with a button "Next", the computer will always be pushed to Site: None in Jamf.
We tried to select the Site in the Enrollment customization profile, but whatever you select result is the same, Site: None.

What I noticed, if is Prestage Enrollment Customization enabled, the computer will be assigned to the proper site at the beginning, but as soon as the Remote Management window is done (all config profiles installed) will be removed from that site. This happens only if is Enrollment Customization Configuration enabled in PreStage enrollment.

 

Does anyone have the same issue or any advice on how to solve this?

We’re having the exact same issue.  I will be opening a ticket with Jamf tomorrow.

Same issue here also!

Exact same issue, opened a ticket, no replies yet.

This is from our Jamf engineer:

 

"Just wanted to drop in with some new information on this. Turns out that the behavior we're seeing here is a product issue (PI112050 for your records). Unfortunately, the only workaround for this is to disable the enrollment customization. The good news is that this is slated to be fixed in 10.48, which is just around the corner."

We're seeing this issue on prestages that do not have any Enrollment Customizations on them.

We're also having this issue, regardless of enrollment customizations. Also having issues that triggers aren't working even when changing the site for the device. This has completely broken new deployments for us and is a pretty major bug.

Same issue here. Jamf support provided some script to change the site assignment, but this also doesn't really work during the enrollment stage (when we need it to be assigned).

Same error here. We've got a significant deploy on-hold until it's fixed.

Looks like the Jamf Update that was released doesn't mention this error in the Resolved Issues section.  Unclear if it was quietly fixed or if we'll be dealing with this for at least another month.

Has anyone updated to 10.48 yet and confirmed if the issue is fixed?

Initial test from our Sandbox looks good.

Updated to 10.48 in sandbox which include multiple sites...

Enrolled computer via DEP with a Prestage Customization for Directory Credentials (from our Coud IdP)...

It assigned user/location correctly and enrolled the computer into the correct site assigned by the Prestage. 

Seeing the same issue with PreStage site assignment/enrollment customization. In testing it gets assigned, and then something kicks it out and reverts the site back to "none". 

Our production Jamf is still on 10.37.0.

We'll see what happens on 10.38...

Reply


Terms & ConditionsCookie settings