Feb 09

Lync Hotfixes available

Product

KBs

Build

 

Update

External

  

Lync Server 2010

Lync Server 2010_CU4_HF4

2670430

4.0.7577.189

Lync Server McxStandalone

Lync Mcx 2010_CU4_HF4

2665325

4.0.7577.189

Lync 2010

Lync 2010 CU4 HF4

2669896

4.0.7577.4064

Permanent link to this article: http://www.reijling.nl/?p=854

Jan 17

Uitnodiging voor UCUG op 26 januari

UCUG & Microsoft Lync vragenuur.

Samen met William van Male van Microsoft NL hebben we een maandelijks Lync vragenuur opgestart. Dit is begonnen in december, en tot en met februari testen we een aantal tijdstippen uit en ook kijken we of een open vragenuur of een specifiek onderwerp beter aanslaat.

Het is een online meeting waar iedereen aan deel kan nemen, of je nu al Lync hebt of niet. Er is ruimte voor alle Lync gerelateerde vragen.  Registratie kan via de links op ucug.nl aan de rechterzijde.

De experts die meewerken doen dit op vrijwillige basis, en komen zowel uit de gelederen van onze usergroup als bij Microsoft Nederland vandaan. We hopen op deze unieke wijze een laagdrempelige manier aan te kunnen bieden om de diverse vragen die er zoal spelen rondom Lync van een antwoord te kunnen voorzien.

UCUG meeting 26 januari.

De meeting is dit keer donderdag middag 26 januari bij Microsoft te Schiphol, het thema is Lync.

Registreren kan hier: http://www.eventbrite.co.uk/event/2663116453

Agenda

  • 12:30-13:00 ontvangst met broodjes
  • 13:00-14:00 Lync bij de gemeente Nieuwegein – Frederik Lefevre
  • 14:00-15:00 Remote access voor mobile devices – Steven van Houttum
  • 15:00-15:15 pauze
  • 15:15-16:15 Microsoft Lync Server als telefonie oplossing – Jeroen Reijling
  • 16:15-16:45 Lync Q&A

Lync bij de gemeente Nieuwegein – Frederik Lefevre

Frederik Lefevre van de Gemeente Nieuwegein, waar Lync volledig wordt gebruikt voor telefonie, komt vertellen hoe ze de implementatie gedaan hebben en hoe Lync door de eindgebruikers opgepakt is.

Remote access voor mobile devices – Steven van Houttum

Sinds kort zijn er voor diverse mobiele platformen Lync clients beschikbaar. In deze sessie kijken we naar de mogelijkheden, werking en implementatie hiervan met speciale aandacht voor het remote access deel waaronder push notifications en autodiscover.

Microsoft Lync Server als telefonie oplossing – Jeroen Reijling

Ik werk bij Avanade en ben Microsoft Certified Master in OCS 2007 R2. Sinds 2011 ben ik MVP op Microsoft Lync.

Na de implementatie van Microsoft Lync voor IM/Presence, het aanzetten van de conferencing mogelijkheden is vaak de volgende stap de integratie van telefonie. Waarom Microsoft Lync als telefonie? Wat zijn de mogelijkheden voor integratie of vervanging? Welk stappenplan kunnen we nemen? In deze sessie zal ik de basis principes uitleggen zodat u de koppeling kunt maken en hoe een migratie kunnen realiseren.

Lync Q&A

Tijdens deze meeting zijn er experts aanwezig op het gebied van telefonie, remote access en diverse andere Lync gerelateerde zaken. Een prima gelegenheid voor vragen en discussies!

Bekijk aub de ucug.nl website

Permanent link to this article: http://www.reijling.nl/?p=848

Dec 12

Lync Mobile clients; how to implement

Now that Lync Mobile is out for Phone 7(.5), it is time to help you all with implementing the updates and getting the correct certificates etc….

