September 23rd, 2012 | Tags:

The October user group has been announced, event details below:

The summer is almost over and Autumn is fast approaching, but fear not, the October edition of MUCUGL is about to arrive! :)

Last October we held the event at the Polycom Executive Experience Centre, this is a great centrally located London venue and we’re pleased to be back again. Jabra are co-sponsoring this event and Stuart Black will be giving us an overview of the latest and greatest Jabra devices optimised for Lync – they’ll also be giving away 5 Supreme UC Headsets. Adam will then provide an update on some of the new and existing Polycom audio/video endpoints and bridges now qualified for Lync, including some live demos.

We also listen to your feedback and it was requested at our last meet that we do a deeper-dive into PBX interoperability with Lync, so Justin has stepped up and will deliver this technical session – EV, RCC, Simring, Gateways, Direct SIP, ISDN, ITSPs and more will all be explained! Tom will then close the event (before the regular visit to the pub) with a round-up on Lync related news and community updates.

We all look forward to seeing you there!

Date: Oct 25th 2012 Title: Title: Devices, Endpoints & Bridges that don’t go bump with Lync
Times Topics
18.00-18.20 – (Guest Speaker) Overview from Jabra on Optimised for Lync Device Portfolio (SB)
18.20-19.00 – (high-level) Polycom Voice and Video Solutions Qualified for Lync (AJ)
19.00-19.20 – (Networking) N/A
19.20-19.40 – (deep-dive) Lync PBX Interoperability Scenarios (JM)
19.40-20.00 – (Gen. Update & Q/A) Latest resources and speaker specific updates (TA)

Registration: here

Location:

Polycom Executive Experience Centre 69 Old Broad St 16th Floor Dashwood House, Broadgate, EC2 London

August 30th, 2012 | Tags: , ,

I’ve not mentioned it previously, but earlier in the year I joined Polycom as a UC Architect. It’s an exciting role for someone like myself, I get to listen/learn and advise customers on their UC strategy, assist in the development of new and existing solutions and most importantly talk about Lync on a daily basis! 🙂

Over recent months I had the privilege of working with the team responsible for the CX7000, specifically supporting the recently released 1.1 update. But before I dig into the detail, I’m going to share, for those not already aware, more on the product itself.

Background

The CX7000 is a purpose built Lync video room system, under the hood is a hardened version of Windows 7 embedded running a Lync 2010 client (Cumulative Update 5 as a part of the 1.1 update) and a Polycom designed user interface, as I’m sure you’re aware the Lync client on a dedicated meeting room PC does not make for a good user experience.

Typically a base Lync account and respective Exchange mailbox is allocated to the CX7000, the idea here is the meeting requests are sent (in addition to the participants themselves) to the CX7000, the respective mailbox will, where configured for resource scheduling, accept/decline the request based upon room availability. The attendees can then enter the room and via the calendar on the home screen use one-click to join the Lync Online Meeting.

In addition to the one-click Online Meeting joining, ad-hoc Lync conversations—IM, Voice or Video—can also be initiated via the CX7000, by clicking “Find a Contact” on the home screen (see above). You can either search your company’s Lync directory, dial a PSTN number (if Enterprise Voice is enabled on the Lync server), or if your administrator has enabled “Show Contact List” you can select a contact from the system’s contact list, including any recent contacts (see below)

 

The CX7000 can be deployed in a single or dual screen configuration, in the case where a secondary monitor is attached video and content is displayed together on either display (this can be configured by the administrator). Native Lync content sharing is also available and the CX7000 can participate fully as attendee or presenter (with control). Content sharing can be initiated either by:

a)      Another Lync participant for any supported Lync content type, or

b)      The CX7000 for Lync Whiteboard and Polls

It is also possible to push content to other conference participants via a locally attached VGA input, to select click Share -> Program… -> PC Content -> Share (see below). Content can be previewed at any time by selecting Options (via the Home Screen) and PC Content Preview. This is especially useful for “visiting” presenters who may not wish to join a meeting online, but instead utilise the CX7000 screens for local content presentation.

 

