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...
- 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/
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/
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/- Just for future memory of someone that reads this thread, I believe I was just not thinking right about what I wanted to do.
It...simply works, having 2 differente VMs in Hyper-V, going through the OOBE and use the "get-windowsautopilot -online" method. When asked for credentials just point to the tenant you want to register the VM.
Thank you all for the help.
