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

"actual combat training for system engineers"

-09-deploy an instant messaging system

-01-deploy front-end servers-6-Design Topology

Author: endless learning

QQ communication group: 454544014

Refer to:

Create and publish new topology

Https://technet.microsoft.com/en-us/library/dn933913.aspx

Create a topology:

1. Log in to the front-end server

two。 Click Skype for Business Server 2015 Topology Builder.

3. In Topology Builder, select New Topology. You will be prompted for a location and file name to save the topology. Provide a meaningful name for the topology file and accept the default extension .tbxml. Click OK.

4. Navigate to the location where you want to save the new topology XML file, enter a name for the file, and then click Save.

5. On the define Primary Domain page, enter a name for the primary SIP domain for your organization, and then click next.

6. On the specify additional support domains page, enter a name for the other domain, if any, and then click next.

7. On the define first site page, enter a name and description for the first site, and then click next.

Cloud computing (China) Co., Ltd.

8. On the specify site details page, enter location information for the site, and then click next.

Shanghai

Shanghai

China

9. On the successfully defined new topology page, make sure that the open new front-end wizard when this wizard closes check box is selected, and then click finish.

Define a front-end pool:

1. On the define a new front-end pool page of the define a new front-end pool wizard, click next.

two。 On the define front-end pool FQDN page, enter the fully qualified domain name (FQDN) of the pool you want to create, click Enterprise Edition front-end pool, and then click next.

3. On the define computers in this pool page, enter the computer FQDN for the first front-end server in this pool, and then click add. Repeat this step for any other computers (up to 8) that you want to add to this pool, and then click next.

4. On the Select Features page, select the check box for the functionality you want the previous end pool to have. For example, if you deploy only instant messaging (IM) and status features, you can select the Conferencing check box to allow multiparty IM, but you cannot select the phone in-call (PSTN) Conferencing, Enterprise Voice, or call allow Control check boxes because they represent voice, video, and collaborative conferencing features.

5. On the Select juxtaposed Server role page, you can juxtapose the mediation server on the front-end server or deploy it as a stand-alone server.

Mediation servers can be juxtaposed on the front-end pool.

If you plan to juxtapose the mediation server on the Enterprise Edition front-end pool, make sure that the appropriate check box is selected. The server role will be deployed on the pool server.

If you plan to deploy the mediation server as a stand-alone server, clear the appropriate check box. After the deployment of the front-end server is complete, the mediation server is deployed in a separate deployment step.

6. The Associate Server role with previous end Pool page allows you to define server roles and associate server roles with front-end pools. The following roles are available:

7. On the define SQL Storage page, do one of the following:

8. On the define File share page, do one of the following:

\\ 061-SFBBE01.i-x-Cloud.com\ FileShare_SFB

9. On the specify Web service URL page, do one or both of the following:

10. If you select Conferencing on the Select Features page, select Associate Pool with Office Web Apps Server on the Select Office Web Apps Server page, and then click New (or select an existing Office Web Apps Server from the drop-down list).

11. In the define a new Office Web Apps server dialog box, type the fully qualified domain name (FQDN) of the Office Web Apps Server computer in the Office Web Apps server FQDN box; when you do this, the Office Web Apps Server discovery URL is automatically entered into the Office Web Apps server discovery URL box.

Https://041-OOS01.i-x-Cloud.com/hosting/discovery/

twelve。 On the define archived SQL Storage page, select an existing instance or SQL Server, or define a new instance to store the data associated with the archived data.

13. On the define Monitoring SQL Storage page, select an existing instance or SQL Server, or define a new instance to store the data associated with the monitoring data.

14. The configuration is complete, please click finish.

Configure a simple URL:

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

two。 In the simple URL pane, select the phone access URL: (dial-in) or Conference URL: (meeting) that you want to edit, and then click Edit URL.

3. Update the URL to the desired value, and then click OK to save the edited URL. The example shown here has changed the phone dial-in URL to https://pool01.contoso.net/dialin.

