Loading…

Andrew J. Price | Technical Blog

Office Servers and Services MVP | Founder of UC and Cloud Day | Founder of Microsoft Cloud User Group

“Watching” your Skype for Business 2015 with Watcher Nodes Part 1 – Installation and Configuration

Hello Readers

With the release of the Skype for Business 2015 Management Pack its time to release an updated blog post which looks at the following

  • Part 1 – Installation and Configuration
  • Part 2 – Configuring Video Interop Server Synthetic Transaction

First of all dependencies;

  • Skype for Business 2015 Deployment
  • System Center Operations Manager 2007 R2 or Higher
  • Windows Server 2008 R2 or Higher for your Watcher Node
  • Skype for Business 2015 Management Packs installed
  • SCOM Agents deployed to the Watcher Nodes
  • 2 Skype for Business enabled Accounts
  • Windows PowerShell Module for Lync Online installed on Watcher Node

In this blog post I will presume you have installed the SfB Management Pack and deployed agent(s) to your Watcher Node.

 

First thing to note is that you require the following specification for the Watcher Node(s)

CPU

One of the following:

  • 64-bit processor, quad-core, 2.33 GHz or higher
  • 64-bit 2-way processor, dual-core, 2.33 GHz or higher

Memory

  • 8 GB

Network operating system

  • 1 network adapter 1 Gbps
  • Windows Server 2008 R2, Windows Server 2012, or
    Windows Server 2012 R2

Windows Features

  • The full version of .NET Framework 4.5.
  • Windows Identity Foundation.
  • Windows PowerShell 3.0.
  • Windows Server Desktop Experience (This is a new requirement for the Watcher Node and will be explained later in this two post)
  • Unified Communications Managed API (UCMA) (This is a new requirement for the Watcher Node and will be explained later in this two post)

 

Once you have met the specification above, insert your Skype for Business 2015 Server ISO.

image

Tick Don’t check for updates right now (At time of this blog no updates was available) –> Press Install

image

Tick I accept the terms in the license agreement –> Press OK

image

You should now receive the above window. We now need to move to the Front End Server or any Server that has the Skype for Business Management Shell as we need to make a New Trusted Application Pool for the Watcher Node.

Enter New-CsTrustedApplicationPool -Identity “Your Watcher Node Name” -Registrar “Your Lync Pool Name” -ThrottleAsServer $True -TreatAsAuthenticated $True -OutboundOnly $False -RequiresReplication $True -ComputerFqdn “Your Watcher Node Name” -Site “Your Lync Site Name

image

We now need to enter New-CsTrustedApplication –ApplicationID “must match Idenitity” –TrustedApplicationPoolFqdn “Your Watcher Node Name” –Port 5061

image

Type Enable-CSTopology

We now need to go back to the Watcher Node and Skype for Business 2015 Deployment Wizard

image

Click Install or Update Skype for Business System

image

Click Run and Press Next

image

Press Finish

image

Click Run and Press Next

image

Press Finish

image

Click Run and Press Request

image

Type

  • Friendly Name
  • Organisation
  • Organisation Unit

Select

  • Country/Region

Type

  • State/Province
  • City/Locality

Press Next

image

Press Next

image

Press Next –> Press Finish

image

Press Next

image

Press Next –> Press Finish –> Press Close

image

Press Run

image

Check your service have started if not launch Powershell and type Start-CsWindowsService -verbose

image

We now need to install the WatcherNode.msi which comes with the Skype for Business 2015 Management Pack. If you have got this to hand you can download from http://www.microsoft.com/en-us/download/details.aspx?id=47364

Once you have the .msi file we need to install Ive Command Prompt or Powershell then enter the following commands

use the CD / command to go to the folder with the WatcherNode.msi we then need to type

.\WatcherNode.msi Authentication=TrustedServer

Please Note: Command Authentication=TrustedServer is case-sensitive as shown below

image

Press Enter

image

Tick I accept the terms in the Licence Agreement –> Press Install

image

Press Finish

This completed the installation side of the Skype for Business Watcher Node

1)

2) Configure Synthetic Transactions

From the Watcher Node you need to launch Skype for Business Management Shell or Windows Powershell will do. Enter the following command

Set-CsTestUserCredential -SipAddress “sip:svc.watch1@lyncme.co.uk” -UserName “lyncme\svc.watch1” -Password “Welcome1”
Set-CsTestUserCredential -SipAddress “sip:svc.watch2@lyncme.co.uk” -UserName “lyncme\svc.watch2” -Password “Welcome1”

New-CsWatcherNodeConfiguration -TargetFqdn “fe01.lyncme.local” -PortNumber 5061 -TestUsers @{Add= “sip:svc.watch1@lyncme.co.uk”,”sip:svc.watch2@lyncme.co.uk”}

TargetFqdn needs to be you Lync Pool and you will need a minimum of two test users

As you can see from below Watcher has now been enabled for all the services that are available in my Lync.

image

Its worth noting that Microsoft have implemented a few new transactions you can compare the Skype Transaction to the Lync Transactions below

image

This post was based on Trusted Server Authentication there are more additional commands for Credential Authentication

8 thoughts on ““Watching” your Skype for Business 2015 with Watcher Nodes Part 1 – Installation and Configuration

  1. “In this blog post I will presume you have installed the SfB Management Pack and deployed agent(s) to your Watcher Node.”

    Is this part a big deal? I have never managed to have a fully working SCOM deployment with mgmt packs not even in my LAB env, something regarding service accounts or SPNs want totally OK and it never discovered my Lync server successfully. So if thats more than a next-next finish and requires masters degree in nuclear physics, I wont have many use of this article then 🙁

    1. Thanks, seems this was missed. I never had the time and patience to understand the essence of SCOM, it was always as a side-project to put the actual deployment into the customers SCOM in order to have them happy and stop complaining, but never knew exactly what I was in fact really doing when I was clicking through the mazes of the SCOM mgmt GUI.

Leave a Reply