MS Lync Backup Pool Setup

Now define Resiliency settings

This will do for Se2

Now Publish Topology

NEXT STEPS >> Install Database

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn se02.lab.local -SqlInstanceName rtc

THEN run Install or Update Setup/Update on SE1/SE2

WARNINGS
Can not update database XDS”

If you get a warning doing the above, May need to install SQL on SE2

install-csdatabase –centralmanagementdatabase –sqlserverfqdn se02.lab.local –sqlinstancename rtc

Command execution failed: Cannot find any suitable disks for database files. You must manually specify database paths.

Needs atleast 16GB free disk Space

CERTIFICATE ISSUE ON SE02

Add User to RTC Universal Server Admins Group

Update: Step 2

  • Also restarted computer before next step worked

Invoke the following command to on se1.lab.local so conferencing data is replicated:

  • Invoke-CSBackupServiceSync –PoolFqdn se01.lab.local  –

  • Invoke-CSBackupServiceSync –PoolFqdn se2.lab.local

^ Solution: RTCUniversalServerAdmin Group also ensure Deployment wizard has been completed

Configure second SRV record for New Se2.lab.local Server

  • Note higher priority

Check

Advertisements

Configuring LS2013 for Archiving

LSMS

Set-CsArchivingConfiguration -Identity Global -EnableArchiving ImAndWebConf -EnableExchangeArchiving $True

—> Result —>

Create Policy

Assigning users Archiving Policy

Grant-CsArchivingPolicy -Identity “Lync Jill” -PolicyName “London User Policy”

Setting Archiving Policy (Options NoArchiving|Uninitialized|UseLyncArchivingPolicy|ArchivingToExchange) for all in a pool

Get-CsUser -Filter {registrarpool -eq “se01.lab.local”} | Set-CsUser -ExchangeArchivingPolicy ArchivingToExchange  -verbo

BEFORE

AFTER

Get-CsUser | Where-Object {$_.ExchangeArchivingPolicy -eq “ArchivingToExchange”} | Select DisplayName

TESTING

Lync Archiving

Need Exchange

[conf] Can archive whiteboard and poll


1. Active Directory

Add user to RTC Universal Server Admins Group

NEW Certiificate


2. Exchange

Step 1: See if all is ok, is mailbox updating and ready for provisioning

Get-MailboxDatabase | select Name,*Provis*

Find Script

Run Script

cd ‘C:\Program Files\Microsoft\Exchange Server\V15\Scripts’

.\Configure-EnterprisePartnerApplication.ps1 -AuthMetadataUrl https://se01.lab.local/metadata/json/1 -ApplicationType Lync

IIS Reset

Get-ClientAccessServer | select name,AutoDisc*

3. Lync

Set-CsOAuthConfiguration -Identity Global -ExchangeAutodiscoverUrl “https://autodiscover.lab.local/autodiscover/autodiscover.svc

Now create partner application for Exchange

New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl “https://AutoDiscover.lab.local/autodiscover/metadata/json/1

Issue 1012

keep eye !!!! Really odd—>>>

 

Worked second time round

-new cert

Issue 1012

-restarted servers …

@Oauth both *.xml and *.svc work!

Ensure -identity Exchange the E is in capital !!

  • May need FE reset

Now Test

  • Ensure the Oauth is configured to correct URL

Exchange VM Not ringing

= “Secured” and restart Exchange services and FE

Prepare First SE server

It will check the pre-requisites

Checking prerequisite WMIEnabled…prerequisite satisfied.

Checking prerequisite NoOtherVersionInstalled…prerequisite satisfied.

Checking prerequisite SupportedOS…prerequisite satisfied.

Checking prerequisite PowerShell…prerequisite satisfied.

Checking prerequisite WindowsIdentityFoundation…prerequisite satisfied.

Checking prerequisite SupportedSqlRtc…prerequisite satisfied.

Checking prerequisite VCredist…prerequisite satisfied.

As part of this install the following will be installed

  • SQL Server 2008 Express Edition will be installed
  • RTC databases will be created and populated
  • Lync Server installation files will be put in place
  • Firewall exception for SQL Instance and SQL Browser

Have a look at the following processes

Deploy.exe

TrustedInstaller.exe

Setup.exe

SQLEXPR_x64.exe

Fluctuating CPU resources, and memory consumption grows = good

Deploy Monitoring Reports

Report: Response Group Usage Report published successfully with no warnings

Report: Response Group Call List Report published successfully with no warnings

http://SE1:80/ReportServer_MONITOR/Pages/ReportViewer.aspx?%2fLyncServerReports%2fReports+Home+Page” has been added to ReportingConfiguration.

Monitoring Reports have been successfully deployed.

http://se01.lab.local/ReportServer_MONITOR/Pages/ReportViewer.aspx?%2fLyncServerReports%2fReports+Home+Page

Separate SQL

The Monitoring Database is using SQL instance “sql01.lab.local\MONITOR”.

The data source is using SQL instance “(local)\MONITOR”.

Could not get objects from namespace root\Microsoft\SqlServer\ReportServer. The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Cannot get the ReportServerWebService URL. Verify that Reporting Services is deployed and configured properly on the target SQL instance:”sql01.lab.local\MONITOR”, and that WMI is included on the exception list of firewall setting on the server that is running Reporting Services.

Firewall

The Monitoring Database is using SQL instance “sql01.lab.local\MONITOR”.

The data source is using SQL instance “(local)\MONITOR”.

The following URL will be used for deployment: http://SQL01:80/ReportServer_MONITOR

Cannot access LcsCDR or QoEMetrics on Monitoring back-end database. Verify that these databases have been deployed, and that access to the Monitoring back-end database is not blocked by the firewall.

Solution

Restart server and + Run Deployment wizard, Step 2

Installing any collocated databases…

Executing PowerShell command: Install-CSDatabase -Confirm:$false -Verbose -LocalDatabases -Report “C:\Users\administrator.LAB\AppData\Local\Temp\2\Install-CSDatabase-[2015_01_18][17_39_50].html”

Installing Lync Monitoring Role

Pre-requsites

  • Server 2012
  • SQL 2008
  • Lync 2013

Step 1 Install Queing on SE1/sql

Step 2 Install SQL 2012

Monitoring Role requires full blown SQL, run SQL ISO

Setup Support Rules = OK,

Next | Next | Next

SQL Feature Installation | Next

Feature Selection. Below are the SQL features we need:

  • Database Engine Services
  • Reporting Services
  • SQL Server Books Online  (D:\x86\Setup\x86\SQL_BOL_Components)
  • Management Tools – Basic
  • Management Tools – Complete

>> NEXT

NT AUTHORITY\SYSTEM

Now run

Connect

Reporting Service Started ^

Now Associate in Topology builder & Publish

Finally Run the below command:

Install-CsDatabase –LocalDatabases

Lync Monitoring and Archiving

  • Deploying Architectures for M&A
    • LCS introduced CDR / Archiving
    • OCS2007 introduced monitoring
    • Only Archiving server can use Exchange server 2013 as alternative
    • Unlike previous versions neither roles require Ms Message Queue (MSMQ) to be installed
    • Defined in Topology Builder
  • Separate SQL instance required when performance of SQL server is critical
  • SE requires separate SQL server, not Express
  • Archiving creates LCSLOG
  • Monitoring creates 2 databases; LcsCdr, QoEMetrics (QoE information)
  • 64 bit SQL, SQL 2008/12 Standard/Enterprise
  • HA: 2010 – Critical mode archiving- FE services would shutdown if unable to archive
    • 2013 automatically arvhives this as it is collocated
    • Multiple FE, SQL instance mirrored config for BE
  • Policy Configuration
    • Reporting pack deployed into SQL repository services using deployment wizard
    • Accessing this data via SQL Query providing user has correct permission, can be achieved using any product that supports Open Database Connectivity (ODBC) to retrieve and manipulate data
    • Actual IM convo stored in RTF – may require additional manipulation before readable
    • MOS
      • G7.11 4.3
        RTAudio  4.1
        UC PSTN: RTAudio 2.95
        UC-PSTN Siren 3.72
        Conf Call G.722  4.3
        Conf Call Siren 3.72
  • TS L5 Designing HA and DR
