Part of the inconsistent results I got is also the fact that sometimes the VM would just fail to contact the MDM server after detecting the pre-stage, while on other runs it ended up being stuck at “Retrieving the activation record”… as said overal some very inconsistent behaviour. Sometimes it detected the Jamf Pro pre-stage but failed to contact the MDM server, sometimes it didn’t detect it at all and setup assistent acted like there was no prestage. But unfortunately I also ran into multiple unexpected and inconsistent results. I knew it works on Parallels Desktop 13, and while I was reading about people having issues getting it to work in version 14, I still gave it shot. Here is what I did, as well as the working configuration for Parallels Desktop 13 (confirmed on Version 13.3.2 (43368) with macOS 10.14.1)Ĭlick here for the Tutorial on how to do this on Parallels 13. The “bad” news is: I haven’t succeeded in getting it to work with Parallels Desktop 14. – See update above. The good news is: it still works on Parallels Desktop 13, even with macOS Mojave. While I personally use VMWare, in combination with my ESXI homelab, I promised to post the workflow for “Automated MDM Enrolment and Parallels Desktop” as well. In my previous post I discussed the steps to create a VMware Fusion virtual machine, which is behaving like your “automated MDM Enrolment” test device (previously known as “DEP”). 'Resolves an issue with the Apple DEP (Device Enrollment Program) not working in a macOS virtual machine'ĬONFIRMED: Works perfectly in Parallels 14.1

UPDATE 20th of November: Parallels released an update for version 14

Parallels for mac os mohave