![]() ![]() And yes, I know that I have to quit VMWare inbetween each change (or double-click the VMBundle) to force the changes to take effect. I'd have to look at my notes, but I believe it was the serialNumber settings worked/booted (verified serial number in "About this Mac") but then that test failed MDM enrollment.Īnyone figured out what's changed yet? I really need to test OS upgrades from 10.13 to 10.14, and I don't want to go back to standing up a real machine every time I test after enjoying the last several months with virtualized Macs that enroll in JAMF. ![]() SerialNumber = "INSERT-YOUR-OWN-FAKE-SERIAL-HERE"īut now for some reason, any combination of the above will either cause 10.13.6 VMs on a 10.14.5 Host to kernel panic (with CPU usage maxed out at the number of CPUs assigned to the VM) or fail MDM enrollment similarly to an unmodified VM. ![]() This is working for me under VMWare Fusion 11.1 with 10.14.5 VMs: Once it is all loaded, Click the Apple icon > About this MacĬheck the 'Serial Number (System)' and 'Model Identifier' have been picked up. MacBookPro12,1 = MacBook Pro Retina 13-inch 2015, MacBookPro14,2 = MacBook Pro 13-inch 2017, This changes 'Show in Finder' to 'Open config in editor window'Īdd the 2 lines above to the bottom of the file: SerialNumber = Use your physical macOS Serial number and increment the last numeric digit This can be fix by adding the following TWO lines into the VMX file for the VM: MDM Profiles not being able to install macOS profiles because it can't tell if its a Mac, and stops enrolment because the serial number isn't correct. VMware Fusion doesn't create the serial number and model number correctly for Mac VMs. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |