![]() ![]() Unlike some of the instructions I saw for Fusion, I was not able to change the settings of a pre-existing Parallels VM to make it into a DEP-enrolled VM. The key for this flag is: ="DEP_SERIAL_NUMBER" Creating the VM You can also set the Serial Number via a boot flag, similar to setting the hardware model. The “SerialNumber” key is within the “General” key. Right-click the VM and choose “Show Package Contents” and then open the config.pvs file into your desired text editor. This file is located within the VM, so you have to find the VM location (normally under ~/Parallels/VM_NAME.pvm/). Unlike the Hardware Model, you can set the Serial Number in the config.pvs file. The key for this flag is: devices.mac_hw_model="MODEL_GOES_HERE"Īn example of this would be: devices.mac_hw_model="MacBookPro14,2" Setting the Device Serial Number The config.pvs method ![]() In order to set the hardware model, we have to set a “boot flag” in the VM’s settings. Setting the Device Hardware ModelĪ Parallels’ VM config file is slightly different than VMware Fusion’s, and we aren’t able to set the hardware model in the config.pvs file like you can in Fusion’s. To jump straight to the instructions, see the Creating the VM. After about the 10th wipe, and literally a full day of (barely) testing, we came to the conclusion:īased on a few guides I found online, and particularly this straightforward one by Ross Derewianko, I realized it should be quite easy, just set the VM’s Serial Number and Hardware Model. But I’d be lying to say that I knew how to create a DEP VM, and thus we were using a physical device and just wiping it… repeatedly. I knew other admins tested DEP with VMs as I’d seen chatter about it on Twitter and the MacAdmins Slack. We have just recently started acquiring DEP-enrolled Macs, and with that, wanted to put to test our planned workflow for provisioning a new machine. Since I don’t have a license for that, but have Parallels at my disposal, that’s what we had to make work. ![]() Most admins I’ve seen, or guides I’ve found, use VMware Fusion for their macOS VM testing. The other thing that Parallels (or really the community) is lacking is guides and tools for MacAdmin tasks using Parallels. Overall this is fine, but I have found Parallels struggles a bit more with testing things like preboot stuff, such as FileVault. Not sure who made the decision, but at some point in the past, my org decided to standardize on Parallels Desktop instead of VMware Fusion. ![]()
0 Comments
Leave a Reply. |