Forum Discussion
Solved
Autopilot - 1 Hyper-V - 2 Intune Tenants
Hello everyone and greeting from Portugal!
I think I described a similar scenario some time ago, but this is a little bit different.
I've an hyper-v with 1 VM. And 2 Intune in different tenants.
I need to test Autopilot for the 2 different tenants. Is it possible with the same VM? My idea was to remove the registered hardware hash from one tenant and register in the other tenant? Does this work?
In an other scenario, I think I've tested this but maybe I done something wrong. Can I've my hyper-v with 2 vms and each one using a different tenant? I believe not because of the hardware hash, but maybe I'm missing something.
Thanks in advance!
Diogo Sousa
- If you enroll the VM with a generalized Windows version then it would be no problem. I use the method that Michael Niehaus describes (updated VHDX files for eacht VM and register with get-windowsautopilot -online)
https://oofhours.com/2023/08/23/windows-autopilot-testing-with-vms/
5 Replies
- Hi Diogo,
Use 1 VM with multiple snapshots for each tenant you mean?
What doesn't work is the same hardware, so i guess a seperate disk could work? But if saving space is the reason, then it has no real point...
Some hardware is relevant for autopilot hash, see https://oofhours.com/2022/08/08/connect-the-dots-create-your-own-hashes/- In this case, I would like to have 2 VMs in same Hyper-V host.
One for a tenant, and the other one for the other tenant.- If you enroll the VM with a generalized Windows version then it would be no problem. I use the method that Michael Niehaus describes (updated VHDX files for eacht VM and register with get-windowsautopilot -online)
https://oofhours.com/2023/08/23/windows-autopilot-testing-with-vms/
- Treat the VMs as physical device. If it will work on a physical device then it will work on the VMs as well. Best way is to confirm is to test it.
