Skip to main content

Lync Server 2010 to Lync Server 2013 installation steps

Lync Server 2010 to Lync Server 2013 installation steps

Recap: I have Lync Server 2010 installed in my environment and want to migrate Lync Server 2013.
You can find so many articles on Lync Server 2013 installation however I have recently deployed Lync Server 2013 for of my customer and want to share best practices with you.
Step: 1: Install Windows Server 2012 and update patches with latest one.
Now you need add your Windows Server to Domain Lync Server 2013 supported following Server Operating System
·         Windows Server 2008 R2 SP1 or latest service pack

·         Windows Server 2012

·         Windows Server 2012 R2

Step: 2: After Server Operating System installation, complete the following pre-requisite –
a.     Windows PowerShell 3.0
b.     Microsoft .NET Framework 4.5 on all internal server roles.
c.      After .NET Framework 4.5 is installed, use Server Manager to install HTTP Activation.
d.     Windows Identity Foundation 3.5 in order to support server to server authentication scenarios.
e.     Internet Information Services (IIS) with so many components. ( )
Use the following command let to install all components without fail.
Open PowerShell and Import-Module ServerManager and then run following command so that all required prerequisites gets install.
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-WCF-HTTP-Activation45
Step: 3: Create DFS name space for Lync to store share information.
Best method is to create share folder on domain controller and then create folder on SQL server or somewhere else.
You can refer my previous article for, How to create DFS for Lync 2013.
Step: 4: This is time to Install Lync Server 2013, Core Components and start the Deployment wizard.
a.     Start Lync Server 2013 Media DVD. Refer Image 1.

b.     Time to Accept the License Agreement. Refer Image 3
c.      Now install Lync Server 2013, Core Components. Refer Image 2.

d.     Core Component installation progress.  Refer Image 4. 
e.     After core component installation open Lync Server deployment Wizard. Refer Image 5. 
a.     This is time to Prepare Active Directory.
Note: You must have Schema Admins and Enterprise Admin permission in order to prepare the Active Directory.
Step1: Prepare Schema. [Once per deployment]
Click on Run next to prepare Schema and it will start the Schema preparation for Lync Server 2013. This step will extend the schema and add the new classes and attributes.
Step2: Prepare Current Forest. [Once per deployment]
Click on Run next to Prepare Current Forest and it will start.
It will create global settings and Universal group for Lync server component.
Step3: Prepare Current Domain. [Once per Lync Server user or server domain]
It will set Access Control entries for Lync Server universal group.
Refer image 6 
b.     Again open Lync Server 2013 – Deployment Wizard and install Administrative Tools. Refer Image 7. 
Note- Best practices: Run the latest Lync Server 2013 Cumulative Updates.

c.      After Administrative tools installation, you will get Lync topology builder to build the topology.
1.     Download the existing topology and open the same. Refer Image8 
2.     Under Lync Server 2013 define the Lync front end pool name. refer Image9 
3.     Define Lync FE pool name. Refer Image10. 
4.     Add the Front End server FQDN. Refer Image11 
5.     Now time to define required role. We are defining all except EV (Enterprise Voice). Refer Image12 
6.     Check the "Enable an Edge pool to be used by the media component of this Front End pool" Option. Refer Image13 
7.     Next page define the SQL server FQDN and port number and use default instance. Refer Image14 
8.     Now time to add Mirror SQL server FQDN and select default instance. Refer Image15 
9.     Now time to ‘enable SQL Server Store mirroring’ it will show both SQL servers FQDN with default instance. Refer Image16. 
10.                        Next screen you have define the file store. Type the domain FQDN where you created file store and folder name. Refer Image17 
11.                        Next screen define the Web services URL. (Internal and external URL). Refer Image18 
12.                        Next screen define the Office Web App Server name and URLs. Refer Image19 
13.                        Next screen select Office Web App Server with Associate pool with an Office Web Apps server in central site. Refer image20 
14.                        Next screen define the Archiving SQL server store and Archiving SQL server store mirror. Refer image21. 
15.                        Next screen define the Monitoring SQL server store and Monitoring SQL server store mirror. Refer image22. 
16.                        Next screen select the Edge Server. We are migrating Lync Server 2010 to Lync Server 2013, here we are initially using legacy Edge server so select legacy edge server FQDN. Refer image23. 
17.                        Now Publish the Topology. Refer image24 
18.                        Now create database, select SQL server. Use SQL Server instance defaults. Refer image25. 
19.                        Now create mirror database and select the same. Refer image26. 
20.                        Now published the Topology. See the screenshot Image27. 
21.                        Topology Published. Refer Image28. 
22.                        After Lync topology published, Time to install Lync component on Front End Server. Open Lync Server 2013- Deployment Wizard and deploy the Lync Component. On Deployment Wizard, click on “Run” next to ‘Install Local Configuration Store’.
23.                        Next screen select option 'Retrieve directly from the Central Management store (requires read access to the Central Management store). Refer Image30. 
24.                        See the progress of Local configuration Store installation. Refer Image31. 
25.                        Lync Server components installation complete. Refer Image32. 
Note: It will install SQL express edition on FE server locally and ask for reboot.

26.                        Now time to 'Setup or Remove Lync Server Components'. Click on 'Run' button to start. Refer Image33. 
27.                        Next screen click on "Next" to install the components. Refer Image34. 
28.                        Next screen see the installation progress and see the components which are getting installed. Refer Image35. 
29.                        Next screen see the Installation get completed and "Finish" button shows to complete the installation. Refer Image36. 
30.                        Open Deployment Wizard and Step 2: is showing checked mark. Refer Image37. 
31.                        Again open Lync Deployment Wizard and Run the Step 3: to Order and assign Certificate for Lync Client-Server communication. Refer Image38.

Ordered the certificate: Installed both certificate Lyncauth and Lyncinternal certificate on server.
Once assign the certificate now certificate part shows green.

NOTE: As per Best practices-
                                                      o   To install Latest Cumulative Updates again to get all components updated.

o   Later Update the SQL database (Backend Server).

o   Now you can run Bootstraper.exe to make sure.

o   Later run the Start-CsWindowsServices to start all required services.

32.                        See the Image39 to show Lync Server 2013 services started.

Note: If your deployment has multiple Front End servers then install Lync components on all remaining front end server. In my deployment was two Front End Server.

Now Office Web Apps server Deployments

Web Office App server Installation:

Note: We are installing Office Web Apps server to Windows 2012 R2 Server.
1.     Install all prerequisite:
a.     .NET 4.5.2

2.     Download the Office Web Apps and unmounts the ISO image.
Before installation you must install all prerequisites.

3.     Open Windows PowerShell and run the following command to with Admin rights.
Import-Module ServerManager
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

4.     Open folder where you downloaded the Office Web Apps.

5.     Click on Setup executive files. Refer Image002 
6.     Next screen you must accept the license. Refer Image003. 
7.     Next screen you need to choose a file location. Refer Image004 
8.     You can see the Installation Progress. Refer Image005

9.     Next screen you see installation got completed. Refer Image006 
10.            Now it’s time to Install Service Pack 1 for Microsoft Office Web Apps Server (KB2880558) 64-Bit Edition and accept license. Refer Image007.

11.            Now you can see the installation progress. Refer Image008. 
12.            Next screen it shows installation completed. Refer Image009. 
13.            It’s time to configure internal and external farm URLs. Use below command to configure both Urls.

New-OfficeWebAppsFarm -InternalUrl "" -ExternalUrl "" -CertificateName "" -EditingEnabled

14.            Refer Image10 for better information. 
Thank you.


Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: ·User name: orgname\bilag ·Password: ************
Note: is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…