4. If necessary, use the same steps to edit the meeting URL.

Select a central management server:

1. Start Topology Builder: click start, click all programs, click Microsoft Lync Server 2013, and then click Lync Server Topology Builder.

two。 Right-click the Lync Server 2013 node, and then click Edit Properties.

3. In the Central Management Server pane, select the front-end server where you want to install the central management server, and then click OK.

Publish Topology:

1. Click Skype for Business Server 2015 Topology Builder.

two。 Choose to open the topology from a local file. If you are on the computer that defines the topology, it will be in the location you saved in the previous steps. Typically, this is the documents folder for the user who configured the topology.

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

4. On the publish Topology page, click next.

5. On the Select a Central Management Server page, select the front-end pool.

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

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 OK.

7. Click next to complete the publishing process.

For the changes to the following simple URL to take effect, you must update the corresponding DNS record. Depending on how the certificate is configured on the front-end pool and the controller pool, the certificate may also need to be updated.

For more information, refer to the product documentation.

Https://dialin.i-x-Cloud.com

Https://meet.i-x-Cloud.com

Https://admin.i-x-Cloud.com

Skype for Business Server can be updated with the changes defined in the topology by running the local installer on each server in the following list.

Important: server changes made in Topology Builder must be replicated to servers in your topology. Verify that you copied successfully before continuing with setup.

Server FQDN: 071-SFBFE01.i-x-Cloud.com, pool FQDN: SFBFEPool01.i-x-Cloud.com

*

Possible questions:

C:\ Users\ Administrator.i-x-Cloud > setspn-L i-x-Cloud\ administrator

Registered ServicePrincipalNames is used for CN=Administrator,CN=Users,DC=i-x-Cloud,DC=com:

MSSQLSvc/061-SFBBE01.i-x-Cloud.com:1433

MSSQLSvc/061-SFBBE01.i-x-Cloud.com

C:\ Users\ Administrator.i-x-Cloud > setspn-D MSSQLSvc/061-SFBBE01.i-x-Cloud.com:1433 i-x-Cloud\ administrator

Unregister ServicePrincipalNames for CN=Administrator,CN=Users,DC=i-x-Cloud,DC=com

MSSQLSvc/061-SFBBE01.i-x-Cloud.com:1433

Updated object

C:\ Users\ Administrator.i-x-Cloud > setspn-D MSSQLSvc/061-SFBBE01.i-x-Cloud.com i-x-Cloud\ administrator

Unregister ServicePrincipalNames for CN=Administrator,CN=Users,DC=i-x-Cloud,DC=com

MSSQLSvc/061-SFBBE01.i-x-Cloud.com

Updated object

C:\ Users\ Administrator.i-x-Cloud > setspn-L 061-SFBBE01

Registered ServicePrincipalNames is used for CN=061-SFBBE01,CN=Computers,DC=i-x-Cloud,DC=com:

MSSQLSvc/061-SFBBE01.i-x-Cloud.com

MSSQLSvc/061-SFBBE01.i-x-Cloud.com:1433

WSMAN/061-SFBBE01

WSMAN/061-SFBBE01.i-x-Cloud.com

TERMSRV/061-SFBBE01

TERMSRV/061-SFBBE01.i-x-Cloud.com

RestrictedKrbHost/061-SFBBE01

HOST/061-SFBBE01

RestrictedKrbHost/061-SFBBE01.i-x-Cloud.com

HOST/061-SFBBE01.i-x-Cloud.com

C:\ Users\ Administrator.i-x-Cloud > setspn-L i-x-Cloud\ administrator

Registered ServicePrincipalNames is used for CN=Administrator,CN=Users,DC=i-x-Cloud,DC=com:

C:\ Users\ Administrator.i-x-Cloud >

*

8. When the publishing process is complete, click finish.

After successfully publishing the topology, you can begin to install a local copy of the central management storage on each server running Lync Server 2013 in the topology. We recommend that you start with the first front pool.

This article has been completed!

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.