#MICROSOFT LYNC 2013 SERVER INSTALL#
#MICROSOFT LYNC 2013 SERVER UPGRADE#
#MICROSOFT LYNC 2013 SERVER DOWNLOAD#

Right click on the Edge pools folder and select New Edge PoolвЂ¦: Once the Edge server has been configured, the next step is to define and then publish the topology:

#MICROSOFT LYNC 2013 SERVER INSTALL#

The only package youвЂ™ll need to install when using Windows Server 2012 as the operating system is the Windows Identity Foundation which can be added via the following cmdlet in PowerShell:ДЄdd-WindowsFeature Windows-Identity-Foundation Since weвЂ™re installing PowerShell 3.0 onto a Windows Server 2008 R2 SP1 server, proceed by downloading the following file:Д¬ontinue and Windows Identity Foundation from the following URL:

#MICROSOFT LYNC 2013 SERVER DOWNLOAD#

ThereвЂ™s a list for 4 items for download and the way to determine which one youвЂ™re supposed install is actually noted at the bottom. NET Framework 4.5 from the following URL:Д¬ontinue and PowerShell 3.0 from the following URL: Proceed with downloading and installing Microsoft. The following packages will need to be installed if you are using Windows Server 2008 R2 as the operating system for your Edge server: Static routes will also be needed for your Edge server to get to the internal server VLAN and workstations so proceed with documenting what VLANs your Edge will need to have access to and add the static routes onto the server as persistent routes:Д¬onfigure a DNS Suffix for the Edge ServerДЄ DNS suffix is automatically added if a server is joined to the domain but since the Edge server isnвЂ™t and shouldnвЂ™t be, we will need to manually add it: The external interface also does not need Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks enabled: The external interface shouldnвЂ™t attempt to register with DNS so the Register this connectionвЂ™s addresses in DNS is unchecked: Two additional IP addresses (total of 3) are assigned to the external interface: Note that the default gateway is filled out but the DNS servers isnвЂ™t. This is what the DMZ NIC settings for the Edge server looks like: Note that there is no default gateway specified but the DNS servers are filled in with the internal DNS servers.

This is what the internal NIC settings for the Edge server looks like: This means the internal NIC is not on the same subnet as my Lync Enterprise Pool server. **Note that both of my NIC interfaces on the Edge server is in a true DMZ network segment. вЂ¦ this post will set up Edge to use internal DNS servers for name resolution (I always avoid host files whenever I can). The official Edge deployment guide for the previous version Lync Server 2010 recommends to use external DNS servers and host records to resolve internal domain servers for the most secure configuration but and while IвЂ™ve gone demonstrated in one of my old Lync Server 2010 Edge posts: How you configure your Edge serverвЂ™s NICs will depend on your network topology such as whether there are DNS servers available in the perimeter network and how your DMZ network is set up. The NIC IвЂ™ve labeled DMZ-Inside-636 will be the NIC that is used to send traffic into your internal network while the NIC labeled DMZ-Outside-637 will be the NIC that is connected to either your DMZ network or directly to the internet.

Set Up Network Interfaces for Edge Servers More information about NIC interfaces can be found at the following URL:

Make sure you have 2 NICs for your Edge server as shown in the following screenshot: There are quite a few tasks required before you can actually begin installing Edge services onto the server youвЂ™ve allocated for this server role and the first item you should turn your attention to is the network interface configuration.

#MICROSOFT LYNC 2013 SERVER UPGRADE#

I recently had to upgrade 2 Lync Server 2013 Edge servers (one on Windows Server 2008 R2 and the other on Windows Server 2012) and since I havenвЂ™t written a blog post demonstrating the process, I went ahead to document one of the deployments for this blog post.

Microsoft lync 2013 server