The role of Persistent Chat Server allows users to participate in multi-stakeholder thematic conversations persistent over time.

Teams can efficiently share information, ideas and decisions with each other. Discussions are persistent, allowing users in different geographical areas to participate even when they are not simultaneously online.

This role allows you to search content, to create notifications and filters to follow conversations on specific topics.

Since Lync Server 2013, the feature is available directly in the Lync client.

Persistent Chat server is an optional role in Skype for Business 2015. Servers are managed in a dedicated farm and depends on the front end to the routing of the messages.

This role is primarily composed of conversation and compliance services. The Conversation is responsible for persistent chat server database service. The compliance service enables archiving of the content of conversations and events.

Web services, dependent on IIS, they are handled by the front-end server. Web services are used for the publication and recovery files as well as the management of the conference rooms.

Persistent Chat Server uses two databases:

• The database 'mgc' for the hosting of data such as history and the content of conversations, configuration and provisioning of user data
• The database "mgccomp" for compliance data archiving

These databases can be located in the same SQL Server instance or different SQL Server servers.

Persistent cat is the only role Skype for Business server whose farm can be stretched between two sites.

Various architectures options available:

• Environment Standard edition including the role of persistent chat collocated with the front end server
• Environment Standard edition including the role of persistent chat deployed on a dedicated server
• Environment in Enterprise edition including the role of persistent chat deployed on a dedicated server
• Environment in Enterprise edition including the role of persistent chat deployed on several separate servers

The following table summarized the capabilities supported by the role:

This paper presents a Skype for Business 2015 Enterprise Server installation.

The upgrade scenario diagram is as follows:

The prerequisites to deploy Skype for Business 2015 Persistent Chat Server:

The good success of a deployment must take into account all of the technology.

• Operating systems supported for Skype for Business:
   
  • Windows Server 2012 R2 Enterprise OS
  • Windows Server 2012 R2 Standard OS
  • Windows Server 2012 Datacenter OS with SP1
  • Windows Server 2012 Standard OS with SP
  • **Windows Server 2008 R2 (Lync Server 2013 migration required)

• Back end support for the following databases:

• • Microsoft SQL Server 2014 Enterprise (64-bit Edition)
  • Microsoft SQL Server 2012 Enterprise (64-bit Edition)
  • Microsoft SQL Server 2008 R2 Enterprise (64-bit Edition)
  • Microsoft SQL Server 2014 Standard (64-bit edition)
  • Microsoft SQL Server 2012 Standard (64-bit edition
  • Microsoft SQL Server 2008 R2 Standard (64-bit edition)

• Back end support for the following database services:
  • SQL Mirroring
  • SQL Clustering
  • SQL Always On
• Applications required on all servers Skype for Business Persistent Chat:
   
  • Windows PowerShell 3.0
  • Microsoft .NET Framework 4.5
  • Windows Identity Foundation
  • Remote Server Administration Tools
  • MSMQ
     

Step 1: Install prerequisites

Installation prerequisites on Persistent Chat Server with the command:

Add-WindowsFeature Net-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, NET – WCF-HTTP-Activation45, Web-Asp-Net45, MSMQ
 

Step 2: Topology builder

1. The beginning of the installation consists in the creation in the builder of our farm topology of persistent cat in Enterprise version consists of a single server
    
2. Open the topology builder, select Persistent Chat pools and New Persistent Chat Pool
    
   
    
3. Specify the name of your pool, in our case, the chosen option is This pool has multiple servers
    
   
    
   
    
4. You can specify a display name for your farm. Compliance activation option is optional, for this example, it will be enabled
    
   
    
5. Select the SQL Server from host the database mgc
    
   
    
6. Select the SQL Server from host the database mgccomp
    
   
    
7. Specify the file used by the farm share
    
   
    
8. Select your Server Front end as next hop farm
    
   
    
9. The configuration is summarized below
    
   
    
   
     
10. After you have validated the information, we can now publish the topology
     
    
     
11. Select Next
     
    
     
    
     
12. Select Use SQL Server instance defaults
     
    
     
    
     
    
     
13. The help file we callback to validate replication
     
    

Step 3: Installation of the components

1. The installations of the components step takes place on the server from host role
    
2. Run the installation setup and choose 'Install' to deploy the Core module
    
   
    
3. Accept the terms
    
   
    
4. The deployment wizard is now available. Choose install or update the Skype Enterprise Server system
    
   
    
5. Run step 1 to deploy the instance SQL Server Express 2014 going to host a local replica of the CMS
    
   
    
6. Choose the default option and select Next
    
   
    
7. End of the installation from step 1
    
   
    
8. Start step 2. From the information contained in the local replica of the CMS, the deployment wizard will deploy the components assigned machine name declare in the topology builder
    
   
    
9. Choose Next
    
   
    
10. You observe in the logs installation of desired components
     
    
     
11. Start now step 3 to assign a certificate to the role
     
    
     
12. Choose Ask
     
    
     
13. Select certification authority from answer your query
     
    Specify information such as:
     
    – Friendly name
    – Organization name
    – Name of the organizational unit
    – Country/Region
    – Department/Provence
    – City/town
     
    You can choose the 'Advanced' option to specify alternative configurations
     
14. Select "Next" to start the process
     
    
     
    
     
    
     
    
     
15. After you have validated all the information, you can send the query by selecting Next
     
    
     
    
     
16. It is possible at this stage to assign immediation certificate to the role
     
    
     
    
     
    
     
17. Logs allow us to confirm the success of the operation
     
    
     
18. You can run services with the command Start-CsWindowsService
19.  
    
     
20. Validation can be performed with the Get-CsWindowsService command
     
    
     

Step 4: Configuration persistent cat:

1. The security group CsPersistentChatAdministrator allows to grant privileges of Directors for this role (a) of the identified users. Members can access various commands of the role through the PowerShell interface or control panel Skype for Business 2015
    
   
    
2. At this stage, we can now configure strategies servers and users
    
   For example, the configurations will be carried out "globally"
    
3. You can customize the strategies the role servers in Control Panel Skype for Business, navigate 'Persistent Chat' – 'Persistent Chat Configuration.
    
   
    
4. Customizable settings are visible below
    
   
    
5. Now navigate Persistent Chat – Persistent Chat Policy and activate the option Enable Persistent Chat
    
   
    
6. Several permanent chat rooms can coexist and can be arranged into a set of categories on the server. Each chat room belongs to only one category. The categories allow to manage access to chat rooms and the different roles
    
7. The configuration of a category is done in 'Persistent Chat' – 'Category.
    
   
    
8. Select your farm
    
   
    
9. Set the desired settings for this category
    
   
    
   
    
10. The category is now active and possesses no chat room
     
    
     
11. It is possible to associate URLs with permanent chat rooms
     
12. Now navigate through 'Persistent Chat' – 'Add-in '.
     
    
     
13. Select your farm
     
    
     
14. Set the name and the URL
     
    
     
15. The configuration for this example is completed
     

Step 5: User Experience

The user now has a new tab in its Skype business client
 

 
The user now has the required permissions to create a chat room
 

 

1. The selected option directs you to a web page
    
   
    
2. Create a new chat room
    
    
    
3. Set the desired parameters
    
   
    
   
    
4. The permanent chat room is now accessible from your Skype enterprise client
    
   
    
5. Accessible via a single click