The CX7000 ships in two configurations with high-definition Polycom cameras, either:

  • CX7000 HD system with EagleEye III (“EEIII”) motorized pan-tilt-zoom Camera with 12x zoom and auto-focus (capable of up to 1080p – currently up to 720p30fps point-to-point within Lync 2010) or…
  • CX7000 View system with EagleEye View Camera, unlike the EEIII this camera only supports digital pan-tilt-zoom with manual focus – but does incorporate built-in microphones.

In addition to the cameras:

  • The CX7000 HD system includes a Polycom HDX Microphone Array, with three mics for 360-degree sound pickup and…
  • Both systems include a Wireless keyboard and mouse

Note: screens and speakers are not included

For a business that has chosen Lync as their UC platform and the requirement of a room video system that supports full Lync collaboration with an easy to use Lync-style interface then the CX7000 is a no-brainer vs. a legacy video endpoint i.e. Polycom HDX (which also natively registers with Lync)

So what’s new in the 1.1 update?

  • Support for Office 365 (both Shared and Dedicated) – more on this later!
  • Standalone-mode – sign into Lync without the need to add the system to the domain (previously required)
  • Ability to daisy-chain either Polycom HDX Microphone Array or Ceiling Microphones (in both cases up to two can be linked together)
  • Hot-desking capability (User Sign In) – idle session timeout can be set here so the CX7000 dedicated account will switch back for those using the room scheduling
  • Utilise the CX5000 (RoundTable) for video input—including support for panoramic video—and as microphone and speaker
  • Improved audio performance via Polycom Audio Echo Cancellation (AEC) enhancements
  • Lync client is updated from CU4 to CU5 – more on this here
  • Support for 11 user interface languages (English, French, German, Spanish, Italian, Portuguese, Russian, Japanese, Korean, Simplified Chinese and Traditional Chinese
  • Ability for users to select a different input language for IM and contact search, reverts to system language after each conversation ends.
  • Ability to override the Exchange Web Services autodiscover address and/or provide alternate e-mail/Exchange credentials
  • Bandwidth reduction for VGA-based content
    sharing – reduction is from 6MB to as low as 1MB, in situations where the content is static

Installation process

The 1.1 update is a replacement system image (in Windows Imaging format .WIM), the resulting effect being that future factory restores will roll back to 1.1 rather than the 1.0 base release. The update is circa 3GB, so for USB deployment you’ll need a drive big enough to hold the image, alternatively you can update via the local area network, in both cases 1.02 must be installed first. For more information on this refer to the release notes.

Digging into more detail…

I’d now like to call out a few features and go into some more detail, specifically Office 365 and the changes to sign-in modes, Hotdesking and Exchange Web Service Settings

1. Office 365 and Sign-in Modes

New in 1.1 is the ability to register the device with Office 365 and On-Premises Lync without the need to add the device to the domain and with this the option to register OOB via a Lync Edge Server (not a common requirement!) It’s worth mentioning that usually when registering a Lync client against a privately signed certificate (off-domain) there is the need to manually configure the Certificate Authority (CA), the 1.1 release will, where available, query Option 43 and download the necessary CA certificate, a process already utilised by Lync Phone Edition devices. In cases where Option 43 is not available certificates can be deployed manually via a USB drive (not recommended for production deployment)

Features available by topology

It’s worth noting the features available below:

Office 365 Shared Office 365 Dedicated On-Premises (Standalone/Domain)
Resource Enabled Room Mailbox No 1. Yes 2. Yes
Calendar Access (EWS Query) Yes Yes Yes
HD Point-to-Point Video 3. No Yes (upon request) Yes (enabled via PowerShell)
  1. At this time Office 365 Shared does not offer Lync-enabled room mailboxes, as a result the base CX7000 calendar may not be reflected correctly (unless this is allocated to a user). The recommended approach would be to utilise hotdesking mode (User Sign In)
  2. Via the setup of a standard Lync/Exchange enabled user resourcing can be enabled by connecting to the mailbox within the Outlook client, go to Options ->  Calendar -> Resource Scheduling (see below). Update: This requires that an Outlook client be open for automated process.

     

  3. HD video is currently unavailable for Office 365 Shared, but where not already available, can be enabled upon request for Office 365 Dedicated customers. Lync 2010 On-Premises supports video resolutions up to 720p for point-to-point calls; any communications going through the Lync AVMCU—multi-party calls, calls involving shared (uploaded) PowerPoint slideshows, Lync whiteboards or polls—are limited to VGA resolution. Update: Office 365 now offers up to HD 720p for RTV-based point-to-point calls and HD 1080p with H.264 SVC (or Lync 2013 clients)

Sign-in modes at a glance

The addition of standalone sign-in mode introduces the ability to register the CX7000 in all types of deployment, domain member mode should therefore only be used where there is a requirement to add the device to the domain.

Office 365-Shared Direct Office 365-Shared ADFS Office 365-Dedicated On-premises
Standalone
Domain Member × × ×

Office 365 versions

There are two types of Office 365 offered to small/medium-sized customers (referred to as Shared or to you and me, the version available for sign-up via office365.com) and Dedicated, for larger businesses (typically greater than 5000 users). Both of these platforms offer hosted or “Online” versions of Microsoft Lync, Exchange and SharePoint – but note that they vary in authentication, integration (including Hybrid approach) and feature-setsInterestingly the CX7000 is the first IP-based device that is able to register directly with Office 365 Shared, this is because it’s leveraging the Microsoft Online Services Sign-in Assistant already in use by Windows PCs connected to Office 365 today – for future updates to the Microsoft Online Services Sign-In Assistant via Advanced Configuration -> System.

Office 365 Shared deployment

The CX7000 is able to support either direct authentication with Office 365 or ADFS (where accounts are provisioned via the customer’s On-Premises Active Directory) – high level topologies are illustrated below:

1. Direct Authentication 2. ADFS Authentication

For both methods of authentication the CX7000 standalone mode is used and account information is inputted as:

Lync Sign-in Address: <sip address@domain.onmicrosoft.com> (In scenarios where ADFS-based accounts are used then the customer’s domain will replace O365alias.onmicrosoft.com)

Username: <sip address@domain.onmicrosoft.com> (same as above)

Password: <your password> (*for direct authentication this will be provided via your Office 365 administrator or in the case where ADFS is used this is likely to be the password for your regular Windows account).

* Note: first time logon for Office 365 direct authentication requires that the initial password be changed, this cannot be achieved via the CX7000 and end-user logon is necessary via the Office 365 portal

Office 365 Dedicated deployment

The CX7000 is able to support authentication with Office 365 – a high level topology is illustrated below:

1. Office 365 Dedicated

For authentication the CX7000 standalone mode is used and account information is inputted as:

Lync Sign-in Address: <sip address@domain.onmicrosoft.com>

Username: <domain\username>

Password: <your password>

2. Hotdesking (User Sign In)

Another addition to the 1.1 update is the ability for an individual user to sign in, this is particularly useful in a scenario whereby you have not invited the base CX7000 account (particularly in the case for Office 365 Shared deployments) and wish to sign in to your personal Lync account. Once signed in, your personal Lync contact list and Online Meeting schedule is displayed, the administrator can set an idle timeout whereby the system rolls back to the base CX7000 account after a period of inactivity (see below)

3. Exchange Web Service Settings

The final feature I’d like to explain in more detail is the ability to manually set either the Exchange Web Service address (particularly useful for organisations that need to manually set the address or may have an incorrect server specified within their existing autodiscover record.

In addition to the above an alternate mailbox can be specified, this can be used in a case whereby the an alternate mailbox or SMTP address needs to be specified as the default CX7000 calendar

Summary

In conclusion I hope this article helps those deploying/updating the device, if you have any questions/comments feel free to leave them below

The CX7000 1.1 is now available for download here (file size 3gb) – as a reminder the 1.02 release is a software pre-requisite and CX7000 re-provisioning is not required once the 1.1 update is complete.

August 21st, 2012 | Tags: ,

OCS and Lync interoperability along with RMX is nothing new, in fact integration with OCS dates back as far as 2009. Nevertheless the RMX hasn’t (until now) reached the accolades of Microsoft qualification status.

So what does qualification really mean?

In some cases vendors go from zero interoperability/ functionality to qualified status overnight, obviously in this scenario this isn’t the case so qualification means a little less – but it’s still a big deal and I’ll go on to tell you why…

Qualified devices are certified by Microsoft, they undergo weeks of pre-defined testing (100+ test cases) and are version specific, in this case Lync 2010.

Passing these tests results in:

a) the respective vendors device being listed within the Microsoft Unified Communications Open Interoperability Program (UCOIP).

b) customer peace of mind that the equipment adheres to a requirements specification laid out by Microsoft.

