"This computer is not managed."

@peter.caldwell We're using thin imaging so we're not touching the OS, but in our configuration we install a bunch of applications, a couple scripts, add an admin account, add a directory binding, add the management account and that's about it.

Should be noted that so far this is the only Mac this has happened to, we have 16 others in the JSS with no issues. We are running our imaging procedure on a different mac to test this theory.

@znilsson Out of curiosity, if you log into that machine and look at the system info, does it have a serial number? The only reason I ask is that I had very similar and it turned out the computer hadn't been properly searialized.

Not sure that's the issue but I figured I'd ask just in case.

@rdwhitt I don't have access to the machine right now but Casper Imaging did pull a serial number from the Mac and slugged it in to the name field, as per my prestage image configuration. But since Casper can't pull the serial number to add it to the JSS because it's unmanaged, I don't know if what it pulled to name it is the same number as what shows up in the system profile.

Working with JAMF support, we got it fixed on our end. Apparently there is a bug in the JSS 9.9 installer for Windows, in which a file or files are not installed, which causes any attempt to enroll Macs into the JSS, by any method, to fail and you're left with a kind of zombie Mac that is technically enrolled and it does check in to the JSS so the agent is running, but none of the policies or config profiles apply to it, and it shows as "unmanaged" in the JSS.

The solution for us was to re-run the JSS 9.9 installer for Windows and use the Maintenance option which did sort of a "reinstall lite" in place on the server, and that solved our problem. Once Tomcat came back up and everything was running, I was able to use a quickadd package on one test Mac, and do a Casper Imaging install via Netboot to two other test Macs, and all three of them successfully enrolled and were managed, with all appropriate policies and config profiles applying correctly.

As far as I know this issue should only affect organizations that are running their JSS on a Windows server, using version 9.9 of the JSS.

Can anyone confirm that this issue is fixed in 9.99? I'm seeing something remarkably like it, and if this isn't it I don't want to start making too much noise about it.