Forum Discussion

Jamie_McNamara's avatar
Jamie_McNamara
Copper Contributor
May 30, 2022

Enterprise Mgmt " Scheduled Task's Missing"

Looking for some assistance regarding the 'PushLaunch' & 'PushRenewal' tasks.   For some reason, both of these task's seem to disappear from our client machines. All our devices are Hybrid AAD Joi...
Intune
Mobile Device Management (MDM)
Jamie_McNamara's avatar
Jamie_McNamara
Copper Contributor
May 30, 2022

Jamie_McNamara Rudy_Ooms_MVP NielsScheffers 

 

I would have expected it to be present as well, it's not hidden, just missing.

 

Can confirm that WNS is running and always has been.


That was my next port of call, add a device to an OU where no GPO's are applied and apply them one at a time to see what the cause is.

 

I've looked into our AV and there is nothing logged here to indicate that it is the culprit.

 

I just wanted to check if this behaviour is expected or someone knows what the potential cause could be before I head down the manual GPO route.

 

To confirm, the only tasks missing are the 'PushLaunch' & 'PushRenewal'

    • Jamie_McNamara's avatar
      Jamie_McNamara
      Copper Contributor
      May 30, 2022

      It is & valid until 2023, Device can still sync to Intune via the sync button under school & work accounts. and updates in the dashboard.

      Waiting to see if the sync function initiated from Intune updates or not.

       

      Edit: Sync from Intune portal doesn't seem to work, I'm going to assume that is due to these task's missing.

       

      Sync initiated from the device works fine, updates last check-in on the dashboard.

      • NielsScheffers's avatar
        NielsScheffers
        Iron Contributor
        May 30, 2022

        Jamie_McNamara That's a correct assumption. The "PushLaunch"-task is executed when the Sync is pushed from Intune. It calls "deviceenroller.exe" with some parameters, which then starts the "Schedule to run OMADMClient by client"-task, which then starts "omadmclient.exe" with some parameters. 

         

        Unfortunately, I haven't gotten very far in troubleshooting this behavior (except that I've now accidentally deleted the task on my own machine, in stead of my VM :facepalm:). I did notice a difference between these tasks and all the other tasks in there: the "PushLaunch"- and "PushRenewal"-tasks are actually visible without an elevated session, which would indicate they're user-based. 

         

        Disclaimer: apparently, no one really ever documented what "deviceenroller.exe" does (or at least, I can't find it), so what I write here is based on my own observation and the sparse information found online.

Resources