c) passing all the associated test cases within a Microsoft lab.

New features…

The RMX 7.7 release was submitted as a RMX 1500 qualified configuration (strictly speaking if you followed the Microsoft qualification law only this device has been “blessed” – however near identical software is utilised on the 2000 and 4000 models), which is now available publicly here. In addition to qualification a number of other Microsoft Lync related features are delivered as a part of this release, namely:

  • Polycom, Microsoft and Cisco bridge interoperability – this is the ability to host multi-party video conferences on the RMX with video endpoints from multiple vendors. In the case of Cisco, signalling is handled via the integration of Cisco Unified Call Manager (CUCM) and Polycom’s Distributed Media Application (DMA).
  • Microsoft RTV forward error correction (FEC) support – with this feature the RMX is able to support Lync error correction in scenarios where there is connection instability.
  • ICE over TCP – When ICE over UDP is blocked by a Firewall, the ICE connection automatically uses TCP.
  • Media over TCP – as with above, when media is unable to utilise UDP due to Firewall policies etc., the RMX will automatically switch to TCP.
  • Additional Virtual Meeting Room (VMR) presence mode – prior to this release VMRs enabled for presence would only display as available, the 7.7 update introduces the busy state when busy or in use.
  • Error recovery – RMX 7.7 can automatically recover from short duration network errors (up to 5 seconds), enabling video or audio conference calls in Microsoft Lync to continue without disconnecting.
  • Lync AVMCU to RMX Cascading – Last but not least (and a personal favourite) the ability to connect a Lync video conference call to the RMX by transparently joining the two meetings, hosted on their respective MCUs, via end-user drag/drop within the Lync client.

