Just quick heads-up, fellow MVP Tom Arbuthnot ran across an issue whereby Office Communications Server 2007 R2 or Lync Server 2010 Edge Servers URL filtering for IMs disrupts push notifications for both iOS and Windows Phone 7 clients. This is caused by:

Taken from Microsoft KB2664650

The Lync Server 2010 Mobility service sends SIP messages that contain active hyperlinks in their Message-Body header that define the XML namespace information for the push notification to the Lync Server Push Notification service.
Lync Server 2010 Front End Pool Using the URL Filter page in the IM and Presence group in Lync Server Control Panel to enable the Hyperlink prefix option Send warning message, will precede the active hyperlink with a user defined warning message in the SIP packet that contains the push notification message. The Lync Server Push Notification service will reject the modified push notification information and send an error response back to the Lync Server 2010 Mobility service.
Office Communications Server 2007 R2 Access Edge server Using the URL Filter tab of the Office Communications Server 2007 R2 Intelligent IM Filter dialog to:

• Allow instant messages that contain hyperlinks, but convert the hyperlinks to plain text
• Allow instant messages that contain hyperlinks. Enter a warning that you want to insert at the beginning of each containing hyperlinks

Will precede the active hyperlink with a user defined warning message and convert the active hyperlink to text by preceding it with an underscore or precede the active hyperlink with a user defined warning message in the SIP packet that contains the push notification message. The Lync Server Push Notification service will reject the modified push notification information and send an error response back to the Lync Server 2010 Mobility service.

For workarounds and more information refer to the Microsoft KB now live here

For some time now I have been arguing debating that the benefits of Lync Edge Services (specifically client access without the need for a corporate VPN) out-weigh the security concerns around exposing NTLM-based authentication over the web – we already have a lock-out policy defined within group policy and some times you need to take a more risk-based approach right?

Unfortunately I was fighting a losing battle, I knew that the only way I could ever win this debate was if I somehow managed to replicate the incumbant two-factor VPN authentication that was already being deployed, in our case RSA – I know don’t get me started right?

My thoughts have always been swayed towards computer-based certificates, this would be the most seamless way of reproducing a two factor scenario (i.e something you know – in my case succesful Windows logon to an encrypted Laptop and something you own – the locally installed cert), much the same as the network access protection setup we had deployed a year earlier. In essence this consisted of:

(a) authentication with Active Directory + (b) a valid computer certificate = (c) an enabled network switch port

This would be great for Lync!

There was a realisation today that I must have been sleeping under a rock as I came across an interesting “tweet” from Rui Maximo, specifically regarding a Lync Security Filter he had developed.

This add-on (which is installed on your Edge Server) offers the following:

• A soft lock-out policy you can enforce independently of your internal group policy settings (for value here you would need to set this below your internal lock-out threshold)
• UPN to Netbios normalisation (i.e. where your domain is contoso and your SIP FQDN is contoso.com)

Last but not least…

• The ability to disable NTLM v.2 authentication altogether, failing back to TLS-DSK-only authentication!

So what’s TLS-DSK?

Taken from the Lync Security Filter Documentation:

“Lync Server 2010 introduces support for an additional authentication protocol called TLS-DSK. This requires users to supply a client certificate for authentication. The Lync client requests certificates from Lync Server. This is an automatic process that happens the first time the user signs in to Lync Server from within the corporate network where the user is authenticated using Kerberos.

This client certificate is used for authentication with any subsequent log-in attempts. This is a self-signed certificate issued by Lync Server, not a Certificate Authority. If that same user tries to sign in to Lync from a different computer, he’s authenticated using Kerberos (if inside the corporate network) or using NTLM v2 (if outside the corporate network). The process of obtaining another client certificate starts all over.

TLS-DSK provides a level of security that’s very close to two-factor authentication. When combined with Windows BitLocker, the computer or laptop acts as the equivalent of a smartcard (something you have). The password that BitLocker requires to boot your computer is equivalent to the pin required to authorize the use of the smartcard (something you know).

There’s the remote possibility someone could steal the client certificate from the user’s computer, but you can mitigate this risk. Make sure corporate-issued computers are locked down to prevent users from downloading unauthorized applications.

