Supported or not Supported, this is the Question


UPDATE 19-01-2015: thanks to Lync MVP Thomas Poett, and his input, I updated the article

how many times did you stumble upon a question from a customer if a certain feature or deployment scenario is supported by Microsoft and Lync 2013 or not.

we all forget, I mean there is a new stuff happening in our world (UC) every minute and sometime we loss tracks, so I have what I call my SCS (supported Cheat sheet) where I keep all information I have through my years in Lync by something I read or researched or learned from someone else about Lync supportabilities, and I decided to share it here in a blog article about what is supported or not supported regarding Lync 2013.

feel free please to correct my information, or put a comment about something I did not mentioned and I will be add it to this article, the purpose is to use this article as a fast / complete resource for “supported or not supported” questions.

Lync Client

  • Lync 2013 client supported OS starting Windows 7 and above
  • Lync 2013 client not supported on Windows XP
  • Lync 2013 not supporting H263 codecs
  • Lync 2010 Attendee is not Supported with Lync 2013 Pool
  • Live meeting not supported when running with Lync 2013 user – use Lync web app if cannot use Lync client
  • Application sharing , Desktop sharing and file transfer are not Available in Lync windows app
  • Lync 2013 Basic client (Article updated 18/01/2014):
    • Support call forwarding & Transfer
    • Support recording
    • Not Available Team call & Delegate
    • Not Available Enhanced E-911
    • Cannot initiate call to RGS
    • Cannot connect to Voice mail
    • Cannot handle call on behalf of others
    • Cannot make call on behalf of others
    • Support gallery Video in meeting – with October 2014 update
    • Not Available OneNote & SharePoint integration (skill search)
    • Not Available VDI with Lync basics
    • Conversation History available only if you using Outlook & Exchange
    • Not Available PGC
    • Not Available RCC
  • Online Meeting Add-on supported starting with Office 2003 and above
  • Lync 2013 Mobile Not Supported with Lync 2010 Edge
  • Lync 2013 for Android is Not Supporting on devices that have Tegra 2 chipset
  • Lync 2013 for Android supported on Android OS 4.0 and above
  • Lync VDI Not Supporting to be used with Lync phone edition
  • Lync VDI Multi-view Not Supported
  • Lync VDI with Audio/video tuning page are Not Supported
  • Lync VDI Recording Not Supported
  • Lync 2013 client cannot connect to OCS 2007 R2 server

Lync Web Application

  • Lync Web App Support
    • Application sharing
    • Video
    • Audio
    • IM
  • Lync 2013 web application supported on 32-bit & 64-bit Browsers.
  • Lync 2013 web application runs on Windows 8 , windows 7 SP1, windows Vista SP2, Windows XP SP3, MAC OS on following supported browsers:
    • IE 8 – 11
    • Chrome 18.x and up
    • Firefox 12.x and up
    • Safari 5.x and up

Lync 2013 & Active Directory

  • Single forest with single domain
  • Single forest with single tree & multiple domains
  • Single forest with multiple tree & disjoint namespace
  • Multiple forest in central forest
  • Multiple forest in resource forest
  • Lync 2013 Support forest level windows 2003 native mode or higher
  • Lync 2013 support domain level windows 2003 native mode or higher
  • DC must be running windows 2003 (32bit or 64bit) or higher
  • Lync 2013 support only 64bit machine to prepare the forest & schema

Lync 2013 and OS

  • Lync 2013 Support Windows server 2008 R2 (SP1, Standard, Enterprise, Datacenter), Windows server 2012 & 2012 R2 (Standard, Datacenter)
  • Only 64-bit OS are supported
  • Lync 2013 support service packs automatically, but full version release (R2 , R3..etc.) are supported only if mentioned by Microsoft.
  • Lync 2013 Support SQL server 2008 – 2012 SP1 (Std. & Ent.) only 64bit

Lync 2013 & Virtualization

  • Lync 2013 supports virtualization of any of the server roles
  • Supported virtualization platform:
    • Windows server 2008 R2 Hyper-v
    • Windows Server 2012 Hyper-v and above
    • ESX 4.0 and above
  • Mix of Virtual and Physical nodes in same Pool-role is not supported
  • Mix of Virtual and Physical servers in same deployment is supported
  • Using Dynamic Memory for a Lync VM is not supported
  • SYSPREP on a machine with Lync deployed is not supported
  • Quick / Live Migration is not supported & can cause some problem with Client connectivity