For a full list of features within RMX 7.7, refer to the release notes here

Update: The RMX has now been listed within the UCOIP here

July 16th, 2012 | Tags:

So today is the day that Microsoft did the big reveal on Lync Server 2013 (previously Lync Wave 15). Expect lots of information to follow, but for now go grab the release preview bits (details below).

Trial Programs (user registration required):

Preview Programs (does not require user registration):

What’s new

On-Demand Webcast

London-based Lync Server 2013 Community Event

Lync Developer Roundtable: What’s new in the Lync 2013 architecture, and demos

  • Date: July 19, 2012
  • Time: 9am PDT
  • Duration: 1 hour
  • Format: 30 minute presentation, 30 minute question and answer period
  • Presenter: Anand Lakshminarayanan, Senior Lead Program Manager with Lync
  • Session Recording will be provided one week after the presentation
  • Meeting Link: Click here to join the meeting. NOTE: please do not join the meeting until ten minutes prior to the start time.

Enjoy!

June 17th, 2012 | Tags: , , ,

 

Update: The recent release of Lync Server 2013 and Lync MX (the Windows App Store version of Lync) has meant that the steps detailed below are critical for securing Office Web App and Lync MX – specifically in scenarios where certificates are provisioned via an internal certificate authority and client computers are not domain-joined.

The reason for this is because Lync MX will not utilise LDAP and Office Web App will be unable to use LDAP unless the client is domain-joined, so HTTP for CRL and CDP discovery is vital – ensure the Certificate Revocation List (CRL) Distribution Point (CDP) for the certificates issued to Lync and Office Web App servers points to an HTTP resource in addition to an LDAP resource.

Update 2: Another article specifically aimed at Office Web App can be found here

Below is an example of a well formed certificate, followed by steps to enable this capability:

CRL Example:

CDP Example:

 

I’ve been working more recently with Lync Online and the varying types of deployment topologies, mostly Office 365 Shared or Office 365-S (the most commonly referred to version, available to small/medium size business) – it’s the one you can sign up to via Office365.com

