Section 1: Prepare Environment - Step 2: Create Enterprise Pool

By -
Section 1: Prepare Environment
Step 2: Create Enterprise Pool

Click on Run on Step 2.




Click Next on splash screen. Under Pool name we give the DNS address we set up as part of prerequisites for our Pool Name, as we will use only one server the DNS name points to the server IP, if we used multiple servers it would point to the IP of the HARDWARE load balancer placed in front. (NOTE: You cannot use Microsoft NLB).

We also enter our domain name (e.g. mgdomain.ie) and pool FQDN (Fully Qualified Domain Name) which should update itself once domain and pool name are in place.

For SQL Instance we enter the SQL server DNS name (e.g MGSQL01). Click Next  to continue.

The pool creation starts, now we will be prompted for an internal and external web farm FQDN. This is the name of the pool internally and externally (If you are implementing external access). You can do the external one at a later time. Click Next.



We are now prompted the Database page, I selected to reuse any existing databases as this is the first install. If a SQL server already exists do not check this option, click Next.


Now we are prompted for locations for ourr Backend Database logs. These are created on the SQL server (MGSQL01), so choose your drives correctly here. Before we click Next we need to create some shares manually for our Conferencing content.

Creating File Shares

Because our Universal Groups have been created, we can now create file shares that are necessary for the following functions:

·         Presentations - Meeting presentations to be downloaded or streamed by conference attendees.

·         Metadata - Meeting information (metadata) that is used internally by the Web Conferencing Server component for the pool.

·         ABS - Address Book information that is used by the Address Book Server, which is included with the Web Components Server, in order to provide global address list information to Office Communicator 2007 and Office Communicator 2005 clients on a daily basis.

·         MeetingCompliance (optional) - Meeting activities and content uploaded during meetings.  We will talk about how to enable Meeting Compliance in a future Part.

These shares can be created on a File Server in your environment.  We will be creating these shares on our OCS FE Server which means that our OCS Server will also be our Web Components Server.

We will create a folder called C:\OCS on our OCS Front End Server (MGOCSFE01).  Within those four folders, we will create the following four folders:

·         Presentations

·         Metadata

·         ABS

·         MeetingComp

·         ClientUpdate

·         ApplicationData



Each of these folders will need to be shared out.  We will use a share name that matches the folder name for simplicity sake.  Grant Full Control on each of these shared folders to the administrator, the RTCUniversalServerAdmins group, and any other user or group responsible for creating pools. Remove Read permission from the Everyone group, you need to add the RTCComponentUniversalServices group to the permissions as well with Full Control. The Presentations needs to allow Everyone read permissions in order for people to download uploaded content to Live Meeting.

Make sure you provide both RTCUniversalServerAdmins and Administrators Full Control via NTFS permissions as well.  Because our folders are in the OCS folder, we can add these permissions on C:\OCS and they will flow down to our sub folders through inheritance.



Now we continue and put in the UNC path to the shared directories we just created. I have used the default naming in all the above paths. Click Next in both cases.


Now we get the option to enable CDR (Call Detail Recording), we can change this later anyway. Click Next to this and the review settings.



When completed you can review the logs and click Finish when done.


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", how...
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 thi...
Read more