Forum Discussion
Solved
Autopilot - Hyper-V - Hardware Hash
Hello everyone and greetings from Portugal!
Can someone please help with this one?
I'm creating a lab for testing Autopilot but I'm getting a "problem".
When I create a second VM, that I don't want to use the Autopilot process, it start independently because it have the same hardware hash of the first machine.
Is there any workaround to avoid this?
Best regards,
Diogo Sousa
- So you only want to perform an aadjoin on the device? Just use an user without an intune license?
6 Replies
- uhhhh I have like 40 vms running in hyper-v ... some of them in autopilot in tenant 1, some of them in tenant 2 and some of them don't have their hardware hash (or what you want to call it ) uploaded to intune
- Humm not sure I've understood your answer but...my scenario is:
Hyper V with 2 VMs, 1 tenant. And when I login no VM2 it starts autopilot.are you 100% sure its autopilot? Not just the esp that always kicks in when configured? If you have configured company branding you should immediately notice the welcome to … your org message
