Skype for Business Server 2015 prerequisites (pre role and with powershell script)

-

For any other pre Skype for Business 2015 versions, e.g. Lync Server 2013 and the different OS, please refer to the old blog article:
http://lyncuc.blogspot.de/2013/09/lync-2013-server-prerequisites-per.html


Skype for Business 2015 Server Software Prerequisites:


Since the installation of Skype for Business 2015 Server require a modern OS, only the Standard and Data Center version of Windows Server 2012 and 2012 R2 are entitled for an installation.
Both servers having the same prerequisites.
 
Recommendation for Windows Server 2008 R2 is only give for in-place upgrades.


Required HotFixes Windows Server

(please consider the KB 2858668, KB2982006 and KB2533623 for in-place upgrades and fresh installations)
 
Windows Server 2012, KB article 2858668. Download.
Windows Server 2012 R2, KB article 2982006. Download.
Windows Server 2008 R2 KB article 2533623. Download.
Not all HotFixes apply to the different rules, e.g. you only need the 2012 R2 KB2982006 on Skype for Business 2015 Server rules, where the IIS is installed, meaning like the Edge doesn't require this hotfix. 
 
 
Windows 2012/ 2012 R2

All Server Roles require:


Add-WindowsFeature RSAT-ADDS, NET-Framework-Core, NET-Framework-45-Core, NET-Framework-45-ASPNET,  Web-Net-Ext45, NET-WCF-HTTP-Activation45, Windows-Identity-Foundation, Telnet-Client -Source X:\sources\sxs

(-Source X:\sources\sxs, where X should be the drive/ or network location where your Windows Server 2012/2012R2 Server ISO/DVD is found)

The RAST is not required on EdgeServer, but you can install them without any negative impact

On all Frontend Standard and Enterprise Server:

  •   SilverLight (optional)

Add-WindowsFeature 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, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client -Source X:\sources\sxs


 

On all Director:


Add-WindowsFeature 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-Asp-Net45, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client -Source X:\sources\sxs


Video Interop Server:

No more additional prerequisites


Mediation:

No more additional prerequisites

 

Edge:

No more additional prerequisites

pChat:

We need Microsoft Message Queuing (Server and Services)
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

 
(30.07.2015 SBA under Skype for Business 2015 are not yet available, instead we use the SBA Lync 2013)

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
Principally said, it is another Server where you can use the first Windows Feature command line at the top of this article.


Author:

Comments

  1. KorbynJuly 30, 2015 at 7:08 PM

    I think those requirements for All Server Roles was supposed to only be All INTERNAL Server Roles. I believe Edge only should have: "Add-WindowsFeature telnet-client, NET-Framework-Core, NET-Framework-45-Core, Windows-Identity-Foundation" although on one edge server deployment I forgot to install the Windows-Identity-Foundation and so far it appear to be fine...

    ReplyDelete
    Replies
    1. Thomas PoettJuly 31, 2015 at 7:41 AM

      You are right, the RSAT are not required on the Edge server, they are need on server which are domain joined and have the ability running the Skype for Business Management Shell.

      Delete
  2. Alejandro TorresSeptember 15, 2017 at 12:54 AM

    i have problems installing Windows Server 2012 R2, KB article 2982006 in my front end

    ReplyDelete
    Replies
    1. Thomas PoettSeptember 15, 2017 at 8:57 AM

      Hi Alejandro, which problem occurs? if you describe your problem, I'll be able helping you solving it. if you don't want posting it public, you can use the form "contact me directly"

      Delete
  3. UnknownDecember 2, 2021 at 11:09 AM

    hello , Can we run different servers in a Pool on different OS versions ? We have an enterprise edition On premise SFB 2015 setup. Our Edge servers are running on 2008 R2 OS build. one of the Edge server's OS is corrupted. Can we upgrade it to 2012 ?

    ReplyDelete

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 modif...
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, uniqu...
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