Azure VM + Intune Autopilot
-
@manny2375 I think that that step is just for testing. Have you tested without doing the reset?
-
You're using a VM you created on Azure to join with Autopilot?
If you are resetting the VM from inside itself - I suppose it could hold onto the same hardware IDs, etc that Azure assigned the VM in the first place, but perhaps not.
If your goal is to have Azure based VM's be part of your Autopilot, there might be other settings you have to make to make the VMs more immutable.
If your goal is to do this mainly to new laptops/desktops - then try a VM on a local platform instead of inside Azure.
In my demo environment, I have windows 10 enterprise virtual machine with latest windows updates. Let’s see how we can enroll it to Azure Intune with Autopilot.
He says he's using a virtual machine for his demo, but doesn't say what platform that VM is on.
-
(@dashrender (Apparently you have to reset the vm to give the out of box experience like sysprep. I am not sure if I have to reset as most documentation says that you must but I not quite sure. @scottalanmiller ) and yes my goal is to have Azure based VM's part of Autopilot. The platform he is using on the demo is hyper-v. )
-
@scottalanmiller I think you are supposed to per most documentation on the internet.
-
@manny2375 said in Azure VM + Intune Autopilot:
@scottalanmiller I think you are supposed to per most documentation on the internet.
It's an assumption, but there's a big difference between it being required to work or just an assumption of the script writer that it is for a machine without important data on it.
-
From what I gather - the reset is only there because he only wants to use that one VM for everything - i.e. the setup, gathering of the machine information, etc.
Then to show it will "autopilot" into your Azure AD account - you reset it, go through setup and tada - it's joined.
You could have just as easily gotten machine information for another VM that you hadn't installed Windows on yet, and had it 'tada' join AAD.
-
The issue is that the only way to access the Win10 VM in Azure is via RDP. So when you wipe it, you wipe the ability to reconnect to the VM to do anything at all (I assume). This has nothing to do with Intune.
I've been managing Intune a few years and never have I wanted to test on an Azure VM. Do it locally on your device via Hyper-V or whatever you want to use. You can grab the hash of the VM and import it into Intune Autopilot before you even install Win10 on the VM. So by the time install is done, you're ready to rock and roll.
-
After the install, take a checkpoint.
-
@obsolesce thanks I know this method works unfortunately this specific client doesn’t want anything onpremise other than networking equipment and thin clients. The autopilot feature would have been nice on azure vm though.
-
@manny2375 said in Azure VM + Intune Autopilot:
@obsolesce thanks I know this method works unfortunately this specific client doesn’t want anything onpremise other than networking equipment and thin clients. The autopilot feature would have been nice on azure vm though.
Can you create Azure VMs before installing Win10 into the VM? if so, the same thing @Obsolesce said should work.
The rest in the instructions were just for doing setup AND testing with the single VM. If you can't get the hash of the new VM, well, then ... good luck.
-
@manny2375 said in Azure VM + Intune Autopilot:
@obsolesce thanks I know this method works unfortunately this specific client doesn’t want anything onpremise other than networking equipment and thin clients. The autopilot feature would have been nice on azure vm though.
Everything you are trying to do Microsoft is telling you not to do.
Read the last part especially:
