Node registration in WMF5 April

Tagged: ,

This topic contains 3 replies, has 2 voices, and was last updated by Profile photo of yaron wainberg yaron wainberg 2 years ago.

  • Author
  • #26798
    Profile photo of sirirako

    I followed this blog to set up the LCM.

    Set-DscLocalConfigurationManager and got this error.

    The attempt to register Dsc Agent with AgentId B74A405E-153E-11E5-80C0-000C29C23BD5 with the server
    http://xxxxx:8080/PSDSCPullServer.svc/Nodes(AgentId='B74A405E-153E-11E5-80C0-000C29C23BD5') returned unexpected response code NotFound.
    + CategoryInfo : InvalidResult: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : RegisterDscAgentUnsuccessful,Microsoft.PowerShell.DesiredStateConfiguration.Commands.RegisterDscAgentCommand

    I have RegistrationKeys.txt that contains the GUID. Is it the way it should be?


    Another thing is that the metamof actually has

    RegistrationKey = "2cfe8756-7d19-46b5-ab98-b59ec0a87259";

    The B74A405E-153E-11E5-80C0-000C29C23BD5 in the error is the existing one on the node.

    Thank you!

  • #26808
    Profile photo of yaron wainberg
    yaron wainberg

    I got the same error

    any luck with the answer?

  • #26870
    Profile photo of sirirako

    YES! I re-configure the Pull Server Web Service by manually delete the site and reconfigure it with xDscWebService. Mine was created in WMF5 Feb and there are changes to it in WMF5 April.

    And I think the change is the method/verb that web service are providing.

    The new one has Nodes which is in the error message Not Found.

    See the available method using http://localhost:8080/PSDSCPullServer.svc/.

  • #27138
    Profile photo of yaron wainberg
    yaron wainberg

    I Managed to solve it with your suggestion


You must be logged in to reply to this topic.