{"id":1651,"date":"2014-05-29T17:33:00","date_gmt":"2014-05-29T17:33:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2014\/05\/29\/how-to-retrieve-node-information-from-dsc-pull-server\/"},"modified":"2019-02-18T13:05:18","modified_gmt":"2019-02-18T20:05:18","slug":"how-to-retrieve-node-information-from-dsc-pull-server","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/how-to-retrieve-node-information-from-dsc-pull-server\/","title":{"rendered":"How to retrieve node information from DSC pull server"},"content":{"rendered":"

NOTE –\u00a0The latest information regarding DSC Pull Service can be found in the DSC documentation using the link:<\/span>\nhttps:\/\/docs.microsoft.com\/en-us\/powershell\/dsc\/pullserver<\/a><\/p>\n

……….<\/p>\n

As described in \u201cPush vs. Pull Mode\u201d<\/a> blog, DSC configuration can be applied on target nodes using pull or push mechanism.\u00a0 In this blog I will talk about how to retrieve node information from DSC pull server. When the node pulls a configuration from the pull server and applies it locally, the pull can either succeed or fail. DSC compliance endpoint stores the pull operation\u00a0status, configuration\u00a0and node information in a database. Compliance endpoint can be used by admins to periodically check the status of the nodes to see if their configurations are in sync with pull server or not (using tools like Excel or write their own client application).<\/p>\n

In this post I will cover the following:<\/p>\n

\n