Home » Posts tagged 'Lync Install'

Tag Archives: Lync Install

Lync 2013 Failed to Publish Topology ACL Error on File Share

While publishing the first topology, you may get an error when the topology builder attempts to enable to topology. Looking at the error it seems to suggest that the install cannot read the permissions on the Lync file share. In order to resolve this edit the file sharing permissions and add in the following groups giving them full control permissions to the share

  • RTCHS Universal Services
  • RTC Component Universal Services
  • RTC Universal Server Admins
  • RTC Universal Config Replicator

Re-publish the topology.

Office Web Apps Server Prerequisites

To install WAC Server on Server 2012 use the following powershell

Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core,NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-HTTP-Activation45

Lync 2013 – DHCPUtil.exe error MSVCR110.dll is Missing when running config script

In order to use Lync Phone Edition devices on your network you must configure DHCP options to support Lync Phone deployment. Lync 2013 has a nice little script that can configure a windows DHCP server with the correct options. This is located on the Lync Front End server in c:\program files\common files\microsoft lync server 2013 directory. The 2 files you need are

  1. DHCPUtil.exe
  2. DHCPConfigScript.bat

Copy these to your DHCP server.

To configure the DHCP server open Command Prompt and go to the directory where you copied these files. From there run the following command

dhcputil.exe -SipServer lyncpool.domain.com -WebServer lyncpool.domain.com -RunConfigScript

You may get an error message saying the MCVCR110.dll is missing. This is a C++ runtime dll. You can install the C++ runtime if you want but a quicker way is to copy the following files from a server that has this already installed (like the front end). You will need 2 dll files

  1. MSVCR110.dll
  2. MCVCP110.dll

Copy these files to c:\windows\system32 folder on your DHCP server and re-run the dhcputil command.

For convenience I have included the 2 DLL files in this post below


Lync 2013 Complete Lab Guide Using Single Public IP Address – Part 2 – Building the Pre-requisites

In Part 1 we covered the basic physical, virtual machine and networking setup. In this section we will build the domain, install certificate services, office web apps server and exchange 2013. Please note that these setup processes will not be a deep dive step by step guide and will expect you to have a base knowledge of all technologies discussed.

Building the Domain

On the VM DC01 install Active Directory Domain Services and DNS roles. Once installed promote DC01 to a domain controller. Remember to name your Active Directory Domain the same as your external Public domain name. Once promoted reboot the server and continue to configure DNS. There are several DNS records internally required for Lync 2013 and these need creating manually in the AD DNS Zone. Add the following DNS records to the AD Zone:


Lync 2013 Complete Lab Guide Using Single Public IP Address – Part 1 – Setting Up the Lab

The following guides will walk you through setting up a complete, fully functional Lync 2013 Standard Edition deployment complete with Enterprise Voice, Remote Access, Mobility and Exchange Integration. Before we embark on this it is important to understand that this is for Lab purposes only and should not be used in any production deployment.

At times this guide will deviate from Microsoft Best Practices in order to achieve the end goal of emulating a deployment in the real world. I think it is a good idea to outline these now before we start so that you are aware

Guide Liberties

  • We will be using only 1 public IP address instead of the minimum recommended of 2 for the simple reason, I only have one
  • We will be installing the Lync Edge Server in the same LAN segment as the front end server because my lab kit does not support multiple network segments
  • We will be using non standard ports for some services in order to achieve a fully featured environment
  • We will be using our own Certificates from the Internal CA for external access because I am not spending money on proper certificates in a Lab

To begin this Lab, lets start with the basic requirements


%d bloggers like this: