Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
DSC Pull Server clients can not send status reports #2921
Steps to reproduce
Setup DSC Pull Server as described on TechNet at https://msdn.microsoft.com/en-us/powershell/dsc/pullserver and register some clients with a registration key and configuration name to the DSC Pull Server. (LCM configured for ConfigurationRepositoryWeb and ReportServerWeb)
DSC clients can send successfully status reports to the DSC Pull.
Some clients can send successfully status reports and some clients fail to send the status reports with HTTP error 400 (Bad Request).
In the Failed Request Tracing log file from IIS on the DSC Pull server contains the following error message:
Client (Server 2016):
DSC Pull Server (Server 2012 R2)
Having exactly same issue on Windows 10 DSC nodes. Server 2012 R2 nodes send reports to Web Pull Server successfully.
Node (WIndows 10):
Web Pull Server (Server 2012 R2):
Errors on Pull Server:
Errors on Nodes (Windows 10):
This seems to be a issue when the DSC Pullserver is running on WMF 5.0 and the clients are running on WMF 5.1 as in WMF 5.1 the additional parameter "AdditinalData" was introduced.
When the DSCPullserver is also running on WMF 5.1 the above error is gone. However the status reports does still not work correctly. The client can send successfully the report data but the DSC Pullserver seems to have issues to store the data in the database. Every time a client reports the w3wp.exe process of the DSCPullserver has a lot of exceptions.
And then the reports of the clients are always empty. So the status reporting is still not working correctly in WMF 5.1!
added a commit
Jan 31, 2017
The only solution is to upgrade the DSC Pull Server to Server 2016 or to WMF 5.1 which is now RTM