Skype For Business 2015 play Series 5: install the back-end database

Skype For Business 2015 play Series 5: install the back-end database

The previous introduction to the Skype For Business Server 2015 active directory preparation and certificate and file sharing preparation work, today to introduce you to the SFB back-end server preparation work.

Like other Microsoft services, SFB's back-end server uses Microsoft's own SQL Server database, and its main function is to store status information, users' contact lists, meeting data containing all current meeting status-related permanent data, and meeting scheduling data. (the back-end server and back-end database of the monitoring and archiving server can be juxtaposed in the deployment.)

Skype For Business Server 2015 has the following restrictions on the version of SQL Server:

In this environment, we use two SQL Server 2014 with CU6 patches to achieve high availability of back-end servers. Let's start with today's content: install SQL Server 2014 on SQL01 and SQL02 servers

First of all, log in to the SQL01 server. I have finished configuring the IP address, changing the computer name and joining the domain for the SQL01 server, as shown in the following figure:

Insert the installation CD of SQL Server 2014 into the SQL01 server and click "run SETUP.EXE":

Click "install"-"install a new SQL Server standalone or add features to an existing installation":

At the location of the product key, enter the product key and click next:

Check here to accept the license terms and click next:

PS: if you don't check it, you can't click the next step.

At the Microsoft Update location, you can choose to use Microsoft Update to update or click next:

At the location of the installation rules, confirm that it is correct, and click next:

When setting the role location, keep the "SQL Server feature installation" checked by default, and click next:

Select the desired feature and click next:

Select "named instance" in the instance configuration location, and then enter your own named instance name. Of course, you can also use the default instance, and click next:

In the server configuration location, configure the service account, and set the startup type to "automatic", and click next:

Set the authentication mode in the database engine configuration location and specify the SQL Server administrator, and click next:

The report configuration location remains the default, click next:

Confirm that it is correct, click install:

When the installation is complete, click close:

At this point, the installation of SQL01 is complete, and the installation process of SQL02 is exactly the same as that of SQL01. There is no more introduction here!