Shulou(Shulou.com)06/03 Report--

This post enters the fourth part of the Skype for business 2015 comprehensive deployment series: installing a Skype for business Server 2015 server (1). This article takes the lync.itwish.cn server as an example to demonstrate the installation, and introduces in detail the prerequisite installation of Skype for Business Server 2015, the creation of file sharing, the installation of management tools, the preparation of Active Directory, the creation of DNS records for Skype for Business Server 2015, and the creation and release of new topology steps in Skype for Business Server 2015. I hope to correct the imperfections of this article in the comments section. Thank you very much.

Overview of Skype for business 2015 installation process

Skype for Business Server installation involves a variety of different procedures. The process required to make Skype for Business Server work properly in your environment varies depending on the details of the environment. The process of getting Skype for Business Server online for the first time involves eight main steps. You can complete steps 1 through 5 in any order. However, steps 6, 7, and 8 must be completed in the order shown in the chart after steps 1 to 5. These eight steps include:

Prerequisites for Skype for Business Server 2015 installation: install prerequisites on all servers that make up the Skype for Business Server topology.

Create file shares in Skype for Business Server 2015: create file shares that will be used by servers in the entire Skype for Business Server topology.

Install administrative tools in Skype for Business Server 2015: administrative tools include topology generator and control panel. Administrative tools must be installed on at least one server in the topology or on a 64-bit management workstation running Windows, a version of the operating system supported by Skype for Business Server.

Prepare Active Directory:Skype for Business Server for Skype for Business Server 2015 to work closely with Active Directory. You must prepare the Active Directory domain to collaborate with Skype for Business Server. This process will be completed in the deployment wizard and executed only once for the domain.

Create a DNS record for Skype for Business Server 2015: for Skype for Business Server to function properly, a large number of DNS settings must be configured. This makes the client know how to access the service and let the server know what is going on with each other.

Create and publish a new topology in Skype for Business Server 2015: to install a Skype for Business Server system on each server in the topology, you must first create and publish a topology. When you publish a topology, the topology information is loaded into the central management storage database.

Install Skype for Business Server 2015 on servers within the topology: after the topology is loaded into central management storage and Active Directory knows which server will perform which roles, you need to install the Skype for Business Server system on each server in the topology.

Verify the topology in Skype for Business Server 2015: after you publish the topology and install the Skype for Business Server system components on each server in the topology, you are ready to verify that the topology works as expected. This includes verifying that the configuration has been propagated to all Active Directory servers so that the entire domain knows that Skype for Business is available in the domain.

Installation prerequisites

First configure the computer name lync, set the default ip address 172.16.10.120, and join the itwish.cn domain environment

To enable windows update update, please use Windows Update to make sure that Windows Server has been updated to the latest version.

New features: Windows Update, .NET Framework 3.5functionality, .NET Framework 4.5functionality (HTTP activation), media basics, remote server management tools (AD DS and AD LDS tools), Windows Identity Foundation 3.5, etc. Prerequisites can be installed by running the following PowerShell command

Add-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

Create file share on the server side of domain control

Skype for Business Server supports basic Windows Server file sharing. However, the file share does not explicitly provide high availability. For high availability environments, it is recommended that you use distributed File system (DFS) file sharing.

Create a folder C:\ sharepoint on the domain server side to share. Right-click the folder and select Properties; then click Advanced sharing; check share this folder, click permissions, add the local Administrators group, grant permission: full Control, change, read permission, and then click OK.

Create DNS related records

For Skype for Business Server to function properly and be accessible to users, DNS records must be provided.

Description

Record type

Name

Parse to

Load balancing type

Internal Web Service FQDN

A

Web.itwish.cn

VIP of the internal Web service

Supported software and hardware

Pool FQDN

A

Pool.itwish.cn

IP address of the server SFB

DNS

SFB FQDN

A

Lync.itwish.cn

IP address of the server SFB

DNS

Skype for Business automatic discovery

A

Lyncdiscoverinternal.itwish.cn

VIP of the internal Web service

Supported software and hardware

Meeting simple URL

A

Meet.itwish.cn

VIP of the internal Web service

Supported software and hardware

Dial in simple URL

A

Dialin.itwish.cn

VIP of the internal Web service

Supported software and hardware

Web Scheduler simple URL

A

Scheduler.itwish.cn

VIP of the internal Web service

Supported software and hardware

Manage simple URL

A

Admin.itwish.cn

VIP of the internal Web service

Supported software and hardware

Old version found

SRV

_ sipinternaltls._tcp.itwish.cn

Pool FQDN (port 5061)

Not applicable

