Section 3: Deploy Other Server Roles - Communicator Web Access Server Install

By -

Section 3: Deploy Other Server Roles

Communicator Web Access Server Install

Next we will install CWA – Communicator Web Access
This cannot be co-located so we install it on its own server MGOCSCWA (along with monitoring server next)
NOTE: IIS must be installed prior to installation of CWA.
We must enter the following DNS entries before we begin:
·         New CNAME/Alias Record           -              as.mgocscwa à mgocscwa.mgdomain.ie
o   Used for Address Book download in CWA
·         New CNAME/Alias Record           -              download.mgocscwa à mgocscwa.mgdomain.ie
o   Used for Download of desktop sharing application in CWA

On MGOCSFE01/MGOCSCWA, request and install an MTLS certificate for CWA 2007 R2

The below is assuming you are using an internal Certificate Authority.
On your Front End server in the OCS Console right click the FQDN of the Front End server and select Certificate Wizard.
Ø  On the Welcome to the Certificate Wizard page, click Next. 
Ø   On the Available certificates tasks page, click Create a new certificate, and then click Next. 
Ø   On the Delayed or Immediate Request page, click Send the request immediately to an online certification authority, and then click Next. 
Ø  On the Name and Security Settings page, do the following: 
Under Name, enter a meaningful name for the certificate that this server will use for CWA communications. 
·         Under Bit length, select the 1024 bit length . 
·         Check the Mark cert as exportable check box. 
When you are finished, click Next. 
Ø  On the Organization Information page, type or select the name of your organization and organizational unit, and then click Next. 
Ø  On the Your Servers Subject Name page, do the following: 
·         In Subject Name, verify that the CWA Server FQDN is displayed. 
·         In Subject Alternate Name, Remove any entries listed
·         Do not check the Automatically add local machine name to the Subject Alt Name check box. 
 When you are finished, click Next. 
Ø  On the Geographical Information page, enter the Country/Region, State/Province and City/Locality. Do not use abbreviations. When you are finished, click Next. 
Ø  On the Choose a Certification Authority page, this wizard attempts to automatically detect any CAs published in Active Directory, do one of the following: 
·         Click Select a certificate authority from the list detected in your environment, and then click your certification authority (CA) in the list. 
·         Click Specify the certificate authority that will be used to request this certificate, and then type the name of your CA in the box, using the format \CA instance>. For example, CA.contoso.com\CAserver1. If you type an external CA name, a dialog box appears. Type the username and password for the external CA, and then click OK. 
When you are finished, click Next. 
Ø  On the Request Summary page, review the settings that you specified and then click Next. 
Ø  On the Certificates Wizard completed successfully page, DO NOT click Assign. 
Ø  Click Finish.
Ø  Open MMC and add Certificate Snap-in for local computer on Front End server (MGOCSFE01).
Ø  Expand Personal/Certificates and right click the certificate you just generated and export with the private key.
Ø  Copy this file to the CWA server (MGOCSCWA).
Ø  Open MMC and add certificate snap-in for location computer.
Ø  Expand Personal/Certificates. Right click on certificates folder and select All Tasks/import.
Ø  Browse to where you copied the exported certficate (change file type to .pfx or all) and select it. OK to complete.
Ø  You should now be able to select it in the CWA interface and apply later in this stage.
Click on Deploy Communicator Web Access

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