Last Updated on September 16, 2010 by GrahamWalsh
Below is a step by step guide on installing a Lync Server Standard Edition server. I have also included some troubleshooting if you are getting SQL errors. It seems to be from a corrupted SQL exe file that was copied over as part of the install.
I have also created some users on my AD prior to starting the install. My AD also has the DNS, DHCP, IIS and Cert Server installed.
Install Windows
Set Computer Name
Install Windows Updates
Join Domain and login with the domain admin account
Run this command to install the required components before installing Lync.
◦servermanagercmd -i NET-Framework Web-WebServer Web-Common-Http Web-Static-Content Web-Default-Doc Web-Dir-Browsing Web-Http-Errors Web-Http-Redirect Web-Asp-Net Web-ISAPI-Ext Web-ISAPI-Filter Web-Http-Logging Web-Log-Libraries Web-Http-Tracing Web-Security Web-Windows-Auth Web-Client-Auth Web-Performance Web-Stat-Compression Web-Mgmt-Tools Web-Mgmt-Console Web-Scripting-Tools telnet-client rsat-adds Desktop-Experience
Shut down and restart server
Install Microsoft Silverlight – http://www.silverlight.net
Mount the ISO and run the Install from the left hand side. The right hand side options are for the client. Select Run when prompted.
When prompted about installing the C++ tools, select yes.
Next you will be asked where you would like to install the Lync server. I accepted the defaults.
Accept the EULA and click OK
Now you will see the Microsoft Lync Deployment Wizard. Click on Prepare Active Directory.
You will now see several steps to do with preparing the AD. Run through Step 1, Step 3 and Step 5.
Once you’ve done the above steps 1-5, step 7 is to add the Administrator’s account to the CSAdministrator, CSServerAdministrator, CSUserAdministrator and CSVoiceAdministrator groups. Start up ADUC and go to the Administrator’s account and select it. Go to the Member of tab and choose Add. Now add the 4 groups above and click OK.
Now that the AD & administrator’s account is ready, click on back and now select Topology Builder from the right hand side and run through the installer.
The next step is to Prepare the First Standard Edition. Choose this option and select Next and let the installer run through the scripts.
If you setup fails with an error when deploying the SQLExpressRTC, then exit the installer and open up the command prompt and run the following script
start/wait SQLEXPR_x64.exe /Q /HIDECONSOLE /ACTION=Install /FEATURES=SQLEngine,Tools /INSTANCENAME=RTC /TCPENABLED=1 /SQLSVCACCOUNT=”NT AUTHORITYNetworkService” /SQLSYSADMINACCOUNTS=”BuiltinAdministrators” /BROWSERSVCSTARTUPTYPE=”Automatic” /AGTSVCACCOUNT=”NT AUTHORITYNetworkService” /SQLSVCSTARTUPTYPE=Automatic
Once the command prompt has returned the cursor, you can now load the Deployment Wizard again and run the Prepare first Standard Edition server. This should now run and complete all the tasks.
Next is to run the Lync Server Topology builder from the Start menu. When prompted, select New Topology.
Next, give your topology a name. I’ve called mine Polycom. Click Save
Now you will need to provide the primary SIP domain for your network. Mine is polycom.ocs. Click Next. If you have additional SIP domains, add them in on the next screen
You will now be prompted to name the First Site. For the name of the site, try to avoid any spaces.
Next enter further details of the site and then Finish and launch the Front End Wizard
Now we will configure the front end pool. Enter the FQDN of the server and choose Standard Edition Server.
Now we can choose what features we want on our server. I have selected Conferencing, Enterprise Voice and Call Admission Control. I have also selected to Collate Mediation Server
For the other server roles, I am not going to select any monitoring or archiving. The next screen then has the information on the SQL store
Next you need to create a shared folder on the server. I have created a folder in the root called share. You can call it what you like, just ensure the name matches here. Then you can accept the default of the External URL, unless you have a different external URL.
As I don’t have a PSTN gateway just yet, you can skip the stage.
Now that the topology has been created, there are 2 more items to be done before we publish it. Click on Edit Properties in the top right corner (under Central Site). Click on Simple URLs and then enter an address for the Administrative Access. Here I have chosen https://admin.polycom.ocs. Then you can drop down the Central Management Server to select your Front End Server.
Next we can Publish Topology from the right hand side menu. The CMS pool should be displayed. Click on Next the the CMS will start to be deployed to the database. Once the topology has been published you should see the completed wizard.
You can now close the Topology Builder and now choose Install or Update Lync Server System from the Deployment Wizard. Select Step 1 – Install Local Configuration Store and then accept the default of Retrieve directly from Central Management Store.
If you get a SQL install error, then open a command prompt and navigate to d:setupamd64 and run the following command
start/wait SQLEXPR_x64.exe /Q /HIDECONSOLE /ACTION=Install /FEATURES=SQLEngine,Tools /INSTANCENAME=RTCLOCAL /TCPENABLED=1 /SQLSVCACCOUNT=”NT AUTHORITYNetworkService” /SQLSYSADMINACCOUNTS=”BuiltinAdministrators” /BROWSERSVCSTARTUPTYPE=”Automatic” /AGTSVCACCOUNT=”NT AUTHORITYNetworkService” /SQLSVCSTARTUPTYPE=Automatic
Now close the command prompt once the cursor has returned and click on back and then Next. The wizard should now complete.
Next we select Setup or Remove Lync Server Components and let the scripts run through. You may see an error that the server needs to be restarted. If so, click Finish and then reboot the server and start the deployment wizard again where you left off and run Step two again of Setup or Remove Lync Server Components.
If you get any more errors relating to the speech, try to copy over the files from the ISO into the C:ProgramDataMicrosoftLync ServerDeploymentcache4.0.7457.0setupspeech. I just copied all the folders over. I then clicked back and next to run the setup again. Another failure for me again, so I ran the ucmaworkflowruntime installer manually. Then back and next. Once completed, you can now run Step 3 – Request, Install or Assign Certificates. Choose Request on the right hand side
Then choose to send the request immediately and on the following screen it should find your CA. Accept the defaults on the next few screens.
For the friendly name, enter the FQDN of your server and then on the next screen just put in your organisation and then your geographic information. Finally you will see a summary of the URLs for your server.
Next you will see SIP Alternative Name, just select your domain and if you don’t have any other alternative names, just click through the next few screens.
Next is the certificate assignment. Just click through the screens and at the end you will see the certificates now have the friendly name.
Now the fun bit to see that it has all worked. Run Step 4 to start the services and once that is done you can open the Services MMC to ensure they are started.
Finally before we can get clients talking to the Lync Server, we need to add some entries to the DNS server. Log into your DNS server and create the following A records
- meet.polycom.ocs
- dialin.polycom.ocs
- admin.polycom.ocs
Once that is done, we need to create a SRV record for the clients to find the server. _sipinternaltls using _tcp on port 5061.
While you are here, you can create a UDP SRV record for the _ntp time server. This is used when you connect Polycom CX handsets to the network.
Now that this is all done, we can log into the Control Panel. The URL for this is https://admin.polycom.ocs/cscp. You can access this from any machine that has Silverlight installed. Then click on Users and choose Enable Users. I have already created a few users in my AD prior to installing Lync and I have also populated the email address. This means that you can use the email address as the SIP URI. I also enabled my user for Enterprise Voice as I shall be connecting up some Polycom CX handsets to the network. Then click on enable.
To get the client installed, I’ve moved over to a Windows 7 VM and mounted the ISO and ran the client installer. Sign in and hey presto.
That’s it for stage one. Next is to get Unified Messaging working on Exchange 2010 and integrate with Lync Server so we can see the integration with Polycom CX IP Phones Optimized for Lync Server.