Log in to the DNS server and open Server Manager. In the console tree of the SIP domain, expand the forward lookup zone, then expand the itwish.cn area where you want to install Skype for Business Server, right-click the SIP domain, and select New Host (An or AAAA). In the name box, type the name of the host record (the domain name will be automatically appended), and in the IP address box, type the IP address of a single front-end server Then select create associated pointer (PTR) record. As shown in the figure.

Continue to create A records for all servers in the planned deployment. DNS server-side Skype related A records

To create a service record (SRV) record, right-click the SIP domain and select other New Records. In Select Resource record Type, click Service location (SRV)

Then click create record. Click Services, and then type _ sipinternaltls. Click Agreement, and then type _ tcp. Click Port number, and then type 5061. Click Host providing this service, and then type the FQDN "pool.itwish.cn" of the pool or Standard Edition server.

View DNS server SRV records

Verify that DNS clicks start, then type cmd and press Enter. Type nslookup or press Enter. If you want to support legacy clients and create SRV records, type set type=srv at the nslookup command prompt and press Enter to verify. Type _ sipinternaltls._tcp. (for example, _ sipinternaltls._tcp.contoso.local) and press Enter

Install Skype for Business Server 2015 administrative tools

Insert the Skype for Business Server 2015 installation media. Please double-click the setup.exe program to "install". The installation media requires Microsoft Visual C++ to run. Microsoft Visual C++ will be installed automatically.

Smart setup is a new feature in Skype for Business Server 2015 that allows you to connect to the Internet to check for updates during installation. This ensures that you get the latest product updates during installation, providing a better experience. Click install to begin the installation.

Read the license agreement carefully and if you agree to the terms, select "I accept the terms of the license agreement", and then click OK.

So far. The core components of Skype for Business Server 2015 are installed on the server. The core components include the following: the Skype for Business Server 2015 deployment Wizard, which provides a startup panel to install the various components of Skype for Business Server 2015, and the Skype for Business Server 2015 Management Shell, a preconfigured PowerShell program that allows you to manage Skype for Business Server 2015.

After you complete the installation of the core components, the Skype for Business Server 2015 deployment wizard starts automatically. In addition to the core components, you need to install the Skype for Business Server 2015 Topology Builder and Skype for Business Server 2015 dashboards on at least one server in the environment. Click install Management tools on the deployment wizard.

When the installation is complete, click finish

Administrative tools have now been added to the server: Skype for Business Server 2015 Topology Builder, which is used to build, deploy, and manage topologies; and Skype for Business Server 2015 Control Panel, which is used to manage installation.

Prepare Active Directory

Log in as a user with Schema Admins credentials for the Active Directory domain. Open the Skype for Business Server deployment wizard and click the prepare Active Directory link.

Step 1: prepare the architecture and review the prerequisite information for step 1, which can be accessed by clicking the drop-down menu under the heading of step 1. Click run in step 1 to start the prepare Schema wizard. Note that you should perform this process only once for each deployment, and then click next. When the schema is ready, you can click View Log to view the log. Click finish to close the prepare Active Directory wizard, and then return to the prepare schema step.

Step 2: verify the replication of the schema partition. Log in to the domain controller of the domain. Open ADSI Edit from the tools drop-down menu in Server Manager. On the actions menu, click Connect to. In the connection Settings dialog box, under Select a known naming context, select Schema, and then click OK.

Under the schema container, search for "CN=ms-RTC-SIP-SchemaVersion". If this object exists and the value of the rangeUpper property is 1150 and the value of the rangeLower property is 3, the schema update and replication are successful. If this object does not exist, or if the values of the rangeUpper and rangeLower properties are not the specified values, the schema has not been modified or copied.

Step 3: prepare the current forest. Check the prerequisite information for step 3, which can be accessed by clicking the drop-down menu under the heading of step 3. Click run in step 3 to launch the prepare current Forest wizard. Note that you should perform this process only once for each deployment, and then click next. Specify the domain in which the common group will be created. If the server is part of a group, you can select Local Domain, and then click next. After you have prepared the forest, you can click View Log to view the log. Click finish to close the prepare current forest wizard, and then return to the prepare Active Directory step.

Click the Skype for Business Server Management Shell on the applications page to start PowerShell. Type the command Get-CsAdForest, then press Enter. If the result is LC_FORESTSETTINGS_STATE_READY, the forest has been prepared successfully, as shown in the figure.

Step 4: verify the replication of the global catalog. On the domain controller in the forest where you are running the forest preparation (preferably at the remote site of another domain controller), open Active Directory users and computers. In Active Directory users and computers, expand the domain name of the forest or subdomain. Click the users container in the left pane and look for the common group CsAdministrator in the right pane. If CsAdministrator is displayed in addition to other new generic groups that begin with Cs, the replication of Active Director is successful. If these groups are not displayed, you can force replication or wait 15 minutes before refreshing the right pane. When the group is displayed, it indicates that the replication is complete.

