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

Author:


Comments

  1. UnknownNovember 27, 2013 at 8:19 AM

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

    ReplyDelete
    Replies
    1. Thomas PoettNovember 27, 2013 at 8:29 AM

      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. Thomas PoettFebruary 25, 2014 at 3:38 PM

    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. Thomas PoettSeptember 18, 2014 at 9:46 AM

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

    ReplyDelete
  4. UnknownNovember 12, 2014 at 6:23 PM

    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. Thomas PoettNovember 13, 2014 at 8:21 AM

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

      Delete
  5. UnknownFebruary 18, 2015 at 7:04 PM

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

    ReplyDelete
  6. UnknownApril 19, 2016 at 7:26 PM

    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. Thomas PoettApril 20, 2016 at 7:56 AM

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

      Delete

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more