You can force the Edge Server to negotiate the authentication protocol down from TLS-DSK to NTLM v2. In this case, the attacker can still target the user’s account, as discussed earlier. To prevent this scenario, the security filter provides an option to reject all NTLM v2 authentication requests, forcing TLS-DSK-only authentication. This doesn’t affect federated partner connections or PIC connections.”

In essence this Edge Server add-on completely mitigates the risk of allowing NTLM v.2 authentication over the web, burn turning it off. The only draw back here is that initial client logons will need to take place inside your corporate network (or directly between the Lync client and the Lync Front End Server).

Download: here

Nice one Rui!

Related Content:

For more on Lync Edge Server Security I’d recommend you read Rui’s guide on TechNet here

If the answer is YES, then why not make your way to the January MUCUGL meet-up!

Justin, Tom and I have spent the festive season tinkering with the all-new Lync Mobility Service or MCX and look forward to sharing best practice/do’s and don’ts at our Mobility themed get together on January 19th @ Bow Bells House, London.

There are still spaces available, agenda and registration details can be found below:

Registration: here

Location:

Bow Bells House 1 Bread Street EC4M 9BE London United Kingdom

So the waiting (as of writing) is almost over and the server-side bits for shiny new Lync Mobility Service (MCX) have been released!

The client-side bits are likely to be released next week and in the meantime there is nothing stopping you from prepping your Lync Servers. All clients have been released and can be downloaded via your Smartphone’s respective AppStore/Marketplace etc…

For those that are keen to get this up and running quickly, I have put together a short step-by-step guide, for official Microsoft documentation head here. I will however caveat one minor thing at this early stage, with the clients still unreleased this guide is still very much in beta! With all clients RTW’d this guide is officially v.1.0

Configuration of Lync Mobility Autodiscover Records

First up you’ll need to create the internal (lyncdiscoverinternal.<SIPFQDN>) and external (lyncdiscover.<SIPFQDN>) MCX discovery records, mine can be seen below:

As this is being configured within a test lab environment my internal discovery DNS is pointed at my Lync Standard Edition Server, for a larger deployment this is likely to be your Front End Pool or Director.

I have also configured the external discovery record, which can be verified using NSLOOKUP (see below). This is pointed toward the external listener address of my TMG reverse proxy.

Next we need to ensure that the November Lync Cumulative Update  (CU4) is installed – see more on this here, once this is complete we need to open up some internal MCX ports via the Lync management shell.

First the internal listening port: (my Lync Front End is lyncserver.jacobs.local, you will need to substitute this for your own front end/pool/director name)

Set-CsWebServer –Identity lyncserver.jacobs.local -McxSipPrimaryListeningPort 5086

Second the external listening port: (as stated in the prior step, my Lync Front End is lyncserver.jacobs.local, you will need to substitute this for your own front end/pool/director name)

Set-CsWebServer –Identity lyncserver.jacobs.local -McxSipExternalListeningPort 5087

Finally you will need to enable the topology, within the same shell type:

Enable-CsTopology –verbose

MCX Service Installation

Now we’re ready to install the MCX server components, this can be downloaded here. Before you can run the installation a few changes need to be made to IIS.

Within the Lync management shell run, ensure shell is run as admin if UAC is enabled (Windows Server 2008 R2):

Import-Module ServerManager

Add-WindowsFeature Web-Server, Web-Dyn-Compression

Or the following within the Windows command line, ensure command is run as admin if UAC is enabled (for Windows Server 2008):

ServerManagerCMD.exe –Install Web-Dyn-Compression

One complete you will be presented with the following

If you are running Window Server 2008 (IIS7.0) then you need to make a minor ASP.Net change (follow Microsoft procedure included below) – I’m running Windows Server 2008 R2 (IIS7.5) so I skipped this.

To change ASP.NET settings in IIS 7.0

Now we’re ready to run the MCXStandalone.msi

First you’ll need to copy the McxStandalone.msi to C:\ProgramData\Microsoft\Lync Server\Deployment\cache\4.0.7577.0\setup, then execute C:\Program Files\Microsoft Lync Server
2010\Deployment\Bootstrapper.exe

During the installation you will be presented with “Installing MCXStandalone…” (see below)

Certificate Update

Now we need to update our internal SAN certificate, this needs to include the newly created lyncdiscoverinternal
record our internal certificates and first up we have to find the correct certificate identifier or thumbprint for this to be completed successfully. To display all certificates type the following within the Lync Management Shell:

Get-CsCertificate

