Now we will go a step further and prepare to deploy an Edge server in our lab. To me, in complexity, Edge is no more complicated than any other role, but looks like many folks are having troubles.
Perhaps the most important (and often omitted) step is… to relax, pull back for a moment and think – “What is that I want to achieve and what resources I have on hand”.
All right, what do we have…?
I will deploy my Edge in “DMZ”. While I don’t really have DMZ in my lab and don’t have time to build one, I will place the Edge on the same subnet where the Lync server is, but the presumption is that you will definitely separate your internal resources from the “Big, bad Internet”.
I will use two different FQDN’s – sipint.drago.local for the machine name (SIPINT with domain suffix applied) and sip.drago.ws for external access.
Because I “have” only one public IP address available, this is what I will use when configuring the topology.
sip.drago.ws 10.20.50.50 (mapped to xxx.xxx.xxx.xxx); port 5061
sip.drago.ws 10.20.50.50 (mapped to xxx.xxx.xxx.xxx); port 444
sip.drago.ws 10.20.50.50 (mapped to xxx.xxx.xxx.xxx); port 443
***Note that I will use the same Public IP address for all Edge Interfaces, and so, I must be sure the ports are not overlapping.
Upon completion, I expect to have:
- External access for my users
- Federation with other domains
- IM, Video, Audio and desktop sharing with federated domain uses
Because this is a lab, I do not expect to complete PIC federation (IM and A/V session with MSN network users).
Preparing the server to host Edge Role
My server is already named “EDGEINT”.
However, I MUST apply the domain suffix or later the MTLS will fail.
…and restart when done. Now the “Full Computer Name” is FQDN.
Next I will provision the IP addresses on my server, where I will use a public DNS server and add my Lync FE to the hosts file.
…and now EDGEINT resolves our fe.drago.ws
We can now proceed with satisfying the software prerequisites as described here: http://technet.microsoft.com/en-us/library/gg412931.aspx
Again, I will run this command:
servermanagercmd -install Net-Framework Net-Framework-Core Net-Win-CFAC Net-HTTP-Activation NET-HTTP-Activation WAS WAS-Process-Model WAS-Net-Environment WAS-Config-ApIs
TechNet talks about this update: http://go.microsoft.com/fwlink/?LinkId=205459, but since I user Windows 2008 R2 SP1, the presumption is that the fix have been incorporated in the SP1 and I will sclip this step.
Next we will add our Edge server to the Topology.