Hardware component | Recommended |
---|---|
CPU | Intel Xeon E5-2673 v3 dual processor, 6-core, 2.4 gigahertz (GHz) or higher. Intel Itanium processors are not supported for Skype for Business Server 2019 roles. |
Memory | 32 gigabytes (GB). |
Disk | EITHER: • 8 or more 10000 RPM hard disk drives with at least 72 GB free disk space (two of the disks using RAID 1 and 6 using RAID 10). OR • Solid state drives (SSDs) able to provide the same free space and similar performance to 8 10000 RPM mechanical disk drives. |
Network | 1 dual-port network adapter, 1 Gbps or higher (2 network adapters can be used, but they need to be teamed with a single MAC address and a single IP address). Dual or multi-homed configurations are not supported for Front End Servers, Back End Servers, and Standard Edition servers. As long as they are not exposed to the operating system and are being used to monitor and manage server hardware, you can have out-of-band management systems, such as DRAC or ILO. This scenario doesn't constitute a multi-homed server, and it is supported. |
Hardware component | Recommended |
---|---|
CPU | Intel Xeon E5-2673 v3 dual processor, 6-core, 2.4 gigahertz (GHz) or higher. Intel Itanium processors are not supported for Skype for Business Server 2019 roles. |
Memory | 64 gigabytes (GB). |
Disk | EITHER: • 8 or more 10000 RPM hard disk drives with at least 72 GB free disk space (two of the disks using RAID 1 and 6 using RAID 10). OR • Solid state drives (SSDs) able to provide the same free space and similar performance to 8 10000 RPM mechanical disk drives. |
Network | 1 dual-port network adapter, 1 Gbps or higher (2 network adapters can be used, but they need to be teamed with a single MAC address and a single IP address). Dual or multi-homed configurations are not supported for Front End Servers, Back End Servers, and Standard Edition servers. As long as they are not exposed to the operating system and are being used to monitor and manage server hardware, you can have out-of-band management systems, such as DRAC or ILO. This scenario doesn't constitute a multi-homed server, and it is supported. |
Hardware component | Recommended |
---|---|
CPU | Intel Xeon E5-2673 v3 dual processor, 6-core, 2.4 gigahertz (GHz) or higher. Intel Itanium processors are not supported for Skype for Business Server 2019 roles. |
Memory | 32 gigabytes. |
Disk | EITHER: • 4 or more 10000 RPM hard disk drives with at least 72 GB free disk space (the disks should be in a 2x RAID 1 configuration). OR • Solid state drives (SSDs) able to provide the same free space and similar performance to 4 10000 RPM mechanical disk drives. |
Network | 1 dual-port network adapter, 1 Gbps or higher (2 network adapters can be used, but they need to be teamed with a single MAC address and a single IP address). Dual or multi-homed configurations are not supported for Video Interop Servers and Directors. Edge servers will require two network interfaces that are dual-port network adapters, 1 Gbps or higher (or two paired network adapters, for a total of four, each pair being teamed with a single MAC address and a single IP address, for a total of two pairs). On standalone Mediation Servers, the installation of additional network interface cards (NICs) to allow the configuration of a specific PSTN IP address is supported. |
Windows Server 2019 |
Windows Server 2016 |
Software/role | Details |
---|---|
Windows PowerShell 3.0 | All Skype for Business Server servers need Windows PowerShell 3.0 installed. • This should be installed by default with Windows Server 2016. |
Microsoft .NET Framework | WCF services is a Feature that's installed as a Windows feature, under Server Manager, initially no downloads needed. • You need to make sure, when you install this feature, or if it's already installed and you're checking on it, that the HTTP Activation option is also checked and installed, like so: Don't worry if you get an additional pop-up saying some other things need to be installed for HTTP Activation to be installed. That's normal; click OK and go ahead. If you don't get this pop-up, you can assume those things are already installed and go ahead. Microsoft .NET Framework is usually installed when Windows Server 2016 is installed. Skype for Business Server requires Microsoft .NET Framework 4.7 or 4.8 though, so you'd probably need to update it. You can find the update here |
Media Foundation | For Windows Server 2016, the Windows Media Format Runtime installs with Microsoft Media Foundation. All Front End Servers and Standard Edition servers used for conferencing require Windows Media Format Runtime to run the Windows Media Audio (.wma) files that the Call Park, Announcement, and Response Group applications play for announcements and music. |
Windows Identity Foundation | We need Windows Identity Foundation 3.5 to support server-to-server authentication scenarios for Skype for Business Server 2019. • For Windows Server 2016, there's no need to download anything. Open Server Manager, and go to the Add Roles and Features Wizard. Windows Identity Foundation 3.5 is listed under the Features section. If it's selected, you're good. Otherwise select it and click Next to reach the Install button. |
Remote Server Administration Tools | Role Administration Tools: AD DS and AD LDS tools |
Software/role | Details |
---|---|
Internet Information Services (IIS) | IIS is needed on all Front End Servers, as well as all Standard Edition servers, with the following modules selected: • Common HTTP Features: Default Document, HTTP Errors, Static Content • Health and Diagnostics: HTTP Logging, Logging Tools, Tracing • Performance: Static Content Compression, Dynamic Content Compression • Security: Request Filtering, Client Certificate Mapping Authentication, Windows Authentication • Application Development: .NET Extensibility 3.5, .NET Extensibility 4.5, ASP.NET 3.5, ASP.NET 4.5, ISAPI Extensions, ISAPI Filters • Management Tools: IIS Management Console, IIS Management Scripts and Tools Note that Anonymous Access is also needed, but you get that when you install IIS, so you don't have a place to select it on the list. |
Windows Media Format Runtime | For Windows Server 2016, you'll need to install the Media Foundation feature in Server Manager. You actually can start your Skype for Business Server 2019 installation without this, but you'll be prompted to install it, and then reboot the server, before the Skype for Business Server 2019 install continues. It's better to do it ahead of time. |
Silverlight | You can install the latest version of Silverlight here. |
Microsoft SQL Server 2019 (64-bit edition), and you must run with the latest updates. | Microsoft SQL Server 2017 (64-bit edition), and you must run with the latest updates. |
Microsoft SQL Server 2016 (64-bit edition), and you must run with the latest updates. |
Active Directory objects | Object types |
---|---|
Schema extensions | User object extensions |
Extensions for Skype for Business Server 2015 and Lync Server 2013, to maintain backward compatibility with the previous supported versions | |
Data | User SIP URI and other user settings |
Contact objects for applications (like the Response Group application and the Conferencing Attendant application) | |
Data published for backward compatibility | |
A service control point (SCP) for the Central Management store | |
Kerberos Authentication Account (an optional computer object) |
Certificate | Subject name/common name | Subject alternative name | Example | Comments |
---|---|---|---|---|
Default | FQDN of the pool | FQDN of the pool and FQDN of the server If you have multiple SIP domains and have enabled automatic client configuration, the certificate wizard detects and adds each supported SIP domain FQDNs. If this pool is the auto-logon server for clients and strict Domain Name System (DNS) matching is required in group policy, you also need entries for sip.sipdomain (for each SIP domain you have). | SN=se01.contoso.com; SAN=se01.contoso.com If this pool is the auto-logon server for clients and strict DNS matching is required in group policy, you also need SAN=sip.contoso.com; SAN=sip.fabrikam.com | On Standard Edition servers, the server FQDN is the same as the pool FQDN. The wizard detects any SIP domains you specified during setup and automatically adds them to the subject alternative name. You can also use this certificate for Server-to-Server Authentication. |
Web internal | FQDN of the server | Each of the following: • Internal web FQDN (which is the same as the FQDN of the server) AND • Meet simple URLs • Dial-in simple URL • Admin simple URL OR • A wildcard entry for the simple URLs | SN=se01.contoso.com; SAN=se01.contoso.com; SAN=meet.contoso.com; SAN=meet.fabrikam.com; SAN=dialin.contoso.com; SAN=admin.contoso.com Using a wildcard certificate: SN=se01.contoso.com; SAN=se01.contoso.com; SAN=*.contoso.com | You can't override the Internal web FQDN in Topology Builder. If you have multiple Meet simple URLs, you must include all of them as SANs. Wildcard entries are supported for the simple URL entries. |
Web external | FQDN of the server | Each of the following: • External web FQDN AND • Dial-in simple URL • Meet simple URLs per SIP domain OR • A wildcard entry for the simple URLs | SN=se01.contoso.com; SAN=webcon01.contoso.com; SAN=meet.contoso.com; SAN=meet.fabrikam.com; SAN=dialin.contoso.com Using a wildcard certificate: SN=se01.contoso.com; SAN=webcon01.contoso.com; SAN=*.contoso.com | If you have multiple Meet simple URLs, you must include all of them as subject alternative names. Wildcard entries are supported for the simple URL entries. |
Certificate | Subject name/common name | Subject alternative name | Example | Comments |
---|---|---|---|---|
Default | FQDN of the pool | FQDN of the pool and FQDN of the server If you have multiple SIP domains and have enabled automatic client configuration, the certificate wizard detects and adds each supported SIP domain FQDNs. If this pool is the auto-logon server for clients and strict Domain Name System (DNS) matching is required in group policy, you also need entries for sip.sipdomain (for each SIP domain you have). | SN=eepool.contoso.com; SAN=eepool.contoso.com; SAN=ee01.contoso.com If this pool is the auto-logon server for clients and strict DNS matching is required in group policy, you also need SAN=sip.contoso.com; SAN=sip.fabrikam.com | The wizard detects any SIP domains you specified during setup and automatically adds them to the subject alternative name. You can also use this certificate for Server-to-Server Authentication. |
Web internal | FQDN of the pool | Each of the following: • Internal web FQDN (which is NOT the same as the FQDN of the server) • Server FQDN • Skype for Business pool FQDN AND • Meet simple URLs • Dial-in simple URL • Admin simple URL OR • A wildcard entry for the simple URLs | SN=ee01.contoso.com; SAN=ee01.contoso.com; SAN=meet.contoso.com; SAN=meet.fabrikam.com; SAN=dialin.contoso.com; SAN=admin.contoso.com Using a wildcard certificate: SN=ee01.contoso.com; SAN=ee01.contoso.com; SAN=*.contoso.com | If you have multiple Meet simple URLs, you must include all of them as subject alternative names. Wildcard entries are supported for the simple URL entries. |
Web external | FQDN of the pool | Each of the following: • External web FQDN AND • Dial-in simple URL • Admin simple URL OR • A wildcard entry for the simple URLs | SN=ee01.contoso.com; SAN=webcon01.contoso.com; SAN=meet.contoso.com; SAN=meet.fabrikam.com; SAN=dialin.contoso.com Using a wildcard certificate: SN=ee01.contoso.com; SAN=webcon01.contoso.com; SAN=*.contoso.com | If you have multiple Meet simple URLs, you must include all of them as subject alternative names. Wildcard entries are supported for the simple URL entries. |
Certificate | Subject name/common name | Subject alternative name | Example |
---|---|---|---|
Default | Director pool | FQDN of the Director, FQDN of the Director pool. If this pool is the auto-logon server for clients and strict DNS matching is required in group policy, you'll also need entries for sip.sipdomain (for each SIP domain you have). | pool.contoso.com; SAN=dir01.contoso.com If this Director pool is the auto-logon server for clients and strict DNS matching is required in group policy, you also need SAN=sip.contoso.com; SAN=sip.fabrikam.com |
Web internal | FQDN of the server | Each of the following: • Internal web FQDN (which is the same as the FQDN of the server) • Server FQDN • Skype for Business pool FQDN AND • Meet simple URLs • Dial-in simple URL • Admin simple URL OR • A wildcard entry for the simple URLs | SN=dir01.contoso.com; SAN=dir01.contoso.com; SAN=meet.contoso.com; SAN=meet.fabrikam.com; SAN=dialin.contoso.com; SAN=admin.contoso.com Using a wildcard certificate: SN=dir01.contoso.com; SAN=dir01.contoso.com SAN=*.contoso.com |
Web external | FQDN of the server | Each of the following: • External web FQDN AND • Meet simple URLs per SIP domain • Dial-in simple URL OR • A wildcard entry for the simple URLs | The Director external web FQDN must be different from the Front End pool or Front End Server. SN=dir01.contoso.com; SAN=directorwebcon01.contoso.com SAN=meet.contoso.com; SAN=meet.fabrikam.com; SAN=dialin.contoso.com Using a wildcard certificate: SN=dir01.contoso.com; SAN=directorwebcon01.contoso.com SAN=*.contoso.com |
Certificate | Subject name/common name | Subject alternative name | Example |
---|---|---|---|
Default | FQDN of the pool | FQDN of the pool FQDN of the pool member server | SN=medsvr-pool.contoso.net; SAN=medsvr-pool.contoso.net; SAN=medsvr01.contoso.net |
Certificate | Subject name/common name | Subject alternative name | Example |
---|---|---|---|
Default | FQDN of the appliance | SIP.<sipdomain> (you need only one entry per SIP domain) | SN=sba01.contoso.net; SAN=sip.contoso.com; SAN=sip.fabrikam.com |
Description | SAN entry |
---|---|
Internal Autodiscover service URL | SAN=lyncdiscoverinternal.<sipdomain> |
External Autodiscover service URL | SAN=lyncdiscover.<sipdomain> |
Description | SAN entry |
---|---|
External Autodiscover service URL | SAN=lyncdiscover.<sipdomain> |