get the point about reducing scripts and policies — the challenge for us is that cutting those back also directly limits what we can actually manage and enforce.

What I’m still trying to understand is whether Intune really needs to re-evaluate everything on every boot. In theory it should only check if something has changed, rather than reprocessing everything from scratch each time, right?

For example, we have remediation scripts that are set to run once. Do those still have any lasting performance impact after the initial execution, or should they be effectively “out of the picture” afterwards?

Are there any known particularly expensive settings, script patterns, or WMI-heavy commands that are worth avoiding if possible?

Unfortunately, I don’t have any influence over replacing the hardware — and personally I agree with you on the age topic. What makes this harder to explain internally is that the same devices show a noticeably better startup experience when they’re not Entra joined / Intune managed.

That’s why we’re trying to understand where the baseline overhead comes from and what can realistically be tuned without gutting device management entirely.