Agent on client
We are using DirectAccess to communicate with our domain when our clients are outside the LAN or on a unsecure WiFi. The problem is that you can't contact a client when it's on DirectAccess, it has to be the client who contact the server.
This will be a problem when Windows Server 2012R2 is replaced with 2016, there will not be anyway to connect to a LAN thru secure WiFi because NAP/NPS is gone in Windows Server 2016 and every client which is not connected with a cable will use DirectAccess.
It would be nice to have an agent on every client that contact the PDQ server and download and install packages.
Microsoft strategy is to have everythin cloud based, no LAN only open network and Office 365-like program...