So I like to keep my lab up to date therefore I decided to see if I could install Skype for Business Server 2016 on the newly RTM’d Server 2016.
Note this configuration is now supported as per https://technet.microsoft.com/en-gb/library/dn951388.aspx
I am installing Skype for Business Enterprise edition load balanced against Kemp Virtual Load Master. This has already been configured as per this guide http://gj294.co/2dE6osr
This article also assumes you have an Internal Certificate Authority setup and configured.
1. Install the prerequisites
Run the following command on the Front End Servers:
Install-WindowsFeature NET-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Dir-Browsing, 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, BITS –Source d:\sources\sxs –Verbose –Restart
Replacing d: with your Server 2016 media location.
This worked fine.
Now install Silverlight on your Front End servers using this link http://gj294.co/2e6aMUH.
IE in Server 2016 does not allow downloads by default so open IE > Settings > Internet Options > Security > Custom Level
Under the Downloads section Enable Downloads. Or you can run it from a location where you have already downloaded it.
2. Create a File Share
You now need to create a file share for the Skype For Business (SfB) front end pool. You can create either a normal windows share or a Distributed File System (DFS) file share if you require high availability. The file share should not be on one of the front end servers. The file share is sued to store shared data of each enterprise edition pool or standard edition server. It stores application, user services and web services data for both enterprise edition and standard edition while enterprise edition also stores windows fabric dump and trace files.
I will be installing my SfBFileShare on my 2 Domain Controllers.
I recommend you follow this guide http://gj294.co/2dSrt5s
3. Configure SQL Server
Install SQL on a separate Server NOT on the Front End servers.
The following SQL editions are supported
- Microsoft SQL Server 2014 Standard (64-bit edition), and we recommend running with the latest service pack.
- Microsoft SQL Server 2012 Standard (64-bit edition), and we recommend running with the latest service pack.
- Microsoft SQL Server 2008 R2 Standard (64-bit edition), and we recommend running with the latest service pack.
However, I am using SQL 2016 Enterprise Edition 64 Bit.
You can use this guide if you are not familiar with installing SQL http://gj294.co/2eDqZRC
4. Create your DNS Records
Follow this guide to create your DNS records http://gj294.co/2deauLE
5. Install Administrative Tools
Insert the media into your SfB Front End Servers and run setup.exe located in x:\setup\amd64\setup.exe
The installation media requires Microsoft Visual C++ to run so leave that to install it shouldn’t take long.
Ensure you select Connect to the Internet to check for updates and click Install.
Once downloaded click Next then you should see the Deployment Wizard:
Click install Administrative Tools and follow the installation wizard.
Click Finish once complete then you will be returned to the Deployment Wizard Screen
6. Prepare Active Directory
Log on as a user that had Schema Admins credentials for your Domain.
In the Skype for Business Server Deployment Wizard, Click Prepare Active Directory.
Complete the three sub-steps for Schema, Forest and Domain to prepare Active Directory
7. Define a Topology
Open Topology Builder from the start menu.
Select New Topology, and click OK
Saved the file somewhere, I always put it on my Desktop.
On the Define the primary domain screen, enter your external domain name that you wish to use as your sip addresses. Normally this is the same as your email domain (eg, microsoft.com), and then click Next.
Add any additional domains you wish to use, and then click Next.
Enter a Name and Description for the location, click Next.
Enter the City, State/Province, and Country/Region Code for the site if you wish, click Next
Ensure Open the New Front End Wizard when this wizard closes is selected and click Finish.
Click Next on the home screen.
Enter the fully qualified domain name (FQDN) of the pool, and select Enterprise Edition Front End Pool. This is the DNS name that points to your Load Balancer or you are using for DNS Load Balancing. It is NOT your Front End servers FQDN.
Click Next.
Enter the FQDNs of the servers you are going to deploy in the pool, and then click Next.
In my environment I only have 2 but this is not recommended in production. For more information on this see http://gj294.co/2e6yX34
Select the features that you wish to be enabled in this topology, and then click Next.
Note: You can enable features later.
Depending on your environment and if you intend to collocate the Mediation server will determine if you select the Mediation Server Colocation check box. In my lab I will select it. Click Next.
Uncheck enable Edge Pool. This will be configured later. Click Next.
You now need to define a new SQL Server instance that you installed earlier to store the SfB pool information, click New.
Specify the SQL Server FQDN in the Define New SQL Store dialog box. Click OK.
Click Next.
Select Define a new file share, in the File Server FQDN box, enter the FQDN of your domain if you are using DFS or enter the FQDN of the server that hosts your file share if not.
Then enter the share name for the file share in the File Share box.
I am using a Kemp hardware load balancer to load balance SIP and HTTP(S) traffic. Therefore, we are not selecting the Override internal Web Services pool FQDN check box. This depends how DNS works in your domain and is a more complex discussion outside the scope of this article.
An Office Online Server (this is the new name for Office Web Apps Server) will be configured later so leave it unchecked and click Finish.
8. Configure the simple URL’s
In Topology Builder, right-click the Skype for Business Server top node, and then click Edit Properties
In the Administrative access URL box, enter the a simple URL you will use for administrative access to Skype for Business Server Control Panel, and then click OK.
This is an internal URL to be resolved by internal DNS server and should never be exposed externally!
9. Publish the Topology
In the Topology Builder right-click the Skype for Business Server 2015 node, and then click Publish Topology.
On the Publish the topology page, click Next.
On the Select Central Management Server page, select a Front End pool.
On the Select databases page, select the databases you want to publish.
Click Next to complete the publishing process then click Finish.
10. Install Skype for Business
Launch Deployment Wizard page from the Start Menu.
On the Deployment Wizard page, click Install or Update Skype for Business Server System.
Click Run next to Step 1: Install Local Configuration Store
On the Install Local Configuration Store page, make sure that the Retrieve directly from the Central Management store option is selected, and then click Next.
The Local Configuration Store will now install. The local configuration store will act as a read-only replica of the Skype for Business Server Central Management store (CMS).
When the local server configuration installation is complete, click Finish.
Click Run next to Step 2: Setup or Remove Skype for Business Server Components.
Click Next.
This will now install the features on the Front End server that you selected during the Topology Wizard.
Once completed click Finish.
Request & Assign Certificate
Click Run next to Step 3: Request, Install or Assign Certificates.
Click Run next to Step 3: Request, Install or Assign Certificates.
On the Certificate Wizard page, click Request.
On the Certificate Request page fill in the relevant data including selecting All under the SIP domain and, click Next.
On the Certificate Request Summary page, review the information in the summary. If the information is correct, click Next.
Once complete click Next.
On the Online Certificate Request Status page, review the information returned. Note that the certificate was issued and installed into the local certificate store.
By default, the check box for Assign the certificate to Skype for Business Server certificate usages is selected. Click Finish.
On the Certificate Assignment Summary page, review the information presented to make sure that this is the certificate that should be assigned, and then click Next.
Click Finish.
Now select the OAuthTokenIssuer option and click Request.
Fill in the relevant details and click Next.
A certificate will now be requested.
Click Next.
Click Finish.
On the Certificate Assignment Summary page, review the information presented to make sure that this is the certificate that should be assigned, and then click Next
Click Next.
Click Finish.
On the Certificate Wizard page, confirm that all services have a green check to indicate that all have been assigned a certificate, including the OAuthTokenIssuer ,as shown in the figure, and then click Close.
Exit the Deployment Wizard.
Open the Skype for Business Management Shell and run Start-CSWindowsServer command.
11. Install Skype for Business on the Second Front End Server
Log onto your second server and repeat all the tasks in Step 10.
12. Check the Load Balancer to ensure all services at functioning
Log onto your load balancer and ensure all the services are up.
All is good
13. Enable a User to test
Log onto your load balancer and ensure all the services are up.
Open Skype for Business Server Control Panel.
In the left navigation bar, click Users
Click Enable users.
Click Add > Search for Admin > Click OK > Click Enable.
If you receive the following error:
Active Directory operation failed on “Domain Controller Name”. You cannot retry this operation: “Insufficient access rights to perform the operation
Open Active Directory Users & Computers and click View > Advanced Features.
Go to the properties of the user > Security > Advanced
Click Enable inheritance. Or disable. Whichever is the opposite.
Click OK and try to enable the user again in Skype for Business Control Panel. This occurs due to the user having Domain Admin privileges.
14. Test login
Go to a client machine and open Skype for Business client.
Enter the users SIP address and Click Sign In.
Enter the users Password and Click Sign In.
Select yes or no depending on your preferences.
If you get this error then click ok and the username in the format domain\username
Congratulations you have a fully functioning highly available (BASIC) Skype for Business Server 2015 installation running on Windows Server 2016.