I’ve recently had the opportunity to deploy Skype for Business Server 2019 on Windows Server 2019 in a Skype for Business Server 2015 environment and decided to capture the process so I can write this blog post demonstrating what the deployment process looks like.
Before I proceed, the deployment guide I will be using can be found here:
Skype for Business Server 2019
Forest and Domain Functional Level
Verify that the forest and domain functional level is at one of the following levels:
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
Windows Roles and Features
Install the required roles and features with the following PowerShell cmdlet:
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, Server-Media-Foundation, Telnet-Client
Skype for Business Server 2015 Coexistence
I could not find any documentation identifying which CU a legacy SfB 2015 environment needs to be in order for coexistence to work properly as the following article is the only section I found in the document:
I ended up going with the latest January 2019 (CU8) for the environment I was installing SfB 2019 in and have not had any problems.
Preparing Install for Skype for Business Server 2019
Launch the Setup.exe executable as administrator:
Those who have installed SfB 2015 would find that the interface hasn’t changed much:
As there is already a Skype for Business Server 2015 deployment in the environment, I would not need to run the Prepare first Standard Edition server until I am ready to remove the legacy pool (https://docs.microsoft.com/en-us/skypeforbusiness/migration/move-the-central-management-server). I’ve also noticed that the Prepare Active Directory step already had a Complete check mark beside it, which most likely because there hasn’t been any changes from SfB 2015.
Installing Administrative Tools
Proceed to run Install Administrative Tools:
Defining Skype for Business Server 2019 Topology
Launch the Topology Builder from the start menu and download the existing topology:
Begin by defining a file store for the new Skype for Business Server 2019 environment by navigate to Shared Components > File stores then right click and select New File Store…:
Fill in the FQDN (make sure you use the FQDN and not the short server name) of the file server that will host the SfB files and the share name:
With the file store defined, proceed to create the new standard front-end server by navigating to Skype for Business Server 2019 > Standard Edition Front End Servers then right click and select New Front End Pool..:
Enter the FQDN of the server name that the front-end services will be installed onto:
Select the appropriate features required for the front-end server:
As this is a standard edition deployment, a local SQL Server Express will be installed:
Select the previously defined file store:
**Note that the path in the screenshot below should be the FQDN of the server.
Fill in the external URL for the Web Services URL:
Associate the existing or new Office Web Apps Server if one exists in the environment:
The new front-end server should now be created:
Proceed to publish the topology:
Review the warnings to ensure that they are not deployment impacting.
For those who are interested, the required security permissions for the file store that was defined earlier are automatically configured after publishing the topology:
Installing Skype For Business Server 2019 Front-End Server
Proceed and run Install or Update Skype for Business Server System:
Run the Install Local Configuration Store:
Proceed to run the Setup or Remove Skype for Business Server Components:
With the components successfully installed, proceed to request, install and assign the certificates:
Note that the OAuthTokenIssuer already had a certificate issued because there is an existing SfB 2015 deployment in the environment.
Depending on the way you’ll be publishing the Web services external service, you may want to assign a certificate issued by a public Certificate Authority but for the purpose of this demonstration, we’ll create a certificate for all 3 services from an internal Microsoft Enterprise CA:
Proceed to leave the Assign this certificate to Skype for Business Server certificate usages checked and click Finish:
Assign the certificate to the services:
All of the services should now have a check mark beside them:
Start Skype for Business Server 2019 Services
Scroll down to the Start Services section:
Click on the Run button for Service Status (Optional) to bring up the Services console:
Run the Start-CsWindowsService cmdlet in the Skype for Business Server Management Shell to start all of the services:
Confirm that all the services start:
Launch the Skype for Business Server 2019 Control Panel to confirm accessibility:
You can now continue with any other migration tasks such as moving pilot users over to verify functionality and/or migrate over services over.