Forum Discussion

Biggamal's avatar
Biggamal
Copper Contributor
Apr 02, 2025

Required Apps assigned to dynamic group are being skipped during pre-provisioning?

I have a few dynamic groups based on a group tag that gets assigned to the device during Intune enrollment. Each of those groups have a different set of applications that are installed on them. One of those dynamic groups just doesn't want to detect the required applications. There are supposed to be 5 apps. During pre-provisioning, it just jumps straight to the reseal page.

 

  • If I let the device sit at the ESP page, the apps are installed in the background as if they aren't being tracked.
  • If I quickly seal the machine before other apps are installed and unseal, it works like normal (tracking each of the apps and installing them). 

I can confirm the following:

  • The device is in the proper dynamic group
  • The Autopilot deployment profile and ESP settings are correct
  • All of the applications are Win32 packages and install successfully during ESP
  • This same setup works with my other dynamic groups fine. And it has worked previously with the trouble group before. I didn't change anything

I tried:

  • Removing and re-registering the device

I'm about to delete and recreate the dynamic group or try to create a static group and see if I get the same results. Everything looks fine and I haven't been able to find something in the logs that points to why it doesn't see the apps as required. Again, if I let it sit, the apps install in the background fine. It's just baffling since my other dynamic groups work fine.

 

Has anyone seen something similar?

4 Replies

  • Biggamal's avatar
    Biggamal
    Copper Contributor

    Now it's happening to the static group I just created.

     

    I sent the wipe command to the device in Intune and watched it wipe. It got to the OOBE page and now it's showing the same behavior of the dynamic group.

  • Hy, based on your description, is very strange what is happening, do you have any kind of filter on these applications, this could be a problem. The filters with assignments targeting the dynamics group could be causing this, as from my analysis they are evaluated very late.

    Good luck!

    • Biggamal's avatar
      Biggamal
      Copper Contributor

      Nope. No filters or anything like that. 

      I set up the static group just like I did the dynamic group and it worked first try. 

      I put in a ticket with MS but the juice might not be worth the squeeze since this group is basically my testing config and it’ll probably less than 5 machines in this group at a time. 

  • Biggamal's avatar
    Biggamal
    Copper Contributor

    Sucks but creating a static group and assigning all of the apps allowed it to work as normal

Resources