Posted on 12-18-2018 03:15 AM
I make a lot of Fusion VMs for testing. I would like to have JAMF already installed to save having to Recon them each time. JAMF Pro sees the clone as the same machine each time. Is there a way to force JAMF Pro to see this as a new machine.
Thanks in advance.
Posted on 12-18-2018 03:17 AM
you could have a quickadd.pkg and a startup script to install it on first boot. You would just need to approve UAMDM afterwards.
Other than DEP, any other method I can think of would still require you to approve UAMDM, so I'd just go with the simplest option.
Posted on 12-19-2018 10:02 AM
Thanks David. That didn't work for me. I have raised a case and will report back once I have the answer.
Posted on 12-23-2018 03:07 AM
I cracked it in the end. These were the steps.
I removed the .nvram from the machine I used as a template for my new machines. That also worked and means I don't have to remember to do it each time.
Posted on 12-13-2021 04:42 PM
I was having the above issue when cloning/copying VMs in esxi.
So far this only works for me before I install the jamf pkg.
From the VM you want to install jamf on open a terminal and
run: sudo nvram -d platform-uuid
and reboot the device. This should give a new hardware ID.
use: ioreg -rd1 -c IOPlatformExpertDevice | grep IOPlatformUUID
to check before running the above command and rebooting and after the reboot to verify the UUID changed.
So far this has resulted in over 10 clones/copied VMs being able to properly have unique ID's in jamf pro/protect.