Tuesday 15 January 2013

Lync Server 2013 Monitoring/Archiving

There is no longer separate roles for Monitoring or Archiving.

Each front-end server communicates directly with the monitoring and/or archiving database, eliminating the need for a separate monitoring/archiving server.

Follow my previous post to define and install the SQL Instances LyncMonitoriny & LyncArchiving and to associate them to a pool in the Topology builder.

 http://mchahla.blogspot.com/2013/01/installing-microsoft-lync-server-2013.html

 

I will install the Databases on SQL-02.chahla.local

 

- Open Lync Server Management Shell (if you don’t have it ,Open the installer and install Lync Server 2013 Core Components) and Run this command:

Install-CsDatabase -LocalDatabases

008

- Click Deploy Monitoring Reports.

012

- Select the Monitoring Database and type the SQL Server Reporting Services instance, then click Next.

013

- Specify the credentials, then click Next.

014

- Specify the Read-Only Group, then click Next.

015

 016

 017

- Reports will be published.

018

 019

 020

- Successfully deployed.

021

- To Access the LyncMonitoring Reports, from a browser type the URL http://localhost/Reports_LyncMonitoring if you are accessing from the same machine, otherwise if you are accessing from another machine replace localhost by the machine fqdn >> sql-02.chahla.local

022

- Click on LyncServerReports.

023

- Click on Reports Home Page.

024

- A list of available reports will show.

025

- This is one of the reports.

026

You will see the records are filled after some time when the users start some sessions.

027

 

For Archiving, create a policy and enable archiving.

033 

- Apply it to some users.

 034

- To access LyncArchiving open it in SQL Management Studio.

009

- (localhost)\LyncArchiving.

010

011

- The table dbo.Messages has all the IM messages.

 028

- Right click >> Select top 1000 rows.

029

- In the Results> Body Column, Right click at any row and select copy, then paste it in a notepad.

030

031

- Rename the notepad txt file to html file and open it.

032

- Or you can simply use the command Export-CsArchivingData to export the data that will be in the .eml extension , rename the file to .mht to view it in a browser.

Check this article for more detailed info about exporting archived data  http://technet.microsoft.com/en-us/magazine/hh328432.aspx

 

Done.

Sunday 13 January 2013

Installing Microsoft Lync Server 2013 Enterprise Pool on Windows Server 2012

I will be installing an enterprise pool that consists of two Front-End Servers.
Servers :
   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.
- Open the installation media, Microsoft Visual C++ 2012 Redistributable will be installed when you launch the installer.
- Browse to the location where you want to install and click Install.
001
- Accept the EULA.
002
- Core components will install.
003
005
- Lync Server 2012 – Deployment Wizard will appear.
004
- The first thing that we will do is to Prepare Active Directory. Click Prepare Active Directory.
006
- On the right side of Prepare Schema, click Run.
007
 008
- Click Next.
 009
 010
- Schema preparation finishes, click Finish.
 011
  - On the right side of Prepare Current Forest, click Run.
012
- Click Next.
 013
- Select Local Domain, then click Next.
 014
 015
- Forest preparation finishes, click Finish.
 016
- On the right side of Prepare Current Domain, click Run.
017
 018
 019
- Domain preparation finishes, click Finish.
 020
 021
- Add users to provide administrative access
On the Domain Controller, Open Active Directory Users And Computers
022
- Open the Security Group CSAdministrator and add the user who will be the Lync Administartor, i am using the Administrator account for this.
023
 024
- Chahla\Administrator is now a member of CSAdministrator Group.
 025
- Install RTC Instance on SQL01.chahla.local
- Open setup from the installation media.
026
- .Net Framework will be enabled.
027
- Planning page.
 028
- Click on the Installation Menu, then select “New Installation  or add features to an existing installation”.
 029
- Support files setup, click Ok.
 030
- Accept the license terms, then click Next.
 031
 032
- Check if you have errors, do not proceed until you fix them, otherwise click Next.
 033
- Select SQL Server Feature Installation, then click Next.
 034
- From the list of features select “ Database Engine Services, Management Tools-Basic, Management Tools –Complete” , browse where you want to install, then click Next.
 035
 036
- In the Instance Configuration, select “Named Instance” and name it RTC, then click Next.
 037
 038
- You can create service account for this step, i created sqladmin account.
 039
- Select Windows authentication mode, then add the users that you want to grant them unrestricted access to the Database Engine, i added Administrator and SQLAdmin, click Next.
 040
 041
- Click Install.
 042
 043
- Done.
 044
- Install Monitoring & Archiving DB instances on SQL02.chahla.local
045
 046
- Named Instance: LyncMonitoring (any name)
 047
048
- Another new installation, Named Instance: LyncArchiving (any name)
 049
- Now you have to allow access to some ports in each sql server
On SQL-01, open SQL Server configuration Manager.
050
- click on Protocols for RTC, right click TCP/IP and hit Properties.
 051
- 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)
 052
- Open Windows Firewall, and click New Rule.
 053
- Select Port, then click Next.
 054
- select TCP, type the port number that you obtained in the previous step (49279), then click Next.
 055
- Allow the connection, click Next.
 056
- Apply it to all profiles, click Next.
 057
- Give it any name, then click Finish.
 058
- On the same server you have to open port UDP 1434 that is used by SQL
 059
We will do the same on SQL-02 for the other two Instances (LyncMonitoring & LyncArchiving)
- for LyncMonitoring.
 060
- Port is 49292 in my case.
 061
- allow it in the firewall.
 062
- give it a name.
 063
- For LyncArchiving.
 064
- Port is 49345 in my case.
 065
- Allow it in the firewall.
 066
