Lync Server 2013 Now Supported on Windows Server 2012 R2


With the release of the Updates for Lync Server 2013: October 2013, Lync Server 2013 is now supported on Windows Server 2012 R2.  You may see Event IDs 32402 and 61045 logged on the Lync Server 2013 Front End Servers:

Event ID 32042

Log Name: Lync Server
Source: LS User Services
Date: 10/15/2013 4:02:05 AM
Event ID: 32042
Task Category: (1006)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncFE01.contoso.local
Description:
Invalid incoming HTTPS certificate.
Subject Name: LyncFE01.contoso.local Issuer: Contoso-CA

Cause: This can happen if the HTTPS certificate has expired, or is untrusted. The certificate serial number is attached for reference.

Resolution: Please check the remote server and ensure that the certificate is valid. Also ensure that the full certificate chain of the Issuer is present in the local machine.

 

Event ID 61045

Log Name: Lync Server
Source: LS MCU Infrastructure
Date: 10/15/2013 4:02:20 AM
Event ID: 61045
Task Category: (1022)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncFE01.contoso.local
Description: The DATAMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection).
The Web Conferencing Server failed to send C3P notifications to the focus at https:// LyncFE01.contoso.local:444/LiveServer/Focus.

Cause: The Front End may not be running correctly or may be unreachable over the network (broken HTTPS connection) from the MCU. Unavailability of The C3P channel affects conference controls, and can also prevent users from joining, starting conferences.

Resolution: Verify that the Front End server is running correctly and that network connectivity and an HTTPS Connection can be established between the MCU and the Front End server.

 

If so, follow the workaround listed in KB2901554.

Comments (24)

  1. CJADuva says:

    I did an in-place upgrade from 2012 to 2012 R2 and my Lync servers are now junk. Nothing works.

  2. Anonymous says:

    @Paul

    All roles are supported on Windows Server 2012 R2.

  3. shawn harry says:

    Awesome news. Now we just need the same for Exchange!

  4. wondering says:

    Is 2012 R2 officially supported? If so why is this not updated? technet.microsoft.com/…/gg398588.aspx

  5. dodeitte says:

    @wondering

    Yes, with the October 2013 updates, Lync Server 2013 is supported on Windows Server 2012 R2.  The documentation is in the process of being updated, but it takes some time.

  6. Jaime says:

    Upgrade Lync October 2013 updates.  Update from windows server 2012 to Windows Server 2012 R2 and Lync services do not start up.  hmmm Supported.  Maybe not.

  7. ViperGTS says:

    Will this support an in place upgrade from Server 2012 to 2012 R2, if Lync 2013 is running with the October updates in place or will we required to do a full migration to implement the new server version?

  8. Thomas Wenzl says:

    The official system requirements have been updated with the 2012 R2 information:

    technet.microsoft.com/…/gg398588.aspx

  9. ViperGTS says:

    The documentation now lists Windows Server 2012 R2 as a supported OS but the documentation does not specify if Windows Server 2012 can be upgraded to Windows Server 2012 R2 in-place, without reinstalling Lync 2013.

  10. Oscar Loria says:

    Hi dodeitte

    One question I have a Lync 2013 Environment running on Windows Server 2008 R2, and we got tons of Event ID 61045.

    I would like to know if the fix suggested in the KB Article also applies for Windows 2008 R2 w/ Lync Server 2013 Enterprise ?

  11. Thorsten5 says:

    Has somebody of you tried to install Lync 2013 on a 2012 R2 Server allready? We tried it out and have some Problems regarding online Meetings and PowerPoint presentation. The Lync 2013 Client tries to upload the PPT but after some time there is an error "Sorry, we ran into a problem displaying the presentation."

    We allready tried UCWA on Server 2012 R2 and 2008 R", no difference.

  12. bill says:

    Thorsten, install the followng update on the WAC server and this should resolve your issue…

    support.microsoft.com/…/en-us

  13. shawn says:

    Is it supported to do an in-place upgrade of the OS from 2012 to 2012 R2 on a Lync Front-End server?

  14. Abdullah says:

    I also did in place update, doesn’t work.
    @CJADuva, what is the quickest fix?

  15. JasonFZ says:

    In place upgrade from 2012 to 2012 R2 with Lync 2013 definitely hosed Lync like other posters have said, Lync 2013 may be supported as a fresh installation on 2012 R2 but going from 2012 to 2012 R2 does not work at this time. Thank goodness for test environments and VMware snapshots, if you have Lync 2013 and are thinking about an in-place upgrade, you would be well served to wait until that path is officially supported (if ever).

  16. RobM says:

    Lync 2013 on Server 2012R2: tons of errors and th eFE service is forever in starting process….

  17. nnatic says:

    leave it to me to not read this before my in place OS upgrade. My Lync server is now also a paperweight. Time to revert the snapshot. I love you visualization!

  18. Balázs MENTES (MSFT) says:

    Yes, this is not documented, but in-place upgrades of Windows OS is not supported if Lync is installed on the server.

  19. Anthony says:

    Would a better method be to shutdown FE Server and rebuild with Server 2012 R2 as a fresh OS one at a time is this possible

  20. soder says:

    Balázs MENTES (MSFT):

    How am I supposed to find this out, if its not written down? Should I mindread the Redmond Lync team members for all such things? What is the supportability document for Lync server 2013 good for then, if such things are simply forgotten from it?

  21. Steffen P. says:

    Soder,
    There is no way the Lync team can list every non-supported setup.
    If it’s listed as supported then go ahead and use that information, if not listed, expect it’s not supported.

    You wouldn’t put bicycle breaks on your car even though it’s not listed as non-supported would you ?

    Br
    Steffen

  22. soder says:

    Steffen P.:
    forgive me to say this, but your example is more far-fetched than mine.

    Refusing to support in-place OS updates is a god damn 1-liner in the supportability section, its not that the documentation would need thousands of such lines to extend with. And yes, the damn Lync is far the most picky and sensitive product of the entire server-line
    of MS, so it DOES make sense to list all the possible ways it can be broken.

  23. AM says:

    Reissing new Cert by MMC not Lync Wizard and then attach the new 1 fixed the issue

  24. paul says:

    What about Director and 2012R2? Outdated Documentation for Director and the OS support or not supported?
    https://technet.microsoft.com/en-us/library/gg398560.aspx