DEP Catalina install not pulling data

NealIV
Contributor

In testing, even though the Mac is checking in it is not pulling application, package receipts etc into jamf pro. Also the machine name isn't DEP - (Serial number) on the Mac. It supposed to report as L(Serial Number) back to jamf pro. This has always worked up until the Catalina Mac. See image.
957dcfdfad91444e8034f97a5b5fb99b

5 REPLIES 5

sdagley
Honored Contributor II

@NealIV What version of Jamf Pro are you running?

NealIV
Contributor

VERSION
10.19.0-t1580394015

sdagley
Honored Contributor II

@NealIV 10.19.0 is Catalina compatible, so that's not it.

Are you using SSL inspection on your network? If so, macOS Catalina changes the server used for the initial APNS communication to init.push.apple.com. If you don't follow changes to Apple's Use Apple products on enterprise networks KB article on what servers need to be on an exception list for SSL inspection you may have courier.push.apple.com as an exception. That works through macOS Mojave, but as of macOS Catalina you need to change it to .push.apple.com to accommodate that initial connection to init.push.apple.com.

NealIV
Contributor

I need to check that. Now ae are still on Prem (for now). When I move to jamf cloud will it fix it? Or it doesn't matter if it's on prem on in the cloud?

sdagley
Honored Contributor II

@NealIV It's the communication from the Mac being enrolled to Apple's servers, so it'll affect any Macs you're trying to enroll on-prem whether or not your JSS is on-prem or Jamf Cloud.