Step 5: prepare the current domain. These steps must be completed in each domain that has a Skype for Business Server object, or the service may not start. This includes any type of Active Directory object, such as a user, contact object, administrative group, or any other type of object. If necessary, you can use Set-CsUserReplicatorConfiguration-ADDomainNamingContextList to add only domains with Skype for Business Server objects. Review the prerequisite information for step 5 and click run in step 5 to launch the prepare current Domain wizard. Note that you should perform this process only once for each domain in the deployment, and then click next. Once the domain is ready, you can click View Log to view the log. Click finish to close the prepare current Domain wizard, and then return to the prepare Active Directory step.

Step 6: verify replication in the domain. Click the Skype for Business Server Management Shell on the applications page to start PowerShell. Use the command Get-CsAdDomain to verify replication in the domain, and the result is LC_DOMAINSETTINGS_STATE_READY, indicating that the domain was replicated successfully.

Step 7: add a user to provide administrative access to the Skype for Business Server dashboard. Log in as a member of the Domain Admins group or the RTCUniversalServerAdmins group. Open Active Directory users and computers, expand the domain, click the users container, right-click CSAdministrator, and select Properties. In CSAdministrator Properties, click the members tab. On the members tab, click add. In Select a user, contact, computer, service account, or group, type the user names admin and administrator that you want to add to the CSAdministrators group. Click OK. On the members tab, verify that the selected user or group exists. Click OK.

Log out and log back in to Windows to update your security token with the new Skype for Business Server security group, and then reopen the deployment wizard. Verify that there is a green check next to prepare Active Directory to confirm that the process is successful, as shown in the figure.

Create and publish a new topology

You can use the Skype for Business Server Topology Builder to design, define, configure, and publish topologies.

Important: Skype for Business Server requires SQL Server to be installed to function properly. The master database is called central management storage. If you are deploying Enterprise Edition, these databases are created when you publish the topology using the following steps. In this case, the topology generator will ask you to provide connection information for the SQL Server installation.

Create a new topology

Log in as a user with access to Topology Builder. Open the Skype for Business Server Topology Builder.

Select New Topology, and then click OK. Select a location and file name for the topology profile.

Note: the topology configuration is saved as a topology generator XML (.tbxml) file. When you publish the topology, you push the configuration information from the file to the SQL Server server. When you open Topology Builder in the future, you can download the existing configuration directly from SQL Server to Topology Builder and then republish it to SQL Server or save it as a Topology Builder configuration file.

On the define Primary Domain screen, enter Primary SIP Domain, and then click next.

Add additional supported SIP domains, and then click next.

Enter a name and description for the first site (location), and then click next, as shown.

Enter City, Province / municipality, and country Code for the site, and then click next.

Click finish to complete the process of defining the new topology. The New Front end wizard starts automatically.

Define a front-end pool or Standard Edition Server

Review the wizard prerequisites, and then click next.

Enter the fully qualified domain name (FQDN) of the pool and select Enterprise Edition Front end Pool or Standard Edition Server, and then click next, as shown in the figure.

Tip: Skype for Business Server Enterprise Edition may include multiple servers that provide front-end roles through collaboration. When multiple servers are used to perform role responsibilities, this configuration is called a pool. Therefore, multiple servers that provide front-end roles through collaboration are also called front-end pools. Skype for Business Server Standard Edition may contain only one server to provide front-end roles. Even if the role is provided through only one server, it is often referred to as a front-end pool.

Enter the fully qualified domain name (FQDN) of all computers in the pool, and click next, as shown in the figure.

Select the features that will be included in this topology, and then click next, as shown in the figure.

On the Select a juxtaposition server role page, you can select a juxtaposed mediation server on the front-end server, or choose to deploy it as a stand-alone server. If you are juxtaposing the mediation server on the Enterprise Edition front-end pool, make sure that this check box is selected and the server role will be deployed on the pool server.

From the Associate Server role with previous end Pool page, you can define server roles and associate server roles with front-end pools. Next step is selected by default

Next, you will define the SQL Server storage for the topology. In this example, we use the default instance, we enter SQL Server FQDN and configure the relevant high availability settings, and then click OK, as shown in the figure.

To use existing SQL Server storage that has been defined in the topology, select an instance in SQL Storage.

To define a new SQL Server instance to store pool information, click New, and then specify SQL Server FQDN in the define New SQL Storage dialog box.

