You can also launch Console with keyboard shortcuts CTL CMD + C . One reason you might want to do this is troubleshooting by monitoring the logs for the mdmclient process as you attempt to enroll the machine through DEP, tailing the Jamf log etc etc.
You could also enable debug logging in JAMF PRO, I had to deal with this 2 weeks ago and this what helped me.
Do you have an Ethernet dongle attached when enrolling on 10.15.0?
Through trial and error, I think I discovered the cause.
I am using a USB-C Ethernet dongle when enrolling a MacBook. I am speculating that the Mac could not pull down the activation record due to the MAC address being polled was that of the dongle’s.
If I enroll the MacBook minus any Ethernet dongle and strictly with Wi-Fi, I am able to get the Mac to pull down its activation record.
We are seeing the same issues? MBA's showing up as iMacs and the remote management either not showing up and or error out. But it seems to be mostly MBA's? Other models seem to be working fine. Fix for use is to wipe and nuke the drive and reinstall Catalina from recovery drive. Sometimes go into ABM find machine and re-enroll in ABM then reselect in Pre-Stage. The team here is working on it i'm just along for the ride..
We are seeing this exact same issue on new 2020 MacBook Air models. I have a support call open with both Apple and Jamf, but we haven't gotten anywhere yet. I'll update when and if we resolve it.
We are currently letting the initial enrolment fail, and then wipe/reinstall macOS and try again. Usually this works, but the odd Mac needs to try a third time.
Is that the only fix to this? I just had this happen with two brand new 16" MBP. I wiped/reinstalled Catalina and it worked fine after that.
Problem with this is we typically have them drop shipped from a reseller who preps them (runs through DEP setup). If they run into this issue they will definitely not wipe/reinstall every MBP to get DEP working.