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...
0
Comments
I will say two words: Have patience ;)
Yes... and is it closer to a solution yet?
No official release date yet. But I assure you, it is coming. They are actively developing/testing it. I had a conversation with them about a few things and it yesterday.
Nice, give them a beer and motivate them to test 24/7. ;)
Any update on this by chance?
Is there a date for release yet? Windows 2012 R2 is almost replaced now and there is still no way to deploy to clients on a DirectAccess-VPN...
This feature is on our roadmap. We do not have a set date yet.
Is it any progress in this matter...
I'm sorry, but we still do not have a set date.
Something my company would be interested in also
PDQ Inventory 16 is currently in beta and includes the new optional Agent. https://www.pdq.com/blog/introducing-inventory-16/
Lovely!! :) And in next version of PDQ Deploy, this function will be present as well?
All I can say is PDQ Deploy support is coming soon.