Does anyone know which services/tasks InTune enrollment depends on?

[Popperoni]

First post here!

I would say I have my sea legs when working with NTLite. I've made a pretty solid OS for personal use that kept all dependencies I needed and it runs flawlessly, I am in love with it and in love with the NTLite project in general.

I showed it to my boss here at work and he was intrigued by the program as well, so we went ahead and got a business license for here to make specially crafted Windows 10/11 images, so far so good, but I am having one issue that really throws a wrench in our plans.

We currently operate in a hybrid environment. It will be like this for the next couple of years I'd imagine. We use Intune and Defender online for our endpoint management, so when we join a new device to our domain, it registers the device in Entra, and enrolls the devices into Intune, Defender, etc.

It appears with the research I have done, that I am still missing dependencies that would enroll the device as expected.

So before I start to handpick each service/dependency and make 40+ ISOs to figure it out, I am wondering if anyone else has come across this issue in their enterprise environment, and was able to figure out the components that need to stay put when cleaning the image.

Any help would be greatly appreciated!

 

[garlin]

Enrollment for InTune clients is normally done by either a Provisioning Package (created by Windows Configuration Designer) or AutoPilot device enrollment.

Enrollment with provisioning packages

From Windows Configuration Designer (WCD), you would create a provisioning package with a bulk enrollment token. Add the new .ppkg file as an Update file to your image. This is straightforward, but the drawback is the bulk token expires after a few months. Your install image would have be periodically refreshed with a replacement .ppkg.

Windows Autopilot

With AutoPilot, register your tenant devices and during normal OOBE, networked devices should be "captured" into the AutoPilot workflow.

NTLite is "unaware" of MDM or MDT management solutions, as it's focused on ISO-based deployments. But as long as you don't remove or disable any OOBE, Autopilot, AAD or Connected Device Platform features from your image, it will behave as MS intended.

If you have a working preset, attach it here (after removing any user passwords or identifying data) and I can do a quick review.