It looks like the documentation for configuring the reporting services for Lync are wrong on the TechNet site.
The article is located here, and mentioned the connection string to be "Data source=(local)\archinst;FailoverPartner=atl-mirror-001\archinst;initial catalog=LcsCDR"
When you change the value to be the correct settings for your environment, I was getting a "Keyword not supported" error as seen below.
After a quick Google search, found an article on Doug Dietterick's Blog, Issue Deploying Lync Server 2013 Monitoring Reports to SQL Mirror.
It turned out to be that the keyword "FailoverPartner" is actually two words "Failover Partner". Once this was updated connection was all good.
Landis Attendant Console Install
Attempting to setup a test tenant with access to Landis Attendant Console, and was getting errors around granting access to the tenant. The ...
-
Using the Office 365 IP Address and URL Web service to pull the latest information. The website above has all the listed parameters that...
-
This has been bugging me for awhile, I wasn't able to assign a number to a resource account that had been created for a Teams AA or CQ. ...
-
Set the LineURI for a user using calling plans (Telstra Calling) 1. Need the location ID Get-CsOnlineLisLocation 2. Set-CsOlineVoice...