This will return all certificates and their corresponding thumbprints, in my case all certificates are the same, so I can run the following command to update the cert for all uses.

Set-CsCertificate –Type Default,WebServicesInternal,WebServicesExternal –Thumbprint <Certificate Thumbprint>

During this process I was presented with a warning, upon further investigation neither Lync Discovery addresses were within my internal or external SAN certificates. To re-generate, I ran the following command within the Lync Management Shell

The easiest method for re-generating certificates is by re-running the Lync Deployment Wizard, going to Install or Update Lync Server System and executing Step 3 Request, Install or Assign Certificates

For more information on this the Microsoft MCX deployment guide details alternate certificate scenarios i.e. where you have a unique cert per usage type, refer to the section – Modifying Certificates for Mobility

Forefront TMG Configuration for Lync Mobility

There are two approaches here, one uses SSL for setup the other does not. The main reason for allowing a re-direction from port 80 (http) to 443 (https) is to avoid the need of replacing your existing SAN.

The recommended approach is to only permit the Lync mobility client to communicate on port 443, so I replaced the certificate within my existing Lync web listener within Forefront TMG – so we’re going to run you through this setup below (you could also add the additional public name “lyncdiscover.SIPFQDN” to an existing Lync website rule, but I’m going to run through this as an independent rule).

First we need to create the new web publishing rule (see below)

Give it a name (see below)

Select Allow (see below)

Select Publish to a single Web site or load balancer (see below)

Select Use SSL to connect to the published web server or server farm (see below)

Specify your internal site name, this will be the name of your Front End Pool (see below)