Lync 2013 Server

  • Lync 2013 Frontend can have following collocated with it

    • Archiving
    • Monitoring
    • Mediation
    • PGC – “Standard Pool only”
  • Mediation Server not Supporting other roles collocated with it
  • Director server not Supporting other roles collocated with it
  • Edge server not Supporting other roles collocated with it
  • SBA can have following collocated with it
    • Mediation server
    • Media gateway
    • SBS
  • Trusted application not Supporting other Lync roles collocated with it (unless it is SEFAUtil from ResKit, supported on Frontend server – thanks to Lasse Nordvik)
  • Exchange and Lync don’t mix in same box
  • Metropolitan Pool – Single pool stretched between two datacenters is not supported (supported if same network without routing)
  • Lync 2013 “Cold Standby” pool pairing (having the backup pool serving other active users) is not supported
  • NAT on the Internal Face of Edge server is not supported
  • NAT on the External Face of Edge is supported (Only with DNS-LB, not supported with HLB)
  • Migration to Lync 2013 is only supported from Lync 2010 or OCS 2007 R2
  • Lync 2013 not supporting SQL Failover Clustering no Always-On
  • Lync 2013 Support SQL Mirroring
  • Lync 2013 Edge Server joined to the Internal Forest is “Supported” but not recommended – serious security risk
  • Lync 2013 Standard Edition pool with correct hardware support up to 2,500 users
  • Using same SQL instance that is serving Lync RTC and other application (Archive, 3rd-party…etc.) is supported but highly not recommended
  • Lync 2013 Control Panel not supported on Chrome or Firefox
  • Lync stress & Performance tool is not supported in production AD environment
  • Lync 2013 support Unified Contact store only with Exchange 2013
  • Lync 2013 support high-resolution pictures up to 648 x 648 with Exchange 2013
  • Lync 2013 does not support Authenticating Proxies
  • XMPP & Lync support only for Presence and IM, A/V and application sharing are not supported
  • Lync 2013 SBA while having OCS 2007 R2 still in the infrastructure is not supported

So that’s about it for now, if I learned something new I’ll update this article, and also don’t be shy to put something on the comment so I can add it here.

Author: Lyncdude

A Senior Service Engineer with more than 9 years of experience in Microsoft Exchange and Microsoft Lync Server / Skype for Business. Egyptian guy lives and works in Frankfurt - Germany. what is written in this blog is my own opinion and thoughts, not my employer and does not reflect their opinion

13 thoughts on “Supported or not Supported, this is the Question”

  1. Some more from my list (mixed Lync 2010 and 2013 issues seen in the field):

    Lync 2010 attendant cannot be paired with LPE phones via USB, CAP cannot be added as RGS agent, Lync 2010 attendant cannot participate in formal RGS agent group (there is no button in the client to open the RGS website, indeed manually you can browse to the RGS website to login, but stil…), Lync calls are forked to a maximum 20 endpoints and not more (for example you cannot add more than 20 people to your team call group, otherwise not all will receive your call), CAP cannot access the device update service (check it: it will get a Non-200-OK from IIS)

    Edge is supported in a so-called DMZ-AD (which is different from the internal AD of course!)
    On the other hand you can add trustedapp to the FE for SEFAUTIL in Lync 2013, so that does not need a new FQDN and host anymore. Just saying.

    Nice list though.

  2. Great post!
    I have a comment on the following statement: “Trusted application not Supporting other Lync roles collocated with it”
    Which is true for most scenarios, but when it comes to the SEFAUtil from the reskit, this is supported on a frontend server (if the reskit can be called “supported” 😉 )
    Keep it up!

  3. Hi. Am a bit confused on the “Cold Standby” comment, which seems to indicate you can’t have active users either side of a pooled pair ? From the Lync Ignite PPT files (which I can’t upload here), Module 2 – Architecture and Manageability: “Notes: In Lync 2013, two pools in different datacenters can be paired in order to provide Disaster Recovery. A service on the Front End is used to copy all required data between the pools. If a pool is lost, an administrator can enable Disaster Recovery and failover to the failover pool.

    It is recommended to run the pools at maximum 50% capacity in an active-active mode, so that each pool is able to take over the full load of the pared pool.

    Please advise.

      1. Hi Andy,

        sorry i was in a vacation with limited internet connectivity 🙂
        this part is little confusing for me too, but what i remember is that you can have two pool in two different datacenters paired, one is active and the other is Standby, and in this case to be supported by Microsoft the Standby pool must have no users homed on it.

        if you going to use both pools, them make sure you have enough resources on them to serve the total number of users you have.

  4. Metropolitan Pool – Single pool stretched between two data centers is not supported (supported if same network without routing)
    >> from my really long discussions with Microsoft my understanding is stretching the pool over more the one really close location (say room) is not supported. Even stretching the pool over two data centers located in same building considered not supported without any additional prerequisits. We especially discussed a case where Lync EE pool should be stretched over two DC connected with leased fiber with nearly unlimited BW on same L2 network (10Gb, didicated to Lync was an option, 10km distance between DC) – Microsoft declined to support this configuration.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: