After few busy weeks, I finally found few hours to play with my lab. This time I will install Achieving and Monitoring roles of my Lync environment.
While Archiving pretty much depends of your company policy requirements, Lync admin MUST install Monitoring, especially if Enterprise Voice is deployed. Monitoring collects not only CDR (Call Detail Record), but also Quality Metrics for every call.
I have MS SQL server already setup on machine with FQDN sql01.lynclog.com. I created a named instance for my roles (I intend to co-locate the databases) called ARCMON.
First, I will add my instance to the SQL store in Topology Builder.
Next, I will add the Monitoring and Archiving roles…
…select the pre-defined SQL Store…
…and associate my server(s) with it
Next, will do so for the Archiving role as well.
It is highly recommended to use a dedicated share for Archiving, typically on the SQL server itself. I could use the file share defined for my first server:
…but what if later for some reason this server is decommissioned? In this case, this would break the Archiving of all servers I could have at later stage. So, I will create a file share on my SQL server right now…
…and use it in Topology Builder.
Last step – Publishing the topology and examining the To-Do-List.
I will now run Lync Installation media on the SQL server.
At this point, I will verify that the databases are installed using SQL Management Studio
***Note that in the line “SQL Server Reporting Services (SSRS) instance” I will use the FQDN of the SQL server (and not the default FQDN\INSTANCE as it was offered), because I configured my ReportServer to run on the default instance only.
Last step will be to open the report Server URL and verify LyncServerReports are available.
Of course, to enable Archiving, more configuration is needed, but this is outside of the scope of this post