INSTALLING LYNC SERVER 2013 EE POOL ON WINDOWS SERVER 2012 Installing an Enterprise Pool that consists of two Front-End Servers. Server Environment: DC-01.chahla.local (Domain Controller, Certificate Authority) Lync-fe01.chahla.local (Lync Front End Server 01) Lync-fe02.chahla.local (Lync Front End Server 02) SQL-01.chahla.local (SQL Back End Server 01 for RTC Instance) SQL-02.chahla.local (SQL Back End Server 02 for LyncMonitoring, LyncArchiving and Persistent Chat Instances) (not used in this article i will be using it for other articles) Pre-requisites: -Active Directory, DNS, Active Directory Certificate Services (Certificate Authority) (From Dashboard > Add Roles And Features) http://technet.microsoft.com/en-us/library/gg398686.aspx Features.NET Framework 3.5 Features (All).NET Framework 4.5 (ALL) Message Queuing Message Queuing Services Remote Server Administration Tools Role Administration Tools AD DS and AD LDS Tools User Interface and Infrastructure Desktop Experience Windows Identity Foundation 3.5 Web Server (IIS) Role Services Common Http Features Installed
Default Document HTTP Errors Static Content Health and Diagnostics HTTP Logging Logging Tools Tracing Performance Static Content Compression Dynamic Content Compression Security Request Filtering Client Certificate Mapping Authentication Windows Authentication Application Development.NET Extensibility 3.5.NET Extensibility 4.5 ASP.NET 3.5 ASP.NET 4.5 ISAPI Extensions ISAPI Filters Management Tools IIS Management Console IIS Management Scripts and Tools Restart the server after installing the prerequisites. 1) Open the installation media, Microsoft Visual C++ 2012 Redistributable will be installed when you launch the installer.
2) Browse to the location where you want to install and click Install. 3) Accept the EULA.
4) Core components will install.
5) Lync Server 2012 Deployment Wizard will appear.
6) The first thing that we will do is to Prepare Active Directory. Click Prepare Active Directory.
7) On the right side of Prepare Schema, click Run.
8) Click Next.
9) Schema preparation finishes, click Finish. 10) On the right side of Prepare Current Forest, click Run.
11) Click Next.
12) Select Local Domain, then click Next.
13) Forest preparation finishes, click Finish.
14) On the right side of Prepare Current Domain, click Run.
15) Domain preparation finishes, click Finish.
16) Add Users to provide Administrative Access on the Domain Controller, Open Active Directory Users and Computers 17) Open the Security Group CSAdministrator and add the user who will be the Lync Administartor, in this document the Administrator account is used.
18) Chahla\Administrator is added and is now a member of CSAdministrator Group.
19) Install RTC Instance on SQL01.chahla.local
20) Open setup from the installation media. 21).Net Framework will be enabled.
22) Planning page. 23) Click on the Installation Menu, then select New Installation or add features to an existing installation.
24) Support files setup, click OK.
25) Accept the license terms, then click Next.
26) Check if you have errors, do not proceed until you fix them, otherwise click Next. 27) Select SQL Server Feature Installation, then click Next. 28) From the list of features select Database Engine Services, Management Tools-Basic, Management Tools Complete,
browse where you want to install, then click Next. 29) In the Instance Configuration, select Named Instance and name it RTC, then click Next.
30) Create Service Account for this step, SQLAdmin Account is created and used in this document. 31) Select Windows Authentication Mode, then Add the Users that you want to Grant them Unrestricted Access to the Database Engine, here Administrator and SQLAdmin is added click Next.
32) Click Install.
33) Done. 34) Install Monitoring & Archiving DB instances on SQL02.chahla.local
35)
36) Named Instance: LyncMonitoring (any name)
37) 38) Another new installation, Named Instance: LyncArchiving (any name)
39) Allow access to some ports in each SQL Server On SQL-01, open SQL Server configuration Manager. 40) Click on Protocols for RTC, right click TCP/IP and hit Properties.
41) Click on the IP Addresses tab, then at the bottom of the list you will see the TCP Dynamic Ports value used by RTC Instance. (49279 in my case)
42) Open Windows Firewall, and click New Rule. 43) Select Port, then click Next.
44) Select TCP, type the port number that you obtained in the previous step (49279), then click Next. 45) Allow the connection, click Next.
46) Apply it to all profiles, click Next. 47) Give it any name, then click Finish.
48) On the same Server open Port UDP 1434 that is used by SQL 49) Do the same on SQL-02 for the other two Instances (LyncMonitoring & LyncArchiving) for LyncMonitoring.
50) Port is 49292 in my case.
51) Allow it in the Firewall.
52) Give it a name.
53) For LyncArchiving.
54) Port is 49345 in my case. 55) Allow it in the Frewall.
56) Give it a name. 57) Also, do not forget to allow UDP 1434.
Add the required DNS Records, create new Host (A or AAA) 58) Create Meet, Admin and Dialin Host A Records use the IP Address of the first Front-end Server: Meet.chahla.local Admin.chahla.local
Dialin.chahla.local
59) Create a Service Location Record (SRV), right click and select Other New Records
60) Select Service Location (SRV).
61) Service: _sipinternaltls Protocol: _tcp Port Number: 5061 Host: pool01.chahla.local 62) Create Lync File Share here it is on on DC-01.chahla.local 63) Share the Folder.
64) Permissions: Everyone (Read) permission level, and the RTCComponentUniversalServices, RTCHSUniversalServices, RTCUniversalConfigReplicator, RTCUinversalServerAdmins (Read,Write) permission level. 65) Back to the first Front End Server, lync-fe01.chahla.local. Open the Deployment Wizard, and then click Install
Administrative Tools.
66) Create the Topology, open Lync Server Topology Builder.
67) Select New Topology, and then click OK. 68) Browse to the directory that you want to save the TBxml file, give it a name then click Save.
69) Create New Topology starts, click Next.
70) On the Specify additional supported domains click Next. 71) On the Define the First Site page, type the name and the description of the first site then click Next.
72) Specify Site details, and then click Next. 73) At the last page of defining your Topology, make sure the Open the new Front-End Wizard is checked, then click Next.
74) Front End Pool Wizard starts, click Next. 75) Select Enterprise Edition Front End Pool, type the Pool FQDN then click Next.
76) At this step, add the Front-End Servers then click Next. 77) Select the features that you want to enable then click Next. (Here are selected Archiving and Monitoring because they will be used later on)
78) If an Edge Server will be deployed, this is where you should define it.
79) Click New to define a new SQL Server Store. 80) Type the Server FQDN and the Name of the Instance then click OK.
81) Click Next. 82) Now define the File Store that was created and Shared before.
83) Select Define a new File Store, type the FQDN of the Server holding that Shared Folder, and the name of the Folder then click Next.
84) Here specify the External URL for the Web Services, here it will not be used externally, so keep it as is.
85) This step allows defining an Office Web Apps Server if one available.
86) Next, define a new Archiving and Monitoring Store. Select New.
87) Type the SQL Server FQDN, Select Named Instance, type the name of the instance and click OK. (if mirroring instance will be implemented check that option and type the port number there
88) The Archiving Store appears, click Next.
89) The same thing for Monitoring, New Store.
90) Server FQDN and Instance Name.
91) Store Appears, click Finish.
92) After finished the wizard edit the Administration URL. 93) Right Click to edit the properties of the Topology, click Edit Properties.
94) Click Simple URLs 95) In the Administrative Access URL type the Admin URL (https://admin.chahla.local in this case) and click OK.
96) Publish the Topology. 97) Click Next.
98) Click Next.
99) Click Next.
100) Succeeded with warning, we will see the warning details.
101) The warnings are because of the default settings of SQL Server, just ignore it.
102) Install Local Configuration Store & Lync Server Components on Lync-FE01 Open the Deployment Wizard, and click Install or Update Lync Server System
103) On the right side of Step 1 click Run.
104) Select Retrieve directly from the CMS, then click Next.
105) Step 1 completed, click Finish.
106) Step 2, Run.
107) Step 2 completed, click Finish. 108) Request and Assign Certificate, Step 3 click Run.
109) Click Request.
110) Select Send the request immediately to an online certification authority
111) Select your CA.
112) Click Next.
113) click Next.
114) Enter a Name for the Certificate, the Bit Length and click Next.
115) Fill in the Organization Name and Unit then click Next. 116) Fill in the Geographical Info and click Next.
117) Select your SIP DOMAIN, and then click Next.
118) Here you can add additional Subject Alternative Names.
119) Request completed, click Next.
120) Make sure the Assign this certificate to Lync Server is checked then click Next.
121) Certificate Assignment is completed, click Finish.
122) Open your browser and type the Admin URL or Pool URL then /CSCP, type your credentials and click OK.
123) You are done with the first FE Server.
124) Install Second Front End Lync-FE02.chahla.local (make sure you install the prerequisites same as FE01)
125) Install Local Configuration Store, then Lync Server
Components. 126) Then request or import a certificate. (you can import the certificate that you created for FE01 if you added the name of the second front end server in the certificate SAN and if you checked the option to make the key as exportable")
127) Request a Certificate.
128) Make sure you check the option Mark the certificate s private key as exportable, type the name then click Next.
129) Add the Second FE Server. 130) Make sure both Servers are listed, and then click Next.
131) Certificate Request is done, click Next. 132) Make sure Assign this certificate to Lync Server.. then click Finish.
133) Certificate Assignment Wizard opens.
134) Assignment is completed, click Finish.
135) Select OAuthTokenIssuer then click Assign.
136) Click Next to Assign. 137) Select the Certificate that you just created, you can View the Certificate here to confirm that you are selecting the correct certificate that has both Lync Servers listed in the SAN.
138) Review the summary, and then click Next.
139) Certificate Assignment is completed, click Finish. 140) Make sure you install the same Certificate on both Servers.
141) Next, start the Services.
142) Services successfully started. 143) The status at the Topology section in the Lync Control Panel showing all working as expected.