Ok, this is a short post from the “John is slow file”.
Lets say you moved your SQL Server Reporting Services (SSRS) instance to a new server. You follow the ‘Installing Lync Server 2013 Monitoring Reports’ guidance to publish the new reports into Lync. You then go to Lync Sever Control Panel (CsCP – ? Cs.. 🙂 ) to verify the new ‘View Monitoring reports’ URL is visible and works and you discover GASP! the old URL(s) are still there. On that note, you will also notice that if you removed the monitoring server (Standard Edition Server, EE Pool) and published the topology, you may just see the old Service:ID and not the pool name.
So how to remove these old entries? Easy. Just Bing ‘Remove Lync Monitoring URL’ and you will likely be referred to the ‘Set-CsMonitoringServer’ cmdlet. So, lets look at that guidance to get the current list of Monitoring Server URL’s.
First thing to note is that there is no ‘Get-CsMonitoringServer’ cmdlet, so the above article references to run ‘Get-CsService -MonitoringServer | Select-Object Identity’.
Lets try again.
Well thats not very helpful is it. It appears this worked in Lync 2010 but is no longer valid.
So now what?
It may have been obvious but apparently I missed the memo. In Lync 2013 we have the ‘Get\Set-CsReportingConfiguration cmdlet which work as you would expect.
Note the old URL’s.
Notice that the Service:1-MonitoringStore-5 ID has been removed. Reloading and verifying the Lync 2013 Control Panel we see that the link has been removed.
Again, this may have seemed obvious to some but I was thrown by the documentation a bit. In addition, there is a great post by Curtis Johnstone from May, 2013 outlining ‘5 Tips for Installing the Lync 2013 Monitoring Reports’ that was helpful to me in putting this together so thank you.
One thing to point out from his article is that if you are adding or changing a Reporting Services URL make sure that you set the full URL path to the LyncServerReports level, or the link in CsCP will take you to the Report Service home.
Hope this helps.