Skip to main content

Hey,



I am trying to setup a virtual mac environment for testing. I have a MacPro 6,1 and I'm looking to run A MacOS Mojave 10.14 off it.



What is the process to get this up and running?



I have ESXi 6.5 installed on the MacPro, the environment is all setup but when I try to build a VM with Mojave 10.14 and try binding it to JAMF the MDM profile fails to create and I think it has to do with the Mojave VM not being registered to Apple. The binding process only works for physical macs with serial numbers registered to Apple. Is there a specific way to bind 10.14 OS?



I have tested it with previous MacOS versions and I was able to bind, it seems the 10.14 OS has a new bind process.



Also whats the EULA around this? Is the way I am doing this legit or do I require other licencing?



Any help will be greatly appreciated
Thanks

you'll have to spoof the VM so Jamf thinks its a real device, you can do this by specifying the Mac model and a real serial number within the VMX config (just use the details from your physical MacPro hardware. As long as the MAC address and sharing name are different, Jamf and AD will be happy enrolling it with the same serial number.



Theres plenty of articles created by other admins on this subject



example:
https://travellingtechguy.eu/vmware-dep/

If you want to do any DEP testing your VM will have to have a legit serial number that is part of your DEP collection. I use the serial number and model from an older Macbook Pro that was DNR'd. Here is the article I used to get up and running.



https://www.modtitan.com/2018/03/tip-for-testing-new-jamf-pro-103.html

Thanks Guys, @garybidwell @m.donovan



I did spoof the HW.model in a previous attempt but never assigned a "real" serial number. Ill try the MacPro serial and see how that goes.



In previous attempts I did notice that when I extract the enrollment package that we use it is saying mobile.enrollconfig. When this is run, it brings me to the Casper enrollment webpage. Perhaps this package is causing a problem too, maybe its trying to register the mac VM as a mobile device rather than a Computer. However this was the same package used to bind older version of mac os and it was working for those so maybe not, just thought I'd put it out there :)

Terms & ConditionsCookie settings