Scott Burrell explains the prerequisites for the course and other things you should know for this course.
- [Instructor] I'm excited to be bringing you this course on the Remote Access features of Windows Server 2019. As you get started there are a few things you should know to help you get the most out of this course. Remote Access roles and services help draw the lines between public and private networks. And all of these networks use TCP/IP as a transport protocol. They take advantage of the addressing of IP version four. This course doesn't require advanced skills in IP addressing or subnetting but some familiarity with how IP addresses work would prove helpful, as well as the ability to bring up a DNS and a DHCP server. To get the most out of this course I recommend that you follow along with the demonstrations. I've done all of the demonstrations in this course on a single hyper V server with 128 gigabytes of RAM. And it could probably be done with about half of that. I've created this network with multiple virtual servers and three virtual switches. The one in the center represents the internet, and the two on either end are private switches that represent private office locations. The servers used at the borders need to be created with two network interfaces each so they can perform as border gateways. I've used two different copies of this virtual machine to minimize conflict or confusion as we configure multiple ways to access the network. Additionally, I'll bring up a RADIUS server later on in the course. And there is a domain controller that you won't be seeing on the screen but it's necessary to provide the list of users in Active Directory, as well as to function as a DNS server and DHCP server for that location. The more I look at this network the more I want to get started, so let's jump right in.
- NAT implementation
- Site-to-site and remote access VPNs
- VPN connections to the cloud
- Planning a site-to-site VPN
- NPS configuration
- Using RADIUS to secure remote access
- NPS templates
- Applying connection-specific policies