Forum Discussion

Paul Rizzi's avatar
Paul Rizzi
Copper Contributor
Mar 01, 2018

OSD Task Sequence Issues

Recently configured SCCM 1710 and attempting to apply a windows image using an OSD Task Sequence deployment that fails after the ConfigMgr client is installed. When going over the SMSTS.log file, I see the following messages and errors:

 

Current Management Point is <empty>

Socket 'connect' failed; 8007274d

Failed to connect to MP :80

Socket 'connect' failed; 8007274d

Failed to connect to MP :443

 

I have added the appropriate boundaries, the firewall is turned off on the MP server, and the ports are open on our network as our new SCCM 1710 server is on the same network as our old SCCM server, but using a different PR site. 

  • Jeremy Dorst's avatar
    Jeremy Dorst
    Copper Contributor

    i hope someone can shed some light on this, as I have begun to experience the same issue. 

     

    thanks

    • Garth Jones's avatar
      Garth Jones
      MVP

      The error # translated to "No connection could be made because the target machine actively refused it."

      Source: Windows

      So check your firewalls, date/time, AD accounts. 

  • RuudGijsbers's avatar
    RuudGijsbers
    Iron Contributor

    Hi Paul,

     

    It looks like your Task Sequence can't locate an MP. Is the MP published correctly? Did you configure the MP for the Task Sequence Media? Is the MP configured to use HTTPS with a self-signed certificate? These are just some questions that come to mind by seeing the error.

     

    Best regards,

    Ruud Gijsbers

Share