Download Upgrading Your Skills to MCSA-Windows Server 2016.PrepAway.70-743.2020-11-03.1e.63q.vcex

New installations of AD FS 2016 require the Active Directory 2016 schema (minimum version 85). Upgrading a domain controller will upgrade the schema. Note: upgrading the schema is not the same as upgrading the domain for forest functional level.  Upgrading the functional level is not required.

For a Windows Server 2012 R2 AD FS server, this solution would work. However, new installations of AD FS 2016 require the Active Directory 2016 schema (minimum version 85). 
References:
https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-fs/operations/configure-device-based-conditional-access-on-premises 
https://docs.microsoft.com/en-gb/windows-server/identity/ad-fs/overview/ad-fs-requirements

New installations of AD FS 2016 require the Active Directory 2016 schema (minimum version 85). You can upgrade the schema by running adprep.exe.

The Add-DnsServerTrustAnchor command adds a trust anchor to a DNS server. A trust anchor (or trust “point”) is a public cryptographic key for a signed zone. Trust anchors must be configured on every non-authoritative DNS server that will attempt to validate DNS data. Trust Anchors have no direct relation to DSSEC validation. 
References:
https://docs.microsoft.com/en-us/powershell/module/dnsserver/add-dnsservertrustanchor?view=winserver2012-ps 
https://technet.microsoft.com/en-us/library/dn593672(v=ws.11).aspx
https://docs.microsoft.com/en-us/windows-server/networking/dns/deploy/apply-filters-on-dns-queries

The NRPT stores configurations and settings that are used to deploy DNS Security Extensions (DNSSEC), and also stores information related to DirectAccess, a remote access technology. 
Note: The Name Resolution Policy Table (NRPT) is a new feature available in Windows Server 2008 R2. The NRPT is a table that contains rules you can configure to specify DNS settings or special behavior for names or namespaces. When performing DNS name resolution, the DNS Client service checks the NRPT before sending a DNS query. If a DNS query or response matches an entry in the NRPT, it is handled according to settings in the policy. Queries and responses that do not match an NRPT entry are processed normally. 
References:
https://technet.microsoft.com/en-us/library/ee649207(v=ws.10).aspx
https://www.microsoftpressstore.com/articles/article.aspx?p=2756482

Network List Manager Policies are security settings that you can use to configure different aspects of how networks are listed and displayed on one computer or on many computers. 
Network List Manager Policies are not related to DNSSEC. 
References:
https://technet.microsoft.com/en-us/library/jj966256(v=ws.11).aspx
https://docs.microsoft.com/en-us/windows/device-security/security-policy-settings/network-list-manager-policies

RAS Gateway - Multitenant. You can deploy RAS Gateway as a multitenant, software-based edge gateway and router when you are using Hyper-V Network Virtualization or you have VM networks deployed with virtual Local Area Networks (VLANs). With the RAS Gateway, Cloud Service Providers (CSPs) and Enterprises can enable datacenter and cloud network traffic routing between virtual and physical networks, including the Internet. With the RAS Gateway, your tenants can use point-so-site VPN connections to access their VM network resources in the datacenter from anywhere. You can also provide tenants with site-to-site VPN connections between their remote sites and your CSP datacenter. In addition, you can configure the RAS Gateway with BGP for dynamic routing, and you can enable Network Address Translation (NAT) to provide Internet access for VMs on VM networks. 
References:
https://technet.microsoft.com/en-us/windows-server-docs/networking/remote-access/remote-access

A new feature of Windows Server 2016 is SET (Switch Embedded Teaming). 
Create a SET team 
You must create a SET team at the same time that you create the Hyper-V Virtual Switch with the New-VMSwitch Windows PowerShell command. 
When you create the Hyper-V Virtual Switch, you must include the new EnableEmbeddedTeaming parameter in your command syntax. 
In the following example, a Hyper-V switch named TeamedvSwitch with embedded teaming and two initial team members is created. 
New-VMSwitch -Name TeamedvSwitch -NetAdapterName "NIC 1","NIC 2" 
-EnableEmbeddedTeaming $true 
References:
https://technet.microsoft.com/en-gb/library/mt403349.aspx

Deploy Network Controller using Windows PowerShell 
1.Install-WindowsFeature 
Install the Network Controller server role 
To install Network Controller by using Windows PowerShell, type the following commands at a Windows PowerShell prompt, and then press ENTER. 
Install-WindowsFeature -Name NetworkController –IncludeManagementTools 
2.New-NetworkControllerNodeObject 
You can create a Network Controller cluster by creating a node object and then configuring the cluster. 
You need to create a node object for each computer or VM that is a member of the Network Controller cluster. 
To create a node object, type the following command at the Windows PowerShell command prompt, and then press ENTER. Ensure that you add values for each parameter that are appropriate for your deployment. 
New-NetworkControllerNodeObject –Name <string> -Server<String> -FaultDomain <string>-RestInte 
3.Install-NetworkControllerCluster 
To configure the cluster, type the following command at the Windows PowerShell command prompt, and then press ENTER. Ensure that you add values for each parameter that are appropriate for your deployment. 
Install-NetworkControllerCluster –Node <NetworkControllerNode[]> –ClusterAuthentication … 
4.Install-NetworkController 
To configure the Network Controller application, type the following command at the Windows PowerShell command prompt, and then press ENTER. Ensure that you add values for each parameter that are appropriate for your deployment. 
Install-NetworkController –Node <NetworkControllerNode[]> –ClientAuthentication 
References: https://technet.microsoft.com/en-us/library/mt282165.aspx

Using Windows PowerShell, the REST API, or a management application, you can use Network Controller to manage the following physical and virtual network infrastructure:
* Datacenter Firewall 
This Network Controller feature allows you to configure and manage allow/deny firewall Access Control rules for your workload VMs for both East/West and North/South network traffic in your datacenter. The firewall rules are plumbed in the vSwitch port of workload VMs, and so they are distributed across your workload in the datacenter. Using the Northbound API, you can define the firewall rules for both incoming and outgoing traffic from the workload VM. You can also configure each firewall rule to log the traffic that was allowed or denied by the rule. 
* Hyper-V VMs and virtual switches 
* Remote Access Service (RAS) Multitenant Gateways, Virtual Gateways, and gateway pools 
* Load Balancers 
References:
https://technet.microsoft.com/en-us/library/dn859239.aspx
https://docs.microsoft.com/en-us/windows-server/networking/sdn/technologies/network-controller/network-controller