Microsoft Lync 2010 mobile applications enable mobile clients to function as UC endpoints, providing instant messaging (IM), contacts, presence, and Enterprise Voice features to create a familiar experience for users of Microsoft Lync 2010. For a matrix that lists the features and capabilities of mobile devices and compares them to the Lync desktop client, see http://technet.microsoft.com/en-us/library/hh691004.aspx

Microsoft has released multiple Lync clients for mobile devices. This chapter will provide:

  • Which clients are supported with which requirements;
  • Which infrastructure components are involved for the mobile devices and which certificates are required.

Mobile clients

An overview of the Operating System requirements are documented here:

Platform

Operating System

Additional comments

Phone 7

7.5

+Latest updates

Android

2.3

 

iPhone

4.2

3GS, 4

iPad/2

4.2

 

Nokia E7

3

SR1.1, web browser 7.4

Sources: Phone7 http://technet.microsoft.com/en-us/library/hh691001.aspx, Android http://technet.microsoft.com/en-us/library/hh690980.aspx, Apple devices: http://technet.microsoft.com/en-us/library/hh690978.aspx, Nokia: http://technet.microsoft.com/en-us/library/hh690977.aspx

Backend infrastructure

To support the Microsoft Mobile Lync clients, several backend infrastructure components require changes. To understand these changes, I’ll explain the discovery process, which user scenarios are valid with which certificates and the required steps on the back-end infrastructure.

Discovery process, scenario’s and certificates

The Microsoft Lync mobile client uses an auto discover service based on DNS names. This is based on the user sign-in address, but is in general:

  • lyncdiscoverinternal.<sipdomain>;
  • lyncdiscover.<sipdomain>.

 

From a functional perspective, the following scenarios are valid:

  1. Remote Internet connected mobile client using data or Wi-Fi;

    A Lync mobile client connects to the Reverse proxy using Lyncdiscover.<sipdomain> as shown below.


    This results in a new web listener or expansion of the current web listener that was used in the previous situation.

    Depending on the mobile devices and the management, I would recommend using Public Certificates. A single Certificate can be used with multiple SAN entries on certificate #1.

    Certificate #2 is mentioned in scenario number 2, but could be left unchanged if the Reverse Proxy solution is capable of rewriting URL’s from Lyncdiscover.

  2. Internal Wi-Fi connected mobile client.


    In this scenario, a user is connected to the internal Wi-Fi network and can be considered as an internal user. If this statement is true, there are two options…

    1. Redirect them to the External Reverse proxy using the valid DNS records;
    2. Redirect them to the correct Front-end Pool that have the mobility service running.

    Option B requires renewal of the certificate on the Front-end Pool to include the SAN entries for Lyncdiscoverinternal.<sipdomain>. And again, if the mobile devices are managed and you are able to include the Internal CA on to the mobile device, you can use internal certificates. Otherwise it is required to use Public Certificates.

Backend steps

First, download the following application and update:

  1. Autodiscover & Mobility service: http://www.microsoft.com/download/en/details.aspx?id=28356
  2. Lync CU4: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11551

Implement them using:

  1. this blog to implement CU4: http://www.ultimate-communications.com/2011/12/best-practices-when-updating-lync-server-with-those-cumulative-updates-lync/
    1. Remark 1; Page 26 regarding adding ASP.NET in IIS is done when installing the Autodiscover & Mobility service.

Hope this helps you all, if not, please contact me!!

Permanent link to this article: http://www.reijling.nl/?p=821

Dec 07

Lync & Polycom; Possible integration

Fellow Lync MVP Jeff Schertz has written some excellent blogs on Lync & Polycom which I recommend you read:

