To install updates for a Lync Server 2013 installation that has had any of the following previous cumulative updates installed, you must do steps 1 and 2. InDepth. The 2017 Microsoft Product Roadmap. Standouts of this years release calendar include Windows 10s next update milestone and Azure Stacks longawaited launch. Configuring Windows NLB for AD FS 2. When we have two or more AD FS and AD FS Proxy servers we install them into a farm configuration. Even though the AD FS servers are installed in a farm configuration, we still need to network load balance them. This can be done with hardware recommended for large Enterprise deployments or with software recommended for small to medium deployments. Office 365 Unable To Install Lync For Mac' title='Office 365 Unable To Install Lync For Mac' />This post will cover installing Windows Network Load Balancing on Windows Server 2. Installing Windows Network Load Balancing Feature. Login to the AD FS server with an Administrative account. Open Server Manager. Click Manage. Click Add Roles and Features. Click Next. Select Role based or feature based installation. Click Next. Select the AD FS server from the server pool. Click Next. Click Next, not adding any server roles. Select Network Load Balancing from Features. Add the required features by clicking Add Features. Click Next. Click Install. Screen-Shot-2014-06-03-at-1.19.11-PM.png' alt='Office 365 Unable To Install Lync For Mac' title='Office 365 Unable To Install Lync For Mac' />Let the install finish and reboot the server when completed. While you are waiting, complete the same steps on the second AD FS Server. Configure Windows Network Load Balancing. Once the feature has been installed on both nodes, make sure that they are both rebooted. Login to the primary AD FS server with an administrative account. Open Server Manager. Click Tools. Click Network Load Balancing Manager. Do your best work with Office, use features and with your. Click Cluster. Click New. Add the primary AD FS server name. Click Connect. Click Next. Verify that the Priority is set to 1 for the first node and verify the IP address. Click Next. Add and IP address VIP for Windows NLB to use. Click Next. Add the Cluster Name Full Internet Name matches the AD FS Farm NameChange to Multicast. Click Next. Click Edit we need to limit what we are load balancing to TCP 4. Change the port range to 4. Change the protocol to TCPClick OKClick Finish. The primary AD FS server is added and the NLB cluster is converged green is goodAdding the Second AD FS Server to the NLB Cluster. While still working on the Primary AD FS server, open Network Load Balancing Manager. Right click the cluster name. Click Add host to cluster. Enter the name for the second AD FS server. Click Connect. Click Next. Verify the priority is set to 2. Verify the IP address matches the second AD FS server. Click Next. Verify the port and protocol match the cluster TCP 4. Click Finish. Second AD FS Server is added and converged. Update DNSNow that the AD FS Servers are load balanced, we have to update DNS. Make sure that the A record for the AD FS Farm Name is updated to match the NLB Cluster IP. Group Activities To Overcome Fear Of Rejection. This will allow for NLB to direct AD FS traffic to the two AD FS Servers. Type. Name. IPAsts. Afs. 01. office. 36. Afs. 02. office. 36. Thanks for visiting and reading my posts. I am always looking for more ideas. Please comment or email me with what you would like to see. Kelsey Epps. Office 3.