Clearly this is safe in a lab environment but if the Edge server’s external interface is to be routed to the Internet than a different approach may be advisable.As covered in the other article it is critical to set the proper Fully Qualified Domain Name (FQDN) on this server so that the server component installation will function correctly.This is a commonly missed step that leads to troubleshooting installation issues further down the line.
Add-Windows Feature RSAT-ADDS, NET-Framework-Core, NET-Framework-45-Core, NET-Framework-45-ASPNET, Web-Net-Ext45, NET-WCF-HTTP-Activation45, Windows-Identity-Foundation, Telnet-Client –Source D:\sources\sxs Before installation any Sf B components make sure to apply the most recent Windows Updates, with one notable exception: do not install the Microsoft .
NET Framework 4.6.1 package as this is not currently supported by Microsoft.
The network topology of the lab environment used for all the articles in this deployment series simply consistent of two physically separated network segments.
A single firewall with separate network interfaces provides connectivity for each network segment to the Internet.
Make sure to open and test the required ports and protocols before attempting to deploy and start the Edge Server services.
The existing server has been prepared with two network interfaces connected to two separate IPv4 networks.
This is a normal practice in environments with multiple routed internal networks but unnecessary in a standalone lab environment like what is used in this example.
If Remote Desktop connectivity is lost after moving the default gateways as shown above then connect to the server console and either define a required static route to back to the network where the remote console is, or if that console is actually in the ‘External’ network then check the firewall configuration to allow remote desktop connections to the external interface.
To enable one or more of these feature follow these example steps.
Only remote user access will be enabled in this article.
The baseline for this deployment is a new Windows Server 2012 R2 installation that is not joined to any Active Directory domain and is connected to two separate IPv4 networks.