- Give it a name.
 067
- Also don’t forget to allow UDP 1434.
 068
Now we will add some required DNS Records, create new Host (A or AAA)
069
- Type the name and the IP Address of the first Front-end Server, do this for:
meet.chahla.local
admin.chahla.local
dialin.chahla.local
pool01.chahla.local
070
- Now we will create a Service Location record (SRV), right click and select “Other New Records…”
071
- Select Service Location (SRV).
072
 073
- Service: _sipinternaltls
Protocol: _tcp
Port Number: 5061
Host: pool01.chahla.local
074
- The Next step is to create Lync File Share
i will create mine on DC-01.chahla.local
 075
- Share the folder.
 076
- Give Everyone (Read) permission level, and the RTCComponentUniversalServices, RTCHSUniversalServices, RTCUniversalConfigReplicator, RTCUinversalServerAdmins  (Read,Write) permission level.
 077
- Back to the first Front End server, lync-fe01.chahla.local.
Open the Deployment Wizard, then click Install Administrative Tools.
078 079
- Next, we will create the Topology, open Lync Server Topology Builder.
080
- Select New topology, then click OK.
 081
- Browse to the directory that you want to save the tbxml file, give it a name then click Save.
 082
- The Create New Topology starts, click Next.
 083
- On the “Specify additional supported domains” click Next.
 084
- On the “Define the first site” page, type the name and the description of your first site then click Next.
 085
- Specify site details, then click Next.
 086
- At the last page of defining your topology, make sure the “Open the new Front-End Wizard” is checked, then click Next.
 087
- Front End pool wizard starts, click Next.
 088
- Select “Enterprise Edition Fron End Pool”, type the Pool FQDN then click Next.
 089
- At this step, add your FE servers then click Next.
 090
- Select the features that you want to enable then click Next. (i selected Archiving and Monitoring because i will be using later on)
 091
 092
- If you will use an Edge server, this is where you should define it.
 093
- Click “New” to define a new SQL server store.
 094
- Type the Server FQDN and the Name of the instance then click Ok.
 095
- Click next.
 096
- Now define the File store that you created and shared before.
 097
- 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.
 098
- Here you can specify the External URL for the Web Services, i am not going to use it externally, so i will keep it as is. 099
- This step to define an Office Web Apps Server if you have one.
 0100
- Next, i will define a new Archiving and Monitoring Store for later on use.
Select New.
 101
- Type the SQL Server FQDN, Select “Named Instance”, type the name of the instance and click OK. (if you are mirroring your instance you can check that option and type the port number there”
 102
- the archiving store appears, click Next.
 103
- The same thing for Monitoring, New store.
 104
- Server FQDN and Instance Name.
 105
- Store appears, click Finish.
 106
- After you finished the wizard you need to edit the Administration URL.
 107
- Right Click to edit the properties of your topology, click Edit Properties.
 108
- Click “Simple URLs”
 109
- in the “Administrative access URL” type the admin URL (https://admin.chahla.local in my case) and click OK.
 110
- Then Publish the Topology.
111
- Click Next.
 112
- Click Next.
 113
- Click Next.
 114
 115
 116
 117
 118
 119
 120
- Succeeded with warning, we will see the warning details.
 121
 122
- the warnings are because of the default settings of SQL Server, you can simply ignore it.
 123
 124
 125
- Next step is to Install Local Configuration Store & Lync Server Components on Lync-FE01
Open the Deployment Wizard, and click “Install or Update Lync Server System”
126
- On the right side of Step 1 click Run.
127
- Select “Retrieve directly from the CMS,,,,” then click Next.
128
 129
 130
- Step 1 completed, click Finish.
131
- Step 2, Run.
132
 133
 134
- Step 2 completed, click Finish.
135
- Now we need to Request And Assign Certificate, Step 3 click Run.
 136
- Click Request.
 137
 138
- Select “Send the request immediately to an online certification authority”
 139
- Select your CA.
 140
- click Next.
 141
- click Next.
 142
- type a Name for your Certificate, select the Bit Length and click Next.
 143
- Fill in the Organization name and unit then click Next.
 144
- Fill in the Geographical info and click Next.
 145
 146
- Select your sip domain, then click Next.
 147
- Here you can add additional Subject Alternative Names.
 148
- the request is completed, click Next.
 149
- Make sure the “Assign this certificate to lync Server ,,,,” is checked then click Next.
 150
 151
 152
 153
- Certificate Assignment is completed, click Finish.
 154
 155
- Open your browser and type the admin url or pool url then /cscp , type your credentials and hit OK.
 156
- You are done with the first FE server.
 157
- Install Second Front End Lync-FE02.chahla.local   (make sure you install the prerequisites same as FE01)
158
- Install Local Configuration Store, then Lync Server Components.
159
- 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")
160
- Request a certificate.
161
 162
 163
 164
 165
- Make sure you check the option “ Mark the certificate’s private key as exportable”, type the name then click Next.
166
 167
 168
 169
 170
- Add the second FE server.
171
- Make sure both servers are listed, then click Next.
 172
- Certificate Request is done, click Next.
173
- Make sure “Assign this certificate to Lync Server …..” then click Finish.
174
- Certificate Assignment wizard opens.
 175
 176
- Assignment is ok, click Finish.
177
- Select OAuthTokenIssuer then click Assign.
178
- Click Next to Assign.
179
- 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.
180
- Review the summary, then click Next.
181
- Certificate Assignment is completed, click Finish.
182
- Make sure you install the same certificate on both servers.
 183
- Next, start the services.
184
- Services successfully started.
185
- And you can see the status at the Topology section in the Lync Control panel.
186

Done.