I’ve been asked many times in the past about what credentials should be entered and the short answer is to use a service account because this account will be granted required logon and database permissions to the database in order for it to access the database. **Note that as the wizard indicates, this will overwrite existing reports so be cautious of any SSRS reports that may already exist on the server.Įnter an account that will be used to access the Monitoring database: Select the appropriate SQL instance and define the SQL Server Reporting Services (SSRS) instance: With the databases created, proceed by launching the Deployment Wizard and click on Deploy Monitoring Report: Step #3 – Deploy Monitoring Reports on SSRS If you are not satisfied with the path in which the database and the log files are stored, you can use the following SQL queries to change the path after taking the database offline:įILENAME = 'D:\Database\QoEMetrics.mdf') Step #2 (Optional) – Move SQL database and log files to appropriate location You can, obviously, change this afterwards or at least have them on the correct drives. What I don’t like about this is that the database doesn’t get stored in the paths defined but rather in sub folders such as D:\Database\ArchivingStore\(default)\DbPath.
Selecting advanced will present the following menu: The Publish Topology wizard will present you with the option to either automatically let the wizard determine where to store the database or manually changing the path by going into the advanced options: The archiving SQL Server store and Monitoring SQL Server store should now have the new SQL server instance defined: Select the same or create a new SQL instance for the monitoring service then click OK: Step #1 – Define Archiving and Monitoring services on Front End Server / Pool Propertiesīegin by editing the properties of the front-end pool, navigate to the General properties and scroll down to the Associations section:Įnable the Archiving and Monitoring (CDR and QoE metrics) options:Įnter the FQDN of the SQL server that will be hosting the two databases when presented with the Define New SQL Server Store menu: Before I begin, note that the official planning documentation Monitoring can be found here:ĭeploy archiving for Skype for Business Serverĭeploy monitoring in Skype for Business Server Instead I'll be focused more on the various authentication approaches of the PowerShell module and Move-CsUser command.Deploying Skype for Business Server 2019 archiving and monitoring services are fairly much the same as the previous version but I thought it would be a good idea to write this updated post to demonstrate the process.
PASSSWORD REQUIREMENTS FOR SKYPE HOW TO
I'm not going to be documenting how to set up Hybrid as this is pretty well documented. Understanding of the requirements and limitations of getting these modules and commands to work in different circumstances.
I personally think that this information is critical when you’re trying to transition smoothly to the cloud and can end up being a painful trial-and-error Requirements are for making these commands work in more complex scenarios. They give few examples about what the practical Work in practice are not described in much detail in the Microsoftĭocumentation. The details about how these commands actually Has a highly secured Skype for Business deployment. I’ve been doing a deep dive recently on Skypeįor Business Online PowerShell and the Move-CsUser command for a customer that