A DSC pull server can be installed either as an HTTP pull server or an SMB pull server. You must choose which type to use before installing your DSC pull server as it determines how the target nodes communicate with the DSC pull server and how it functions internally.

An SMB pull server is very easy to get running as it requires just a properly set up file share to function. In simple network topology environments or ones with existing file shares, it may be easier to use an SMB DSC pull server. In more complicated network topology environments, accessing file shares with complicated permission rules across firewalls or multi-domain AD forests is difficult to get right. SMB pull servers also introduce two points of contact for a target node to work: the DSC pull server itself and the server where the file share is hosted. All target nodes must be able to reach the file share server, something that may be harder to accomplish for a file server than a single purpose DSC pull server.

An HTTP pull server, in comparison, requires more initial effort to get working but may be easier to use in the long term. In the short term, it requires you to set up an HTTP endpoint, which means IIS and dependent services need to be installed and configured correctly. If you set up a website, you're going to want to use HTTPS and SSL certificates. Depending on the location from which you get your SSL certificate, this might add extra work for you to procure and deploy (we will cover these steps in a moment). While it may require more initial effort, an HTTPS endpoint is easier to access. There's no dependency on permission rules or AD forests. In complicated network environments, getting one port allowed on multiple firewalls is much easier than allowing the SMB traffic through.

Considerations such as these largely depend on your environment, so evaluate your options carefully before proceeding.