Path should be “/*” and select the check box for Forwarding the original host header (see below)

Add the public lyncdiscover address (see below)

Select your existing Lync web listener, with the new SAN certificate that now includes the lyncdiscover address. Select No delegation, but client may authenticate directly (see below)

Finally allow requests from All Users and Finish

You will now need to go into your newly created web publishing rule and go to the to tab, in the section Proxy requests to published site, ensure that Requests appear to come from Forefront is checked for a single Front End server or Standard Edition server. Alternatively select Requests come from the original client if you have a Front End Pool (see below) This statement is incorrect, and unlike the single Front End server scenario was not tested directly and was taken directly from the official documentation - in both scenarios requests should appear to come from TMG.

Finally go to the Bridging tab and change the default ports from 80 -> 8080 and 443 -> 4443 (this is the external web site on your Lync Front End). Once complete ensure you apply the new rules.

Your TMG rule is complete!

Push Notifications Configuration

Push notifications are handled by Microsoft Office 365 or Lync Online, so you need to have federation deployed and run the Set-CsPushNotificationConfiguration cmd-let

First let’s enable push notifications within the Lync Management Shell by running:

Set-CsPushNotificationConfiguration

Next we should enable federation with Office 365 (if not completed already), within the Lync Management Shell type: (this will add a new Hosted Provider)

New-CsHostingProvider –Identity "LyncOnline" –Enabled $True –ProxyFqdn "sipfed.online.lync.com" –VerificationLevel UseSourceVerification

Then add the Lync Push federated domain type:

New-CsAllowedDomain –Identity "push.lync.com"

That’s it!

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

Early indications from CU PowerShell help files (credit to Tom Arbuthnot and Ari Protheroe) suggest that CU4 paves the way for Lync mobility, with the addition of six shiny new cmd-lets:

1. CsAutodiscoverConfiguration – Modifies an existing collection of Autodiscover configuration settings. The Autodiscover service provides a way for client applications such as Lync Web Access or Microsoft Lync Mobile to locate key resources such as a user’s home pool or the URL for joining a dial-in conference.
2. New-CsWebLink - Creates a new web link that points to the Autodiscover service. The Autodiscover service provides a way for client applications such as Lync Web Access or Microsoft Lync Mobile to locate key resources such as a user’s home pool or the URL for joining a dial-in conference.
3. Test-CsMcxPushNotification – Verifies that the push notification service is working. The push notification service (Apple Push Notification Service and Microsoft Lync Server 2010 Push Notification Service) provides a way to send notifications about event s such as new instant messages or new voice mail to mobile devices like iPhones and Windows Phones, even if the Microsoft Lync 2010 application on those devices is currently suspended or running in the background.
4. CsMobilityPolicy – Modifies an existing mobility policy. Mobility policies determine whether o r not a user can use Microsoft Lync 2010 Mobile. These policies also manage a user’s ability to employ Call via Work, a feature that enables users to make and receive phone calls on their mobile phone by using their work phone number instead of their mobile phone number.
5. CsMcxConfiguration – Modifies an existing collection of Microsoft Lync Server 2010 Mobility Service configuration settings. The Mobility Service enables users of mobile phones such as iPhones and Windows Phones to do such things as exchange instant messages and presence information; store and retrieve voice mail internally instead of with their wireless provider; and take advantage of Microsoft Lync Server 2010 capabilities such as Call via Work and dial-out conferencing.
6. CsPushNotificationConfiguration – Modifies an existing collection of push notification configuration settings . The push notification service (Apple Push Notification Service and Micros oft Lync Server 2010 Push Notification Service) provides a way to send notifications about events such as new instant messages or new voice mail to mobile devices such as iPhones and Windows Phones, even if the Microsoft Lync 2010 application on those devices is currently suspended or running in the background.

Server-side updates

• Lync 2010 Server – KB2514980 – download
• Lync 2010 Mediation Server – KB2640253 - download
• Lync 2010 Policy Decision Point – KB2502809 - download
• Lync 2010 Administrative Tools – KB2467771 - download
• Lync 2010 Core Components – KB2514981 - download
• Lync 2010 Conferencing Attendant – KB2575872 - download
• Lync 2010 Conferencing Server – KB2514978 - download
• Lync 2010 Web Components Server – KB2514979 – download
• Lync 2010 Group Chat Server – KB2514984 - download

Client-side updates

• Lync 2010 (Communicator) – KB2514982 – download (x86 / x64)
• Lync 2010 Group Chat Client – KB2636065 – download
• Lync 2010 Group Chat Administration Tool – KB2636063 - download
• Lync 2010 Phone Edition (Polycom CX500, CX600 & CX3000) – KB2636067 – download
• Lync 2010 Phone Edition (HP 4110 and HP 4120) – KB2636069 – download
• Lync 2010 Phone Edition (Polycom CX700 & LG Nortel 8540) – KB2636066 – download

Uncovering a last minute inability to join a Lync online meeting (or Live Meeting) can be incredibly frustrating, fumbling around for PSTN dial-in details and then switching from the “richer client” or Lync Attendee to the audio/video challenged Lync Web App a disappointment.

That is why I have spent that last couple of months (on and off) looking into an issue with both the Lync Attendee  and Live Meeting Clients when joining via an authenticated web proxy – in my case a Cisco IronPort, but the proxy vendor is immaterial – if it isn’t anonymous then you’ll hit a similar stumbling block.

The first thing you’ll notice when you try to join is a failure (see below) and the inability to make it into the meeting lobby.

If we examine a network capture we’ll see why, pay particular reference to the “Using NTLM Authorization” (see below)

Whilst both clients support web proxies and obtain server settings via the Internet Explorer settings, they do not support any form of proxy authentication. Fear not there is a way around this, my workplace defined a group on our proxy for specific domains that we want to permit without content filtering or the need to enforce A/D authentication (IronPort examples below).

AccessNoAuth group definition:

The only drawback with this method, is that it requires you maintain a list of “white-listed” domains, for Microsoft we added livemeeting.com (Live Meeting) and sip.microsoft.com (Lync), the domains can easily be determined within a network trace.

I hope this helps!

With the recent “Indian Summer” well and truly behind us (Brits) I thought what what better way to welcome in the Autumn season than posting a brief update on what is happening in the world of Microsoft UC

First up, Lync on the Mac – it has been known for some time (even with the equivalent R2 client released a year back) that Lync on the Mac was lacking in capability. Which is why the new Lync for Mac client has received a very warm winter welcome. This is now available for download via TechNet, MSDN and the Microsoft Volume Licensing site.

Then there is Skype and Microsoft, the purchase was announced back in May and only today did the EU bless the deal. This is great news because it might mean we’ll start to see tighter Skype integration start to appear within the relevant Microsoft products – Lync often referred to as a key driver behind the deal.

Mobile still remains to be one of the most common asks and with the release of Windows Phone 7.5 (aka Mango) the Lync mobile client can only be more imminent than ever with a target date no later than the back end of 2011 – if I were a betting man (and I have no inside information on this) I’d imagine this will hit your corresponding smart phone market place some time pretty soon.

Microsoft Lync 2010 “awareness materials” are also available for download, a great resource for driving successful Lync workplace deployments, it can also be customised to fit in with your corresponding company “colours”

Another great download is a plug-in developed by the folks at “Project Leadership Assoc.”, called Lync Social. This free plug allows you to post Lync status updates directly to Twitter and LinkedIn via the Lync client - nice! (for a installation instructions, a fellow Lync MVP, Tom Arbuthnot has a guide here)

Lync CU3 client, server and phone updates also went out in July and hit Windows Update in August - in case you didn’t know this process typically takes a month to work it’s was through the Microsoft update quaranine.

Last but by no means least I, along with Justin Morris and Tom Arbuthnot setup a new London-based Microsoft Unified Communications User Group (or MUCUGL for short!). We had our first event in July and our second event is due later this month, I have to say I really underestimated how much satisfaction I’d get out of bringing like-minded folks together – it was great and I’m looking forward to the next event on Polycom Lync Interoperability on October 20th.

To learn more about MUCUGL and register for the event head here.

Now back to sweeping the leaves from my driveway…(apparently an endless job!)

Then help is at hand (if you are in London on 20th October 11 of course) as the next MUCUGL event is a unique opportunity to learn more about what Polycom can offer enterprises looking for enhanced conferencing capability. The October agenda can be found below, register now to avoid disapointment!

In this, our second MUCUG gathering, the kind folks at Polycom have offered to host the event at their London Executive Briefing Centre, or EBC – naturally we agreed!

“The Polycom® Executive Briefing Centers and Solutions Centers offer exciting experiences that are unlike any others in the world of corporate briefings. At a Polycom center, you can explore the full range of our solutions hands-on, and easily envision how they can work specifically in your business.”

In our first session Mike Adams (Polycom Customer Experience Manager) will be running a series of Polycom/Lync integration demos – it’ll be a 6pm sharp kick-off, so if you are late you might miss out!

Then what better way of demonstrating Polycom’s telepresence but by Mike Stacy and Jeff Schertz (Polycom Solutions Architects and Lync MVPs) joining us to present on Audio/Video Conferencing and Interop in Lync Server.

Finally Tom, Justin and Adam will provide an industry update and focussed Lync guidance/sharing.

A full agenda can be found below, we’re looking forward to seeing you there!

Registration: here

Location:

Polycom Executive Briefing Centre
69 Old Broad St
Dashwood House (16th Floor), Broadgate
EC2 London
United Kingdom

Those that use Mac OS will no doubt be aware that there are a number of limitations within the Communicator for Mac client, most notable being that inability to experience the full conferencing capability of Lync (Lync Web App does go some way to address this).

Also unlike the PC Lync client it is unable to hookup to Office 365 or “Lync Online”, but fear not…help is at hand. Last night the Office for Mac blog announced that the Lync for Mac 2011 had been “released to manufacturing”, great news for Mac users and as with other Cocoa-based apps it looks very Apple-esque!

For a detailed Mac Communicator and the Windows Lync client comparison i’d recommend reading an article on Justin Morris’s blog here also for the full announcement head here. A video tour of the new Mac Lync client due for release in October is below…

I’m a big fan of Gartner’s Magic Quadrant reports, they are well written and extremely credible analysis. I myself  have subscribed and find it incredibly useful – over time I have had to succumb to the fact that I can’t always be on top of all that is leading in enterprise technology.

So with that said a couple of days back Gartner refreshed their annual UC MQ report, first and foremost it will come as no surprise that Microsoft have managed to sustain their pole position for the sixth year running.

I won’t dig too deep into the the detail (as a link to the full report can be found below) but I thought picking out key changes within the respective 2010/11 quadrants (see illustration below) would be of value, from this we can glean the following:

• + Alcatel-Lucent have moved up from “challenging” to “leading”
• + Siemens have moved up from “visionaries” to “leading”
• + Hauwei Technologies are new on the UC scene (just when you though these guys only manufactured 3G dongles?!?)
• + Digium (the folks that make Asterisk) have at long last entered the quadrant, specifically within the niche players market
• - Interactive Intelligence  have dropped from “visionaries” to “niche players”
• - IBM have been overtaken by NEC
• - SAP have dropped off all together

For a full read of the report, it can be accessed here (no Garter subscription required)