Martin Gibney - Microsoft Teams

Creating and assigning certificates on OCS 2007 R2 Edge Server So you now need to install certificates on the Edge server. The following is the correct method to do the following. In my scenario I have a server with 2 NICs - Internal: 192.168.41.200 External: 87.219.43.22 *********** Internal CA for the following Certificates: - A/V Edge Server role - Internal Connection Public Certificates for the following roles: - Access Edge (SIP) - Web Conferencing Role Internal Certificates can be created from this and should be done on the ROOT CA SERVER (as your edge server is not on the domain): · select “Create a new certificate” · Choose which Interface you will create for (Internal or A/V for these) · Prepare the request, and send immediately · Name: Logical name for your interface, use DNS name, also ensure Include client EKU is ticked · Fill in owner details · Cho

OCS Quality of Experience (QoE) While preparing my last post, I consolidated some quick facts about the QoE functionality that should benefit people who are considering deploying this role: 1. There is no additional server license (to your enterprise or standard license) required for this role. For OCS 2007, the role can be downloaded here . 2. In OCS 2007 R2, the QoE functionality and the Call Detail Record (CDR) functionality were merged into the OCS 2007 R2 Monitoring Role. 3. Supported OCS 2007 QoE Collocation: a. The OCS 2007 QoE Monitoring Server cannot be collocated with other Office Communications Server 2007 server roles. b. The OCS 2007 QoE SQL Database can be collocated with the QoE server, or installed on a dedicated server. 4. Supported OCS 2007 R2 Monitoring Role Collocation: a. A variety of collocation scenarios are supported depending on your scalability requirements. b. The OCS 2007 R2 Monitoring Role service and database can be collocated with a computer running Stan

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

New Live Meeting Add-in for Outlook available for download The Conferencing Add-in for Microsoft Office Outlook now allows delegates to schedule a Live Meeting or a conference call on behalf of their manager. The new add-in can be downloaded here: http://go.microsoft.com/fwlink/?LinkId=140651 Written instructions on scheduling a meeting on behalf of another person: http://office.microsoft.com/en-us/livemeeting/HP101541161033.aspx Dial-in Conferencing is also a new audio option for audio conferences that are hosted on Office Communications Server 2007 R2. The dial-in option provides a cost-efficient replacement for your company’s conferencing provider service. It also allows conference call attendees to join a Communicator conference call or a Live Meeting that uses Dial-in Conferencing for the audio by calling in from a phone or mobile device. The dial-in option can be used for scheduled Communicator conference calls or Live Meeting. With Dial-in Conferencing, members and non-members

This server role/configuration Can collocate with this server role/component Cannot collocate with this server role/component Standard Edition configuration Archiving Server (not recommended) Monitoring Server Director Communicator Web Access Edge Server Mediation Server Group Chat Server or Compliance Server Enterprise Edition consolidated configuration None Never collocated Back-End Database server Archiving database Monitoring database Group Chat database Compliance database (for Group Chat) Any other Office Communications Server role Enterprise Edition expanded configuration, Front End Server None Never collocated Enterprise Edition expanded configuration, Web Conferencing Server None Never collocated Enterprise Edition expanded configuration, Application Sharing Server None Never collocated Enterprise Edition expanded configuration, A/V Conferencing Server None Never collocated Web components Archiving Server Monitoring Server Front End Server Web Conferencing Server Application S

From July 1st PIC with windows Live will not require any additional license. Licensing requirements for Public IM Connectivity depends on the service providers you want to connect with and your Communications Server client access licenses. Windows Live:  Customers with Office Communications Server 2007 R2 Standard Client Access License or Office Communications Server 2007/ Live Communications Server 2005 SP1 Standard CAL license with active Software Assurance (SA) qualify for federation with Windows Live Messenger without additional licensing requirements. Customers who do not meet the qualifying requirement should buy the Office Communications Server Public IM Connectivity license for federation with Windows Live Messenger. AOL/Yahoo!:  Federation with AOL and Yahoo! requires the Office Communications Server Public IM Connectivity (PIC) per user subscription license. The PIC License provides connectivity to both IM service providers. There are no license options for connectivity to

OCS DNS Automatic Configuration when Split DNS is not an Option I have run into a couple issues with customers that are unable to or unwilling to create DNS Zone of Public namespace internally into their AD environment. In order to get Automatic configuration to work we need to create a SRV Records or a fall back A Record.  DNS Records that Office Communicator look at for Automatic Configuration are as follows. DNS Records   (These records are not in any specific order) _sipinternaltls._tcp.domain.com _sipinternal._tcp.domain.com _sip._tls.domain.com _sip._tcp.domain.com sip.domain.com A typical SRV Record for OCS is configured as below. This is where the problem starts to come in.  The AD Domain is corporate.contoso.local and your SIP URI is   first.last@contoso.com   to match your primary SMTP domain (email address).  In most environments contoso.com is managed by Public DNS Servers and is not available from the internal AD DNS Servers.  One option is to create thi

How do I roll out a certificate to every client in my organisation? Now we have OCS installed, we need to put the internal certificate into the "Trusted Root Certificates" folder on each client. The easy way to do this is to push out the certificate through a Group Policy. We can do this easily and quickly. Start by making a copy of the certificate. You can do this by exporting the file from the certificate snap in in MMC on the Front End server. Export it to a location you can reach on the Domain Controller. Now on the Domain Controller we open the Group Policy Editor. Under Computer Configuration >> Windows Settings >> Security Settings >> Public Key Policies >> Trusted root Certification Authority -- Import and choose the location of the cert we exported earlier. Now we can see the cert in here, we know it will be pushed to each client on next login once replication of Group Policies have been completed.

We came across an issue with a segmented network with multiple VLANs separated by numerous firewalls. Each VLAN was considered a separate LAN. Rules must be opened on the firewalls to allow video and audio traffic to work inter-VLAN. By default ports 1024-65535 TCP/UDP are used which is pretty much all of them bar 1023 ports - this is a big hole. So instead we can limit the ports used from the client and then on the firewall just open up these ports - minimum 20 ports. Media Port Range This section describes the minimum media port allocation requirements for the client and server. The default UDP/TCP port range used by the Office Communicator 2007 client is 1024-65535. The Real Time Media Communications stack in Office Communicator 2007 allocates the media port dynamically in this range. In order to maintain an adequate level of performance, you can specify a smaller port range for Office Communications Server to use. To control the specific range of ports that need to be open on