Section 3: Deploy Other Server Roles - Monitoring Server

By -
Section 3: Deploy Other Server Roles

Monitoring server Install

Next we will install the Monitoring server, this role can be installed on its own or collocated on another server as it does not use much processing or memory at all and simply gathers information only. (For this example we will install it on the MGOCSCWA server).
Before we install Monitoring Server MSMQ (Microsoft Messaging Queue) must be installed on this server. This can be done through Add/Remove Windows Components (Under Application Server). MSMQ must also be installed on all servers being monitored (IE. Front End servers)
On MGOCSCWA open the installer program for OCS and choose Deploy Other Server Roles



We choose Deploy Monitoring Server from the list.




Step 1: Install files for Monitoring Server




Click on Install here to begin.



Accept the licence agreement and click Next. Select the install location and Next. Screen will return when completed successfully.

Step 2: Activate Monitoring Server



Click Run to start the activation section.



Click Next at the splash screen, Input details for RTCComponentService account and click Next. Enter the name of the SQL server in use for OCS (MGSQL01) and click Next.


Click Next without checking box, Input Folders used for log files on SQL box and click Next, review settings and click Next.


When finished review log and click Finish.
These warnings are ok as we do not have the CDR monitoring set up yet:

Step 3: Start Services


Click on Run to start.

Click Next to splash screen, choose steps to validate and click Next, When done review logs and click Finish.

Step 4: Deploy Monitoring Server Reports


Click Run on step 4 to start.

Click Next to splash screen, Enter a new account to be used for monitoring (RTCReportPack) and click Next. Enter a URL to be used for reports, use CWA server.
We must create the following account in AD before next step: RTCReportReaders and assign members to this group.

Select your domain and enter the Report Readers Group and click Next, review settings, Next Review log click Finish.
Our error because CWA Should be installed first.

Comments

Post a Comment

Popular posts from this blog

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", however it seems to take between 5-10 mins
Read more

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &
Read more

Skype for Business Edge Server replication troubleshooter

By -
Image
Many times in Skype for Business/Lync the main issue I come across is the deployment is that the edge server(s) fails to replicate. We see this when we run the command in Skype for Business Management Shell : Get-CsManagementStoreReplicationStatus and we see that the edge servers have False and no LastStatusReport or ProductVersion is shown as below. There are a number of things which can cause this and I am going to list them here. Try them in order here as this will contain the most common to the least common issues I found. Ø   Routing Ø   Firewall rules Ø   DNS suffix Ø   DNS (Local and LAN) Ø   Registry entries for SCHANNEL Ø   Certificates A check we can use to see if the replication is working can be done by trying to connect to the following URL from the Front End Server whish hosts the CMS: https://edgeinternalfqdn.domain.ie:4443/Replicationwebservice You should get the following screen: Without this response there is an issue,
Read more