To specify the name of the SQL Server instance, select named instance, and then specify the name of the instance.

To use the default instance, click default instance.

To use SQL mirroring, select enable SQL mirroring, select an existing instance, or create a new instance.

Define the file shares you want to use. In this example, we will click define New File Store, enter File Server FQDN and File sharing, and then click next.

To use a file share that has been defined in the topology, select use previously defined file share.

To define a new file share, select define a new file share, in the File Server FQDN box, enter the FQDN of the existing file server where you want to place the file share, and then enter the name of the file share in the File share box.

On the specify Web service URL page, you must decide whether you need to override the internal Web service pool base URL.

Important: base URL refers to the Web service identity of URL minus https://. For example, if the full URL of the pool's Web service is https://web.itwish.cn, the base URL is web.itwish.cn.

You will be asked to select an Office Web Apps server. Click New to launch the dialog box. In the define a new Office Web Apps server dialog box, in the Office Web Apps server FQDN box, when you type the FQDN; of your Office Web Apps server to do this, your Office Web Apps server search URL should be automatically entered into the Office Web Apps server search URL box.

If the Office Web Apps server is installed locally and is in the same network area as Skype for Business Server, you should not select the option "deploy Office Web Apps server in external network (that is, perimeter / Internet)"; if the Office Web Apps server is deployed outside the internal firewall, select the option "deploy Office Web Apps server in external network (that is, perimeter / Internet)".

Next, you will define the SQL Server storage used for archiving. In this example, we use the default instance, we enter SQL Server FQDN and configure the relevant high availability settings, and then click OK, as shown in the figure.

Next, you will define the SQL Server storage for monitoring. In this example, we use the default instance, we enter SQL Server FQDN and configure the relevant high availability settings, and then click OK, as shown in the figure.

Click finish to complete the configuration.

Configure simple URL

In Topology Builder, right-click the Skype for Business Server top-level node, and then click Edit Properties, as shown in the figure.

Define an optional management simple URL

In Topology Builder, right-click the Skype for Business Server node, and then click Edit Properties.

In the manage access URL box, enter the simple URL that you want to use for administrative access to the Skype for Business Server control panel, and then click OK.

Tip: it is recommended that you use the simplest URL as the management URL as possible. The simplest option is https://admin. . The administrative URL can be an internal or external domain, such as contoso.local or contoso.com (as long as any record can be parsed in the internal DNS).

Publish and verify the topology

Check that all simple URL are configured correctly.

Verify that the SQL Server-based server is online and available to the computer on which the topology generator is installed, including all necessary firewall rules.

Verify that the file share is available and that the appropriate permissions are defined.

Verify that the correct server roles are defined in the topology to meet the deployment requirements.

Verify that the server exists in Active Directory Domain Services (AD DS). This action is performed automatically when you join the server to the domain. If the topology has been validated and there are no validation errors, the preparation for publishing the topology should be ready. If a validation error occurs, you must correct the error before you can publish the topology.

Right-click the Skype for Business Server 2015 node, and then click publish Topology.

On the publish Topology page, click next.

On the Select Central Management Server page, select a front-end pool, as shown in the figure.

Note: you can click Advanced to configure the database file location.

On the Select Database page, select the database you want to publish.

You can also click Advanced. By using advanced SQL Server data file placement options, you can choose between the following options:

Click OK.

Automatically determine the location of database files-this option determines the best operating performance based on the disk configuration on the SQL Server-based server by distributing log and data files to the best location.

Use SQL Server instance defaults-this option places log and data files on a SQL Server-based server by using instance settings. This option does not use the operational capabilities of the SQL Server-based server to determine the best location for logs and data. Typically, SQL Server administrators move logs and data files to a location suitable for SQL Server-based server and organizational management processes.

Click next to complete the publishing process.

Note: there is often a failure in this step that the SQL Server database cannot be created. When the process cannot be completed, an error is displayed, as shown in the figure. The most likely reason is that the user trying to create the database does not have the appropriate permissions, or that the SQL Server system cannot be contacted due to firewall or other network problems.

After you complete the publishing process, the system will provide you with a link to open a list of next steps. Click Click here to open the to-do list to see the next steps, and then click finish.

During database creation, the message "completed with warning" does not indicate that an error has occurred. For Skype for Business Server to work properly, the installation process must change the settings in SQL Server. This event is logged as a warning when the settings in SQL Server are changed, allowing the SQL Server administrator to understand exactly what the installation process accomplished. If you receive a warning, you can select the record and click View Log to view the details of the warning.

After successfully publishing the topology, you can begin to install a local copy of the central management storage on each server running Skype for Business Server 2015 in the topology.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.