How to install Lync Server 2013 – Part II

Favad Qaisar 4 September 2012 1




We would be starting this part with the building of different topologies that are needed by the Lync server 2013. For this go to the installation wizard and click “install administrative tools”, it might take a few seconds to start up but once it is up and running you can start Lync server topology builder.

Check the new topology in the radio buttons and click ok

Now to define this topology, first of all you need to provide the primary SIP domain and click next. Then it asks you for any additional supportive domains. Add any if you want to and click next. Now it will ask you to define the first site. I.e. name and description of the site, enter that and click next now specify site details like city, state and country and click finish. What we need to do next is to define a new front end pool.

Select the standard edition server and after clicking next, check the features as shown in the image

Below:

Click next and select “Collocated server roles” before again clicking next, now you’’ have to define the SQL store,its better to leave the default credentials there and clikc next, in this window you would have to define a file store manually. Click next after that again and it would take you to the “specify web services URL” window where you have to define your external Base URL. After this comes the office web apps server selector. Just point it to your OWA.(your-domain name). You are done with this wizard. Go to edit properties of the topology and define the admin URL there. Now it’s time to publish the topology. Once you have published it, you can open the click here to open the do list text file to double check that you have done everything mentioned there.

Now to install the Lync server system, go to the deployment wizard again and click install or update lync server system. The components that you need to install include RTCLocal database, speechfiles, setup Certs and then start Lync services. (To install RtcLocal run and retrieve directly from the CMS) Run, select “default certificate” and then click request. Next you have to choose a certifying authority from a drop down list. Specify alternative certificate template and click next where you would have to fill the name and other security settings. For SIP domain setting on SAN, select SIP domain and click next and the certificate wizard would open up.

Make sure you check the “default certificates” as visible above and click assign. Now comes the most important part, to start the services do that and to check if they started fine, you can open the services and check their present status (it should be running)

If everything is fine, go to start menu and run Lync control panel, it would prompt you to enter your administrative credentials. It is always a better option to make a few test accounts and not to use the administrator account so do those in your AD server. Now go back to the control panel and add these users. Click the enable button and if all goes fine, three users should be readily available for login on Lync. That’s about it!




Favad Qaisar (51 Posts)

I am a Unified Communications Engineer. Over the last 3 years, I have been working dedicatedly on OCS/LYNC and Exchange 2007/2010. I was responsible for getting my Company Microsoft’s Unified Communication Voice Certified Partner status. Occasionally, I like to share my experiences on the latest developments in the Unified Communications industry.

One Comment »

  1. Shahram 19 November 2012 at 3:12 am - Reply

    ..We have also used port redirection for etxernal web services to 4443 for these URLs We have created DNS A records for meet and dialin on our public DNS server..In Forefront TMG 2010 we created one Non-Web Server Publishing rule using the New Server Publishing Rule Wizard ..Next on the Select Server page we typed the internal IP address of our Lync Server ..Then on the Select Protocol page from the Selected protocol drop-down list we selected HTTPS Server and then clicked Properties ..On the HTTPS Server Properties page under Application Filters we verified that none of the filters are selected Back on the Select Protocol page we clicked Ports. On the Network Listener IP Addresses page select External and then Address On the External Network Listener IP Selection page select the specific IP address for your Meet and Dialin URLs On the completion page click Finish After the rule has been created right-click the rule click Properties and then click the To tab..On the To tab click the Requests appear to come from the Forefront TMG computer option and then click OK to apply the changes Now when our users are etxernal or federated or anonymous users try to join our Online meetings they can connect.

Leave A Response »