To leverage your existing Active Directory with Office 365-S you need to deploy Active Directory Federation Services (ADFS 2.0), this is a service hosted on a single or multiple IIS web servers (or a farm as Microsoft refer to it). If you want to allow external clients (via the Internet, rather than a VPN) you also need to configure an ADFS Proxy, this essentially acts as a reverse ADFS proxy. In all my test environments to-date I have not needed to deploy an ADFS proxy, but it’s also worth noting that there is one gotcha to my previous statement – for Outlook access to Exchange Online a proxy is required for both internal and external access. Put simply this is due to the fact that Exchange Online redirects part of the authentication from the Micrsosoft Exchange Online service back into the tenants ADFS service via the Internet – there is no VPN tunnel established between the Office 365 shared data centres and the customer.

So with the background covered I’ll dig into the problem I experienced with Lync Online, specifically for ADFS provisioned accounts accessed via client PCs that were not members of my ADFS domain. I elected to use a privately signed certificate for my ADFS service, this was because it limited the amount of manual client-side intervention (CA certificates deployed via AD) and was easier/cheaper to provision, it was a lab environment after all…famous last words!

Prior to this issue (“Server is unavailable” within Lync) and subsequent resolution, I’ve never really needed to customise my Windows CA installation – I’ve become a victim of Microsoft’s intuitive wizard-driven installations (this, I fear, is where the problem stemmed from) 🙂

The out-of-box installation (post-wizard) for a Windows Certificate Authority is configured to publish CDP and Authority Information Access (AIA) to LDAP-based clients only, I needed to enable HTTP access to CRLs (via CDP) and AIA. But before I tell you how I did this, let me explain, in simple terms, what this is used for:

  • CRL Distribution Point (CDP) – this is the published location of your certificate revocation list, here we can see a list of thumbprints for certs that have been revoked by an administrator. (see image below)

  • Authority Information Access (AIA) – this is the location used to publish PKI topology information, i.e. which server holds information for a specific certificates.

Without both CDP and AIA information ADFS and most PKI-based applications with fail.

So what is required it to enable publishing to either LDAP and HTTP or just HTTP (which would be sufficient for cover both on/off Domain scenarios)

Ashamedly, the answer is simple (and many thanks to the folks at Microsoft Support for pointing this out)!

1. To set the CDP (CRLs) for your Windows CA access CA management tool (Start -> Run -> CertSrv.msc), right click your CA server and click Properties and go to the Extensions tab. Ensure that “Include in CRLs… and Include in the CDP…” is selected for HTTP (see below)

2. To set AIA change the extension drop-down to AIA and ensure that “Include in the AIA…” is selected for HTTP (see below)

Once these steps are completed you will need to re-provision the signed ADFS certificate and assign to the IIS website(s) hosting ADFS and the ADFS Service Communications Certificate within the ADFS 2.0 management console. I hope this helps!

June 17th, 2012 | Tags:

The latest batch of Lync cumulative updates are detailed below, server-side updates can be deployed via the Cumulative Update installer (recommended) or manually (via this page). Updates will as always make their way to Microsoft Update.

Some new features worth mentioning:

  • The ability to switch user when Aries phones are configured as common area phones for hotdesking and locked by another user
  • Aries will support wildcard certificates (for Exchange and Lync), this increases the opportunity of running wildcard certificates within a Lync 2010 environment. There are still some limitations of course, such as backward compatibility with LCS/OCS etc. Jeff Schertz, a fellow Lync MVP has written a great post on this (disregard the last gotcha on Lync Phone Edition clients)
  • The ability to view uploaded Microsoft PowerPoint presentations within a scheduled Lync Meeting, as well as view the meeting participants’ list – more on this here

Server-side updates

Client-side updates

  • Lync 2010 (Communicator) – KB2701664 – download (x86 / x64)
  • Lync 2010 Attendant Console (32bit/64bit combined patch) – KB2702444 – download via Windows Update
  • Lync 2010 Attendee Client – KB2693283
  • Lync 2010 Group Chat Client – KB2701665download
  • Lync 2010 Group Chat Administration Tool – KB2707265download
  • Lync 2010 Phone Edition (Aries for Polycom CX500, CX600 & CX3000) – KB2701671download
  • Lync 2010 Phone Edition (Aries for Aastra 6721ip and Aastra 6725ip) – KB2701667 – download
  • Lync 2010 Phone Edition (Aries for HP 4110 and HP 4120) – KB2701670download
  • Lync 2010 Phone Edition (Tanjay for Polycom CX700 & LG Nortel 8540) – KB2724545download