Office Communications Server 2007 R2 Setup - Pre Install

By -
It took sometime for me to get my head around setting up OCS r2 properly in a live environment. While doing this I learned many things so I decided to keep a step-by-step guide updated as I went along and it can be used for future installs. The details in this guide should be used as a guide as it is a living document it can and does change when other issues are found :)

********************************************

Walkthrough for OCS 2007 R2

This is a click-by-click guide to installing Office Communicator Server 2007 R2 Enterprise Edition.

This example was installed in a virtual lab using VMware ESX 3i (This is unsupported by Microsoft but it does work – You will have issues with sound quality; so for testing and learning purposes only).

This document installs OCS R2 Enterprise Edition Front-End in a consolidated configuration (All roles on one server), a stand alone CWA server (Which also hosts the monitoring server), a consolidated Edge server and a standalone SQL 2005 SP2 server. This is the method which uses the fewest possible hardware servers.

All servers are built on Windows 2003 Enterprise Edition x64.

Prerequisites:

Servers are all Windows 2003 ( 64Bit ) with SP2 and fully patched -  media should be available.

SQL  server should be minimum SQL 2005 SP2 or SQL 2008 (This doc uses SQL 2005 SP2)

Domain should be in place. This doc skips this part and assumes in place. Example domain here is MGDOMAIN.IE

An internal certificate server should be running (our example will use a cert server on MGDC01)

We also remove “Internet Explorer Enhanced Security” option from all servers in this lab.

IIS must be installed on DC (for Certs) and on Front End server.

Forest level  MUST be Windows 2003 NATIVE mode.

(Step 1) OU for OCS Servers must be created in AD with FE server in it. We use “OCS-Servers” for our example.

(Step 2) Pool name must be set up in DNS (we only have one server so pool name is mgocspool and points to 10.9.5.23)

AD must contain the users phone number in a Localised format e.g. +35311234567 in the Phone field under General Tab.

Servers used in example:

Domain Controller           -              MGDC01                              -              10.9.5.21

SQL Server                          -              MGSQL01                            -              10.9.5.22

OCS Front End                   -              MGOCSFE01                       -              10.9.5.23

Mediation Server             -              MGOCSMED01                  -              10.9.5.24

Communicator Web       -              MGOCSCWA                      -              10.9.5.25

Exchange 2007                  -              MGEXCH07                         -              10.9.5.26

MX-ONE Phone System-                              MX-ONE                              -              10.9.2.10/11


Create the following accounts in AD before starting install:

RTCService

RTCComponentService

Passwords used for RTCxxxxx accounts should not use special characters like $ or *

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