BlackBerry Enterprise Instant Messaging is not functional with Microsoft Office Communications Server 2007 R2

By -

BlackBerry Enterprise Instant Messaging is not functional with Microsoft Office Communications Server 2007 R2


Environment

  • BlackBerry® Enterprise Server software version 4.1 Service Pack 6 (4.1.6) or later for Microsoft® Exchange
  • Microsoft® Active Directory®
  • Microsoft® Office Communications Server 2007 R2
  • Microsoft Office Communications Server 2007
  • Microsoft® Office Communicator 2007 R2
  • Microsoft Office Communicator 2007
  • Microsoft® Office Communicator Web Access 2007
  • Windows Server® 2003 R2 64-bit bit edition
  • Windows Server 2003 R2 32-bit edition
  • SDR271303


Overview

In Microsoft Office Communications Server 2007 R2, the Asynchronous JavaScript® and XML (AJAX) AJAX application programming interface (API) is no longer being supported by Microsoft. The Unified Communications (UC) AJAX SDK that is available through the Microsoft Office Communicator Web Access 2007 server will not be re-released by Microsoft in Microsoft Office Communicator Web Access 2007 R2 or in future releases.

If you are planning to install Microsoft Office Communications Server 2007 R2, the unsupported AJAX API impacts the BlackBerry Enterprise Server for Microsoft Exchange for instant messaging implementation against Microsoft Office Communications Server.

Once Microsoft Office Communications Server 2007 R2 is installed, you cannot integrate your instant messaging environment with the BlackBerry Enterprise Server.

Instant messaging with Microsoft Office Communications Server 2007 R2 is compatible with the BlackBerry® Collaboration Service and the BlackBerry® Client for use with Microsoft® Office Communications Server 2007 only if the workaround as described below is implemented.



Workaround

RIM, in conjunction with Microsoft, has documented a workaround that must be implemented to allow BlackBerry smartphone users to continue using the enterprise instant messaging application.

If you update your Microsoft Office Communications Server 2007 to R2, you must leave the Microsoft Office Communicator Web Access 2007 servers at R1 for continued communication with the BlackBerry Enterprise Servers.

For more information on the removal of AJAX API support, search the Microsoft support web site for knowledge base article 969336.

Prerequisites

  1. Configure two servers in the same domain as follows:
    • On server 1, install Windows Server 2003 R2 32-bit edition
    • On server 2, install Windows Server 2003 R2 64-bit edition
  2. Verify that you have an existing Mutual Transport Layer Security (MTLS) certificate, or create a new MTLS certificate.

Note: You must install Microsoft Office Communicator Web Access 2007 in the domain before you install Microsoft Office Communications Server 2007 R2. If you install Microsoft Office Communications Server 2007 R2 first, the installation of Microsoft Office Communicator Web Access 2007 fails.

Tasks - server 1

On server 1, perform the following actions:

  1. Using the deployment wizard in Microsoft Office Communications Server 2007, configure Microsoft Active Directory.
  2. Using the deployment wizard in Microsoft Office Communicator Web Access 2007, use the MTLS certificate to install, create, and activate a virtual Microsoft Office Communicator Web Access 2007 server.

    Note: You can ignore the requirement in the deployment wizard that states that you must have already installed and deployed Microsoft Office Communications Server 2007.

  3. Type the following web address in your browser to access Microsoft Office Communicator Web Access 2007:

    http://<server1>:81/

    where <server1> is the computer name of server 1.

    Note: If the error message Error 401: Unauthorized Access displays, your web browser might be sending an Internet authentication header field that the web server cannot accept. In this case, perform the following actions:

    1. On server 2 or from the domain controller, click Start > Run.
    2. Type dsa.msc.
    3. Using Microsoft Active Directory, add the existing CWAService user name to the RTCUniversalServerAdmins user group.
    4. On server 1, click Start > Administrative Tools.
    5. In Computer Management, restart the World Wide Web Publishing Service.
    6. Retry step 3.

Tasks - server 2

On server 2, perform the following actions:

  1. Using the deployment wizard in Microsoft Office Communications Server 2007 R2, configure Microsoft Active Directory.
  2. Install Microsoft Office Communications Server 2007 R2.

    Note: You can ignore warnings related to log components or a failure to start services if only the Monitoring Agent in Microsoft Office Communications Server 2007 R2 fails to start.

  3. In the directory where you installed setupse.exe or setupee.exe, from the setup subdirectory, runadmintools.msi. The Communications tab for users is accessible in both Microsoft Active Directory and the Microsoft Office Communications Server 2007 console.
  4. In Microsoft Active Directory, create SIP user IDs that are enabled for Microsoft Office Communications Server 2007 R2.
  5. Install Microsoft Office Communicator 2007 R2.
  6. Using a SIP user ID, connect to Microsoft Office Communications Server 2007 R2.
  7. Using the Microsoft Office Communications Server 2007 console, in Front End Server Properties, on the General Tab, add TCP port 5060 to connections.

On server 1, type the following web address in your browser to access the virtual Microsoft Office Communicator Web Access 2007 server:

http://<server1>:81/

where <server1> is the computer name of server 1.

Sign in with a SIP ID.

Post-requisite: You can also install Microsoft Office Communicator 2007 or Microsoft Office Communicator 2007 R2 on server 1 to verify connectivity and sign in.

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