Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Microsoft Lync Server 2013 : Persistent Chat Deployment (part 2) - Topology Update

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
12/4/2014 8:26:50 PM

Topology Update

As with all Lync Server roles, the Topology Builder must be updated to include Persistent Chat before the server role is installed. Follow these steps to update the Lync topology to include Persistent Chat:

1. Log on to a system where the Lync Server 2013 administrative tools are installed using an account that is a member of the Domain Admins and CsAdministrator groups, and open the Lync Server Topology Builder.

2. At the prompt, select Download Topology from Existing Deployment to retrieve the current topology from the Central Management Store.

3. At the Save Topology As prompt, select a name and location for the Topology Builder file and click Save.

4. In the left pane, expand the Lync site where Persistent Chat will be installed, expand Lync Server 2013, and then right-click on the Persistent Chat pools node and select New Persistent Chat Pool.

5. At the Define the fully qualified domain name (FQDN) screen, enter the FQDN that will be used for the Persistent Chat pool. If Persistent Chat will be collocated with a Standard Edition Front End, the FQDN entered here must be the FQDN of the Front End Server. If Persistent Chat will be deployed using separate servers, the FQDN entered will be new to the topology. After the FQDN is entered, choose either the Multiple computer pool or Single computer pool option, and click Next.


Tip

Although a new FQDN is created in the topology for Persistent Chat pools that are deployed on separate hardware, it is not necessary to enter the FQDN of the Persistent Chat pool as an internal DNS record. The Front End Server handles all the routing for Persistent Chat without requiring DNS queries.


6. If the Multiple computer pool option was selected on the preceding screen, the Define the computers in this pool screen appears. Enter the FQDN of each system that will be added as a Persistent Chat Server, and click Add to add each to the pool. When finished, click Next.


Note

If the Single computer pool option was selected, the Standard Edition Front End Server is automatically chosen as the Persistent Chat Server, since this is the only option.


7. At the Define properties of the Persistent Chat pool screen, enter a display name for the pool, and keep the default Persistent Chat port number of 5041. Select from among the listed options to enable compliance, or to define this pool as the default for the Lync site. If the Multiple computer pool option was selected earlier, the option to enable disaster recovery is also presented. After the desired options are selected, click Next.

8. At the Define the SQL Server Store screen, several SQL options are presented, as shown in Figure 1. To use a SQL Server that is not currently part of the topology, click New, enter the FQDN of the new SQL Server, enter the instance name if the default instance is not being used, and the SQL mirroring option if high-availability will be used. To use a SQL Server that is already part of the topology, use the drop-down menu to select the SQL Server that will be used. If SQL mirroring will be used for high-availability with this server, select this option and then click New to enter the information for a new SQL store for this purpose, or use the drop-down menu to select one that is already part of the topology. If automatic failover will be used requiring a SQL Server mirroring witness, enable this option as well, and click New to enter the information for a new system to act as a SQL witness, or use the drop-down menu to select one that is already part of the topology. After the SQL Server Store options have been selected, click Next.

Image

Figure 1. Persistent Chat SQL Server Store options.

9. If the compliance option was enabled on an earlier screen, the Define the Compliance SQL Server Store screen appears, and presents the same SQL options for the compliance store that were presented for the Persistent Chat Store. To use a SQL Server for compliance that is not currently part of the topology, click New, enter the FQDN of the new SQL Server, enter the instance name if the default instance is not being used, and the SQL mirroring option if high-availability will be used. To use a SQL Server for compliance that is already part of the topology, use the drop-down menu to select the SQL Server that will be used. If SQL mirroring will be used for high-availability with this server, select this option and click New to enter the information for a new SQL store for this purpose, or use the drop-down menu to select one that is already part of the topology. If automatic failover will be used requiring a SQL Server mirroring witness, enable this option as well, and click New to enter the information for a new system to act as a SQL witness, or use the drop-down menu to select one that is already part of the topology. After the compliance SQL Server store options have been selected, click Next.

10. The Define the File Store screen appears, as shown in Figure 2. If using a file store that is already part of the topology, use the drop-down menu to select the existing file store. If a new file store will be defined, select Define a new file store and enter the fully qualified name of the file server as well as the file share name. When finished, click Next.

Image

Figure 2. Persistent Chat file store options.


Tip

When using a new file store for Persistent Chat, the file store does not need to be created before it is defined in Topology Builder. However, it must be created before the topology is published.


11. If the option to install the chat pool using separate servers was chosen on an earlier screen, the Select the Next Hop Server screen will appear. Use the drop-down menu to select the next hop pool for traffic sent from this Persistent Chat pool, and then click Finish to complete the wizard and return to the Topology Builder.

12. The Persistent Chat pool details are now displayed in Topology Builder, as shown in Figure 3.

Image

Figure 3. Persistent Chat pool in the Topology Builder.

13. From the Action drop-down menu, select Topology, and then select Publish.

14. At the Publish Topology screen, click Next to continue.

15. If the option to define a new SQL Server store was chosen on an earlier screen, The Create Databases screen now appears, as shown in Figure 4. Verify that the correct target database server for the Persistent Chat pool is selected. Note that the wizard defaults to the option of automatically determining the file locations for the Persistent Chat database. If alternative database paths are needed, for example, if dedicated volumes have been created on the target SQL Server for database and log files, then select the target store in the wizard and click the Advanced button. The Select Database File Location dialog is then presented. To specify alternative paths for the database files, select the option for Use These Paths on Target SQL Server; then enter the specific paths to the database files and the log files on the target server, and click OK. Click Next to continue.

Image

Figure 4. Topology Builder database options.

16. The topology updates are now published, and the new Persistent Chat databases are created on the target SQL server. When the topology has been successfully published, click Finish to complete the topology update for Persistent Chat.

Other -----------------
- Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 2) - Processing meeting requests according to policy
- Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 1) - Providing policy direction to the Resource Booking Attendant
- Microsoft Exchange Server 2013 : Mailbox management - Mail-enabled contacts, Mail users
- Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 2) - Processing moderation requests, Moderated mailboxes
- Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 1) - Moderated groups
- Microsoft Exchange Server 2013 : Mailbox management - Shared mailboxes , Recalling messages
- SQL Server 2012 : Transact-SQL - Functions, Triggers
- SQL Server 2012 : Transact-SQL - Stored Procedures
- SQL Server 2012 : Transact-SQL - Transactions
- SQL Server 2012 : Transact-SQL - Data Manipulation Language (part 2)
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server