locked
Cannot initiate MDM synchronization in Windows 10 Pro (0x80072F8F) RRS feed

  • Question

  • Hi.

    We have a problem with Windows 10 MDM. We are trying to get our MDM solution work in an environment that has no access to Internet. The tablets to be managed have Windows 10 Pro (build 1703) and they have installed the certificate in order to recognize the server and allow HTTPS protocol. Connectivity is resolved because tablets are enrolled to the MDM and the browser can open some server's html pages, but the tablets cannot receive commands from the server. When I click on "Synchronize" button in the tablet's MDM connection detail screen it takes some seconds to answer with an error message "cannot initiate sinchronization (0x80072F8F)". The MDM server never receives the request from the tablet, as if they were not in the same network, but they are. I checked the system event log "Microsoft/Windows/DeviceManagement..." but the error message only says "The OMA-DM message could not be sent (unknown Win32 Error code 0x80072F8F)". How can we know the exact reason or have a complete error description? In a different environment the same tablet worked perfectly with our MDM solution, but here we cannot synchronize it. Any ideas?

    Thanks in advance.  

    Tuesday, December 26, 2017 5:00 AM

All replies

  • The following error in the "Security" event log is generated everytime I attemp sinchronization. It says something about the Windows filtering platform blocking a package. Could this be the reason of the problem with MDM? Thanks

    ---------------------------

    Nombre de registro:Security
    Origen:        Microsoft-Windows-Security-Auditing
    Fecha:         26/12/2017 01:37:48 p. m.
    Id. del evento:5152
    Categoría de la tarea:Colocación de paquetes de Plataforma de filtrado
    Nivel:         Información
    Palabras clave:Error de auditoría
    Usuario:       No disponible
    Equipo:        TABKLET2.xxxxxxxxxxxxxxxxxxxxxxxxxx
    Descripción:
    La Plataforma de filtrado de Windows bloqueó un paquete.

    Información de aplicación:
    Id. de proceso: 0
    Nombre de aplicación: -

    Información de red:
    Dirección: Enlace interno
    Dirección de origen: 0.0.0.0
    Puerto de origen: 68
    Dirección de destino: 255.255.255.255
    Puerto de destino: 67
    Protocolo: 17

    Información de filtro:
    Id. de tiempo de ejecución de filtro: 120442
    Nombre de nivel: Transporte
    Id. de tiempo de ejecución de nivel: 13

    ---------------------------


    Eduardo

    Tuesday, December 26, 2017 9:22 PM