none
DeviceManagement log event id 404

    Question

  • Hi

    I am trying enroll Windows 10 1809 into Intune.

    The machines have been installed using a sysprepped image via MDT/WDS.

    I have GPO, MDM etc. setup according to guides and I even get Company Portal (which is assigned as required) installed on the machines.

    The problem is that when I open Company Portal on any of the machines, I get a message that my administrator has not made any apps available and that the device is has not yet been configured for company usage.

    In the Microsoft-Windows-DeviceManagment-Enterprise-Diagnostics-Provuder/Admin log, I have event 75 which indicates everything is good, but I continoulsy receive event 404, stating that:

    "MDM ConfigurationManager: Command failure status: Configuration Source ID: (xxx), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (DMClient), Command Type: (SetValue: from Replace), CSP URI: (./User/Vendor/MSFT/DMClient/Provider/MS DM Server/FirstSyncStatus/ServerHasFinishedProvisioning), Result: (File not found)."

    I suspect that the above error is the cause of my problems, but I can't seem to find the solution.

    Anyone?

    Thank in advance.

    /Michael


    • Edited by MGLDK1 Thursday, December 6, 2018 12:09 PM
    Thursday, December 6, 2018 12:07 PM

All replies

  • You don't need the company portal to enroll Win 10 in to Intune. You can do auto enrollment via hybrid ad join or you can manually enroll devices.

    https://docs.microsoft.com/en-us/intune-user-help/enroll-your-w10-phone-or-w10-pc-windows


    BI For SCCM https://www.fatstacks.tech/home/bi | Register for a Free Demo

    Thursday, December 6, 2018 7:23 PM
  • You don't need the company portal to enroll Win 10 in to Intune. You can do auto enrollment via hybrid ad join or you can manually enroll devices.

    https://docs.microsoft.com/en-us/intune-user-help/enroll-your-w10-phone-or-w10-pc-windows


    BI For SCCM https://www.fatstacks.tech/home/bi | Register for a Free Demo

    Hi

    That's true - maybe my question wasn't very clear.

    I need the Company Portal for my users to be able to install available software. The Company Portal gets installed, but the portal doesn't show apps or any devices :-(.

    I am not sure, whether the event 404 has anything to do with that, but it's the only error I have in the Microsoft-Windows-DeviceManagment-Enterprise-Diagnostics-Provuder/Admin log.

    /Michael

    Thursday, December 6, 2018 7:42 PM
  • Hello Michael,

    Could you please check the status of the device enrollment in Intune console?

    You can navigate to Devices - All devices, search for the device, and check out the followings:

    Compliance - Compliant

    Ownership - Corporate 

    Associated user - AAD Account

    If the device is not listed there, then the device is not enrolled in Intune.

    By the way, how did you enroll the device? Did you follow the method in the following article?

    https://docs.microsoft.com/en-us/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, December 7, 2018 5:03 AM
  • Hi Andy

    Yes, I have enrolled using GPO and the enrollment is working. The devices show up as Compliant and Intune/MDM Managed.

    Actually it seems to be working now. I changed 'Device Limit Restrictions' from default 5 to 15.

    I just don't understand why that has anything to do with Company Portal?

    /Michael

    Friday, December 7, 2018 6:37 AM
  • Hello Michael,

    It just limits the number of device enrollment per user. 

    I don't think there is anything to do with the Company Portal.

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, December 7, 2018 6:56 AM
  • I agreee - nevertheless it seems my problem is solved..... For now anyways :-)
    Friday, December 7, 2018 7:02 AM