Polycom and other vendors are providing Room Video Conferencing systems as well as personal Video solutions. However, I would like to focus on the integration of the Room Video systems of Polycom and Lync. Polycom is one of the members of the Unified Communication Interoperability Forum (UCI Forum) (http://www.ucif.org/). The goal of all members of the UCI forum is: “To improve interoperability among UC products and services.” This will result in easy to use and transparent usage of video conferencing systems, either room- or person based.

This article will help you to understand the various terms/roles Polycom uses and how you can somewhat compare it to the roles in Microsoft Lync. The picture below provides a logical overview of these components:

HDX systems

Polycom calls their telepresence endpoints HDX systems.

Integration between Lync and Polycom HDX systems requires the following steps to be taken into account.

  1. All Polycom HDX systems are required to have software version 3.0.0.2 to be able to integrate with Microsoft Lync.

    How to update the systems is described in the release notes: http://downloads.polycom.com/video/hdx/ReleaseNotes/hdx_rel_notes_v3_0_0_2.pdf

  2. For each HDX system, a user object must be created in the Active Directory and have a mailbox to allow joining an online meeting;
  3. Registration of Polycom devices in the Lync environment can be done following this guide:

    http://support.polycom.com/global/documents/support/setup_maintenance/products/video/UC_Deploy_Guide_MS.pdf

Once the system is registered, the presence of the HDX system should be visible in any Lync client.

In both OCS releases (2007 and 2007 R2) Microsoft uses different versions of ICE between the Front End server (ICE v6) and the Edge server (ICE v19), whereas Lync Server 2010 uses ICE v19 throughout the entire product line. As the Polycom implementation of CCCP is only compatible with the current ICE v19 used in Lync server then an HDX will not be able to join conferences hosted on an OCS AVMCU, only conferences hosted on the Lync AVMCU.

RMX systems

Polycom calls their conferencing bridges RMX systems. A conference bridge is comparable with a (virtual) meeting room.

Integration between Lync and Polycom RMX systems requires the following steps to be taken into account.

  1. All Polycom RMX systems are required to have software version 7.2.2 to be able to integrate with Microsoft Lync.

    How to update the systems is described in the release notes: http://downloads.polycom.com/bridging_collab/rmx/relnotes/RMX_Release_Notes_V_7.2.2.pdf

  2. For each RMX system, a DNS entry must exist in the specific DNS domain;
  3. Within Lync, the Trusted Application Pool, must be expanded with the new RMX;
  4. Within Lync, a static route must be created for the just created RMX;
  5. Within the Active Directory, a user object must be created in the Active Directory;
  6. Registration of Polycom bridges in the Lync environment can be done following this guide:

    http://support.polycom.com/global/documents/support/setup_maintenance/products/video/UC_Deploy_Guide_MS.pdf

Once the system is registered, the presence of the RMX should be visible in any Lync client.

Minimum versions

To allow seamless integration and high quality video sessions between Lync and Polycom, the following Polycom devices are supported:

RTV Compatible Models

Polycom HDX 4000 with Hardware Revision C

Polycom HDX 4500 – All Hardware is supported

Polycom HDX 6000 – All Hardware is supported

Polycom HDX 7000 with Hardware Revision C (shipping from early February 2010)

Polycom HDX 8000 with Hardware Revision B (shipping from January 2009)

Polycom HDX 9006 with Hardware Revision B (shipping from April 2010)

RMX1500 only with MPMx

RMX2000 only with MPMx

RMX4000 only with MPMx

Note: Minimal software version needed HDX v3.0.1 and RMX v7.2 or higher will support 720p video using RTV with OCS2007 and Lync.

Bridge (MCU) bandwidth demand

As Polycom offers multiple video streams instead of the Active Speaker configuration that Microsoft uses, bandwidth usage is highly impacted.

Key infrastructure components of the video conferencing system need special consideration. First consider the video conferencing bridge (or MCU). If six video conferencing endpoints are engaged in a conference call, all six endpoints have established a full duplex connection to the bridge. The bridge network connection must be able to sustain the maximum number of endpoints that will be in all simultaneous conference calls. Each client that connects to the bridge will have a traffic stream flowing from the client to the bridge at the bandwidth negotiated for that video conference. If each client has negotiated a 1.9 Mbps bandwidth call, and there are 6 clients, the bridge will be supporting 1.9 Mbps x 6 or 11.5 Mbps of traffic. When we add the 20% additional bandwidth required for IP packet overhead, this now comes to 13.8 Mbps.

Some video conferencing endpoints also support a built-in multipoint conferencing mode. If a video conferencing endpoint is acting as a bridge for a small conference, there will be a proportionate increase in the bandwidth to that client. A 4-person conference using one of the 4 clients as a bridge will generate three full duplex streams to the client acting as a bridge. The other three clients will see a single full-duplex stream.

Polycom’s integration with Microsoft Lync Server 2010 provides the following functionality:

  • Enables point-to-point calls between Polycom HDX systems and Microsoft Lync clients.
  • Provides real-time presence information between Polycom devices and Microsoft Lync clients.
  • Enables support for remote and federated endpoints to participate in point-to-point calls and video conference calls.
  • Supports high-quality video (720p) between Lync clients and Polycom endpoints.
  • Allows Polycom endpoints to participate in Lync Server-hosted multi-point conferences.
  • Allows Microsoft Lync clients to view the presence for Polycom RMX meeting rooms and start one-click conferences.

 

In the end, the overall picture might look like this:

Permanent link to this article: http://www.reijling.nl/?p=812

Nov 29

Lync CU4 Hotfix 1 available

CU4 Hotfix 1 is available which will solve a specific RCC issue. Please read the Knowledge Base article for more info.

Product

KBs

Product Update

 

Lync 2010 Lync2010_CU4_HF1

2647415

Permanent link to this article: http://www.reijling.nl/?p=809

Nov 21

Lync CU4 is available!!!

As people may know, Lync CU4 is a requirement for all supported mobile clients.

Feel free to download the updates and regarding the mobile clients… They should be coming this year!!

Product

KBs

Download

Product

Update

  

  

Lync 2010 (64bit)

Lync_2010_CU4

2514982

MS download

Lync 2010 (32bit)

Lync_2010_CU4

2514982

MS download

Lync Server 2010

LS_2010_CU4

2493736

MS download

Lync 2010 Group Chat Server

LGCS_2010_CU4

2514984

MS download

Lync 2010 Group Chat Client

LGCC_2010_CU4

2636065

MS download

Lync 2010 Group Chat Admin

LGCA_2010_CU4

2636063

MS download

Lync 2010 Phone Edition (Polycom CX700 and LG-Nortel IP Phone 8540)

LPE_CX700_IP8540_CU4

2636066

MS download

Lync 2010 Phone Edition (PolycomCX500, Polycom CX600 and Polycom CX3000)

LPE_CX500_CX600_CX3000_CU4

2636067

MS download

Lync 2010 Phone Edition (Aastra 6721ip and Aastra 6725ip)

LPE_Aastra6721_Aastra_6725_CU4

2636068

MS download

Lync 2010 Phone Edition (HP 4110 and HP 4120)

LPE_HP4110_HP4120_CU4

2636069

MS download

Permanent link to this article: http://www.reijling.nl/?p=807

Nov 17

CX7000 introduction; register for the online event!!

Polycom and Microsoft Special Online Launch Event: The Power of Collaboration

Don’t miss this webinar which will feature the introduction of more than 10 new Polycom phones interoperable with Lync and the launch of the new Lync Room System designed by Polycom.

  1. December 6th at 8:00AM PST
  2. Register now!
  3. Learn about new Polycom solutions including: Polycom’s legendary desktop, conference and wireless phones now interoperable with Lync and the Polycom CX7000 Unified Collaboration System — group collaboration custom-built for Lync.

This is a native Lync integrated device!


The Polycom CX7000 Unified Collaboration System is in the final stages of testing and qualification with Lync and available to order. The CX7000 is specifically designed to integrate with Lync. With especially tight integration between the Polycom and Microsoft solutions, customers get an intuitive interface, simplified UC experience, and seamless telepresence. The solution integrates all the features of the Lync platform customers love (IM, Online Meetings, content collaboration, etc.) with Polycom’s industry-leading room video collaboration solutions in a single plug-and-play system.

Learn More about the
Polycom CX7000 Unified Collaboration System

Permanent link to this article: http://www.reijling.nl/?p=806

Nov 17

CX5000/Roundtable firmware update available

A new software update for the Polycom CX5000 (a.k.a. RoundTable) is available.
It will
offer improved audio performance by increasing the supported USB audio bandwidth to a full 6KHZ, nearly HD quality performance. This upgrade is free.

Download the update from here:
CX5000 Downloads

Permanent link to this article: http://www.reijling.nl/?p=789

Oct 20

Lync CU3; HF5 available for download

Product

KBs

 

Update

External

Build

Lync Server 2010

Lync Server 2010_CU3_HF5

2630296

4.0.7577.173

Lync 2010

Lync 2010 CU3 HF5

2630294

4.0.7577.336

Lync 2010 Phone Edition (Aries – Aastra)

Lync 2010 CU3 HF5

2633998

4.0.7577.337

Lync 2010 Phone Edition (Aries – Polycom)

Lync 2010 CU3 HF5

2634533

4.0.7577.337

Permanent link to this article: http://www.reijling.nl/?p=778

Oct 19

Lync; ABSCONFIG & corrupt addressbook; Fixed!!

Situation

When you’ve implemented Lync within your environment and you have modified the address book, you might get a similar message in your event viewer:

A full data file is corrupt.

Path: ‘\\<SERVERFQDN>\<SHARE>\1-WebServices-1\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000\F-0f4e.lsabs’ – file corrupted: invalid attribute id 0 in contact. Index: 38 Guid: {301db040-7ab9-47d8-a1e4-00e4bbc1cbaf} Offset: 484

Cause: The Address Book Server is attempting to read one of the full data files in order to generate a delta file. The full data file is corrupt and the delta file cannot be generated.

Resolution:

Examine the details in the associated event log entry to determine which full data file is corrupt and first save it away for possible use by PSS. Then delete the corrupt file. This will result in a missing delta file, but the client will get the next oldest delta file instead.

Found so far…

Now I’ve found a blog entry: http://www.lync-blog.nl/?p=504&lang=en regarding the ABSConfig tool. The address book is indeed modified to only include only the Lync enabled users.

However, when I’m looking into the dbo.AbAttribute is see differences in the RTC and RTCLOCAL databases…. The blog mentioned earlier provides a solution to restore the address book without the filters… However, that didn’t solve my issue… We’ve got a whole lot of users and contacts with the same value in the mail attribute that resulted in double entries in the default address book.

Great news… It is fixed!!

You can follow these steps to fix the address book and have a filter on it.

  1. Request the hotfix from Microsoft using the following reference: http://support.microsoft.com/kb/2621857.
    1. Unpack the file and copy the OCSReskit.msi to the Front-end server(s).
  2. Request the hotfix from Microsoft using the following reference: http://support.microsoft.com/kb/2621854/
    1. Unpack the file and copy the OCSCore.msp to the Front-end server(s).
  3. Uninstall the current Lync resource kit from the Front-end server(s);
  4. Run the OCScore.msp on all Front-end(s) servers;
  5. Type in: Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <EEBE.Fqdn> -UseDefaultSqlPaths

    Remark: You only need to run this once on a Front-end

  6. Install the OCSReskit.msi

    If you’ve installed it on the default location, you can run the ABSConfig.exe from the following location: C:\Program Files\Microsoft Lync Server 2010\ResKit. In the screenshot below, I’ve added a filter that only objects that have the msRTCSIP-PrimaryUserAddress attribute filled in.

  1. When pressing Apply, Regeneration of the User database will be done. Look at the Lync Server part of the Eventviewer to validate that you see the EventId 30024:

    This EventId is required for all domains in the Active Directory Forest where Lync is deployed.

  2. Once step 7 is finished, you need to update the address book by typing in:

Update-CsAddressBook

  1. In the Lync Server part of the Eventviewer (on the server where you’ve performed step 7) look for EventId 21056 that the LS Address Book Server is finished.

Thank you Microsoft for getting this fixed within short period of time!

Permanent link to this article: http://www.reijling.nl/?p=769