Tuesday, September 10, 2013

Lync 2013 Server Prerequisites (per roles and with powershell script)

Lync 2013 Server Software Prerequisites:


Lync 2013 requires several additional software to be installed and has the need of certain roles and features, as well as hotfixes.
Since I'm missing a scripted PowerShell installation, segregated into Lync 2013 roles, I decided writing this detailed Blog, based on Microsoft Technet article and experiences. It shows you all requirements  and prerequisites for each Lync Server Roles and all supported Operating Systems.

Especially with the additional software you need to install, the installation sequence is important, therefor .NET Framework is a prerequisites for PowerShell 3.0 and Identity Foundation

As a common question; Which prerequisites do we have if I need the Administrative tools only. You simply can consider the Administrative Tools as a server role, therefor you need the same prerequisites as listed in the common section for "All Server Roles required".
The other components, e.g. Visual C++ or SQL Tools....

Regarding the Visual C++ Runtime: Best is you install this component by ONLY using the installation media. Microsoft C++ 2012 x64 Runtime -  11.0.50727 if you try installing any other version, you will run into an issue. 
Check my blog article about this issue here.


Windows 2008 R2

All Server Roles require:



Additional on all Standard and Enterprise Frontend Server:

  •  .NET 3.5 (activated by default)
  •  SilverLight (optional)
  •  prerequisite KB2646886 for IIS 7.5 (http://support.microsoft.com/kb/2646886/en-us)
      FIX: Heap corruption occurs when a module calls the InsertEntityBody method in IIS 7.5
      NOTE: Install this Hotfix only after IIS Components are installed!
Import-Module ServerManager
Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-HTTP-Activation, Web-Asp-Net, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS, Desktop-Experience

Director:


  •  prerequisite KB2646886 for IIS 7.5 (http://support.microsoft.com/kb/2646886/en-us) FIX: Heap corruption occurs when a module calls the InsertEntityBody method in IIS 7.5
  • NOTE: Install this Hotfix only after IIS Components are installed!

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, NET-HTTP-Activation, Web-Asp-Net, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS


Mediation:

No more additional prerequisites

 

Edge:

No more additional prerequisites

pChat:

We need Microsoft Message Queuing (Server and Services)
Add-WindowsFeature MSMQ-Services



Note:
Remember, with Windows Server 2008 R2 you need to import the Server Manager module first.
Import-Module ServerManager




Windows 2012 and Windows 2012 R2

All Server Roles require:

  •  Windows PowerShell 3.0 (is installed by default)
  •  Microsoft .NET Framework 4.5 (http://go.microsoft.com/fwlink/p/?LinkId=268529) Additional Step's after Installation: Select WCF Activation if it isn’t already selected. Then select HTTP Activation, or include in PowerShell
  •  Windows Identity Foundation 3.5 (activate via Server Manager)
    or add via PowerShell
    Add-WindowsFeature
    Windows-Identity-Foundation

Additional on all Standard and Enterprise Frontend Server:

  •  .NET 3.5 (must be manually activated)
  •  SilverLight (optional)

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS, Desktop-Experience, Windows-Identity-Foundation -Source D:\sources\sxs



Director:

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS, Windows-Identity-Foundation -Source D:\sources\sxs


Mediation:

No more additional prerequisites


Edge:

No more additional prerequisites

pChat:

Add-WindowsFeature MSMQ-Services
---------------------------------------------------------------

Additional Information:

Do not install any Winsock Layered Service Providers (LSP) software, on any Front End Servers or stand-alone Mediation Servers. Installing this software could cause poor media traffic performance.
A LSP Software for example it:
Microsoft Internet Security and Acceleration (ISA) Server client software


Lync 2013 Survival Branch Server

In this section regarding the SBS (the equivalent "self-build" SBA:), I assume Windows Server 2012/ 2012 R2 is used:
As written, all server role have requirements in common, therefore to realize the SBA has its Registrar, Lync Frontend Service, the same overall requirements are valid too:

All Server Roles require:

  •  Windows PowerShell 3.0 (is installed by default)
  •  Microsoft .NET Framework 4.5 (http://go.microsoft.com/fwlink/p/?LinkId=268529) Additional Step's after Installation: Select WCF Activation if it isn’t already selected. Then select HTTP Activation, or include in PowerShell
    Add-WindowsFeature NET-WCF-HTTP-Activation45, Web-Asp-Net45
  •  Windows Identity Foundation 3.5 (activate via Server Manager)
    or add via PowerShell
    Add-WindowsFeature
    Windows-Identity-Foundation


10 comments:

  1. Is there any reason, why your powershell command for 2012 server does not contain windows-identity-foundation ?

    ReplyDelete
    Replies
    1. well normally, you should activate Identity Foundation via the Server Manager before you install the other requirements. Generally you can add it into the script, it doesn't matter.
      In the past, we intitiated like described on this page and also did the recommended patching part by part
      i hope this helps you

      Delete
  2. IF the link to the IIS Hotfix is broken, please have a look here:
    http://www.microsoft.com/en-us/download/details.aspx?id=34852

    ReplyDelete
  3. Additional Update for Servers running Windows 2012 R2:
    http://support.microsoft.com/kb/2901554

    ReplyDelete
  4. Thanks for providing this blog post. I just installed Director servers for the first time. The Director prerequisite script for Server 2012 (and 2008 too I believe) is missing the component Web-Dyn-Compression.

    ReplyDelete
    Replies
    1. Hi Jason, according the latest update with Lync 2013, the Static Content Compression is sufficient and Dynamic Content Compression is not necessary

      Delete
  5. Thomas good article! Just one thing there needs to be a space on the director script at the -Source portion.

    ReplyDelete
  6. thanks for the piece, does edge server need any prerequisite that needs to be installed through powershell like Front end servers or not. thanks

    ReplyDelete
    Replies
    1. Hi Tope, well it needs the "All Server roles require" pre-reg. hope this helps you.

      Delete