CMS = Xds.ldf & Xds.mdf, Lis.ldf & Lis.mdf
Archiving and Monitoring – LcsCdr / QoEMetrics / LcsLog /
RGS  Cpsdyn / RGDConfig / RGSdyn

 

  • Monitoring & Archiving ALWAYS on FE
  • Collects and manages information from FE, Mediation and other server roles and stores in a DB separate to one used by FE
  • Leverages SQL server reporting services
  • Archiving Serves as legal compliance – now stored in Exch2013 central repository,
    • Following Content types: 1) P2P IM 2) Multiparty IM 3) Web Conference (incl Content and Events such as join, leave, upload etc) 4) AV for P2P IM & Web Conf 5) web conference annotations and Poll
  • Monitoring allows admins to collect trends and review quantative data on IM/A/V
    • Leverages MS Message Queueing technology to collect information & deposit in Monitoring Database
    • Uses SQL reporting services to display various canned and custom reports
    • During SQL install ensure reporting service box is checked
    • 4 distinct areas:
  1. System Usage
  2. Per call Diagnostic – great place for overall health of voice deployment
  3. Call reliability Diagnostic – deeper view of health – window into user experience
  4. Media quality Diagnostic –
  • Default reports: this week/6 weeks, monthly available available top right

 

  • Organisations must be concerned with the health and performance
  • Health & performance: should be top priority
  • Monitoring systems E2E enables admins to confidentially monitor all Lync modalities
  • Many organisations have KPI for Lync deployment
  • Monitoring health and performance of LS2013
    • Any organisation that has a designated SLA to lync system will require monitoring of all Lync components to ensure availability of environment
    • End goal: highest availability – highest level of insight in environment with least amount of effort for admins
    • Using perfmon to establish performance baselines
      • Every time new services are added new baseline should be established
  • Provides a solution for archiving IM & web conferencing coms to support compliance requirements
  • Collects numerical data about quality of network, participant details device names, drivers, IP add
  • QoE allows monitoring quality of real sessions
  • Call detail stats for monitoring usage trends help calculate organisation ROI

Archiving Service

  • New features
    • Co-location in FE
    • Exchange integration option
    • Searchable transcript of archived information
    • SQL store mirroring
  • 3x components
    • Unified data collection agents: agents activated/Installed on FE/SE, needs to be configured and activated
    • Archiving data storage: locations
      • Exchange server 2013 storage
      • SQL server storage

IM Archiving

  • When setting archiving for IM&C specify users
  • Archiving can be configured at global/site/pool(service) leve;s
  • Configure policies at global/site/user
  • Content That Is Archived
  • Content of peer-to-peer instant messages
  • Content of multiparty instant messages
  • Content of web conferences, including uploaded content (such as handouts) and events (such as joining, leaving, uploading, sharing, and changing visibility)
  • Whiteboards and polls shared during a conference
  • Content That Is Not Archived
  • Peer-to-peer file transfers
  • Audio/video for peer-to-peer and conferences
  • Content of desktop-sharing sessions
  • Content of application-sharing sessions

Monitoring Service

  • Collects performance metrics and provides reporting capabilities
  • You can use the QoE, CDR, and Capabilities offered by the monitoring service
  • Features
  • Voice over Internet Protocol (VoIP) calls
  • IM messages
  • A/V conversations
  • Meetings
  • Application sharing
  • File transfers
  • Error and troubleshooting
  • Components
    • Unified data collection store: CDR/QoE installed on every FE
    • Monitoring Databases: can be collocated or separate SWL
    • MS System Center Operation manager (SCOM) – monitoring (Optional)
    • Supported Database colocation
      • CDR (LcsCdr) + QoE database (QoEMetrics) share same SQL instance
      • Common for both monitoring db to be in same SQL as archiving db (LcsLog)