search

MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
628 stars 282 forks source link

Unable to use MDM in non domain task sequence. #309

Open connorwilliams-aps opened 3 years ago

connorwilliams-aps commented 3 years ago

I am trying to get MDM working in a non domain task sequence. I have it working fine in my task sequence for domain joined computers, but my Intune Image with no comanage is not working. If I try to use the Configure Network step as a workgroup, or not use that step at all, it errors out. Is there some way to configure my task for MDM in a situation like this?

I guess my real question is what is so important about the Apply Network Settings step? I would think as long as the MDMUsername and MDMpassword variables are set prior to the script running, that should let it go through.

Thanks

merlinfrombelgium commented 3 years ago

HI @connorwilliams-aps ,

I think you have a slight misconception on the Apply Network Settings step. It, along with the Apply Windows Settings step, provide the Windows Setup Answer file (unattend file) with required information. They are critical in the Windows setup process.

However, this has nothing to do with the MDM script. You mention you don't have co-management enabled, which also isn't required. Do you have the Cloud Management Gateway setup though? Please refer to Step 3 of the documentation to enable support for your scenario. https://msendpointmgr.com/modern-driver-management/#tab-step3

connorwilliams-aps commented 3 years ago

Thats what i thought. I was mainly needing clarification on this step as I was following the guidance from the website. I dont know if that means the guidance on the website needs to be updated.

For the BareMetal deployment type, make sure that the Invoke-CMApplyDriverPackage.ps1 script is executed during the WinPE phase of the deployment inbetween the Apply Network Settings and Setup Windows and Configuration Manager steps.

In my case I am not using an unattend file as I am using the reformat and replace json method for autopilot deployment. I have a CMG, but it is not applicable for this use case.

I did discover that the reason my deployment was not working was the package was formatted incorrectly. I made a custom package, and the Operating system dropdown does not include 20H2, it had 2009 in its place, which is not an acceptable version in version 4.1.0. I am going to make an issue report on that repo to inform them of that issue.