Well-produced, easy to follow and understand, easy to understand speaker. Thank you!
One of the best videos I have come across.Create to point and precise. Keep up the good work mate.
Thank you very much (very nice). It gives a good understanding of simple DA solution. If it is possible,
please do more videos with DA in Windows Server 2016 with two network cards and DMZ (advanced DA solution).
Great guide, thank you. One thing to add is that DirectAccess will only work on the following endpoint operating systems:
Windows 10 Enterprise
Windows 10 Enterprise 2015 Long Term Servicing Branch (LTSB)
Windows 8 and 8.1 Enterprise
Windows 7 Ultimate
Windows 7 Enterprise
Very detailed video, Excellent work. Thanks
great explaining, thanks.
I followed all the steps exactly you have mentioned but at the end "Get-DnsClientNrptPolicy" does not give anything at all and "netsh dnsclient show state" gives Direct Access Settings and DNSSEC as Not configured. I have done gpupdate /force and restarted server and client. Can you please help.
Awesome video! Would it work having the public dns being 8.8.8.8 instead of having your own?
Hi, thank you so much for your tuto. could please tell me how to configure DirectAccess 2016 client Active Sessions ? the DA is connected on my laptop I can access to the share but tcan't the client on DA server ! thank you again
DANG!! GREAT TUTORIAL!! AND YES I'M YELLING!!! :-) Thank you!
Quite helpful video very well explained👍
great tutorial, can i do direct access using 1 server only?
This person is simply awesome. Any idea how to NAT with Cisco ASA, instead of using Microsoft?
How do i troubleshoot connection issues to DA from external devices?
hi guys has anyone configured it using BT hub 5 router in the UK ? plz let me know. Thanks
When you say IPV6 has to enabled on all servers and clients, what if you have 3rd party servers that are not IPV6 capable. Will you not be able to access them through Direct Access?
What did you to add 443 port? because when I try to usit I get a Message that say, port 443 is in use for Web server.
Thanks for the great video - well detailed.
Just to make sure I have got it right - If we use Kerberos authentication, the features such as load balancing and client management will be disabled? And the only way to have these features working we need certificates (PKI) installed on the client?
PKI could be self-generated?
Super
I followed this to the best of my ability but it doesn't connect when I leave the network and go to an outside network
This channel is a gold mine.