Persistent Chat Server is a Lync Server 2013 component that provides chat services and enable users to take part in multiparty topic-based chat sessions. The added value of Persistent Chat Server 2013, compared to the earlier Group Chat Server, is the use of a single client and its integration in the Lync Control Panel for administration tasks. This article outlines the steps that must be run in a coexistence scenario during migration from Group Chat Server 2010 to Persistent Chat 2013.
Author: Mame-Fatou GUEYE, Unified Communications Consultant, Microsoft FRANCE
Technical Reviewer: Sekou Page
Persistent Chat Server is a Lync Server 2013 component that provides chat services and enable users to take part in multiparty topic-based chat sessions. The added value of Persistent Chat Server 2013, compared to the earlier Group Chat Server, is the use of a single client and its integration in the Lync Control Panel for administration tasks.
The following section lists the steps that must be run in a coexistence scenario, during migration from Group Chat Server 2010 to Persistent Chat 2013.
Figure 1. Lync Environment
In your Lync Server 2010 environment, make sure that you have fulfilled prerequisites during your Lync Server 2013 pool deployment.
To prepare for migration in a coexistence scenario
1. Make sure that your Lync 2010 environment is running with the last update.
2. Deploy a complete and functional Lync Server 2013 pool in your Lync environment.
3. Deploy the Lync Server 2013 Persistent Chat pool.
4. Make sure that the next hop of your persistent chat pool is a Lync 2013 Front End pool.
Step 2: Migration procedure
1. Identify the Group Chat server to be migrated.
2. Stop Lync 2010 group chat services on the running Group Chat server:
OCS Group Chat Lookup
3. Make sure that the using account is a member of CsPersisentChatAdministrator group and is a member of the Group Chat Back-End Server System Administrator group.
4. Open the Lync Server 2013 Management Powershell, and run the following cmdlet to export the Group Chat database content: Export-CsPersistentChatData -DBInstance “SQLServer\GCInstance” -DBName Group Chat database Name -FileName “FilePath.zip
5. Copy the content of the Group Chat File Share, as follows:
a. Open Group Chat Server Configuration tool.
b. On the File Repository page, copy the Root Directory path, as shown in Figure 1 below.
c. Copy the content of this directory in the persistent chat file share.
Figure 2. The Root directory path.
6. Stop Persistent Chat Services.
7. Open the Lync 2013 Management Powershell.
8. Verify that the parameter in Filename is the folder exported and run the following cmdlet: Import-CsPersistentChatData –DBInstance “SQLServer\PersistentChatInstance” –FileName “c:\FilePath.zip” –WhatIf
The “Whatif” parameter is recommended because it allows detecting possible warning or errors. These errors must be solved before performing next step.
9. Import chat room information by running the following cmdlet: Import-CsPersistentChatData -DBInstance « SQLServer\PersistentChatInstance » -FileName « FilePath.zip »
10. If any customized category doesn’t exist in your Persistent Chat configuration, the imported Group Chat room will be located in a default Lync 2013 Persistent Chat category: Original Root Category.
11. Start Persistent Chat Services and make sure all Group Chat rooms are well imported.
The steps above summarize the data migration from Lync 2010 Group Chat server to Lync Server 2013 Persistent Chat. As we discussing the coexistence scenario, the Group Chat client must be able to access Persistent Chat Services. To do so. an endpoint must be created.
Scenario 1: Migration must be transparent on users’ side
This scenario requires configuring a new endpoint with the same SIP URI used with the Group Chat Lookup Service. By default, Ocschat@contoso.com is used for Lookup Services. This SIP URI was shared by all Lookup servers in the same Group Chat pool.
1. Delete Group Chat Active Directory Object Ocschat@contoso.com. This URI was used by the Group Chat Lookup service to reach the Chat server.
2. Create the new endpoint: New-CsPersistentChatEndpoint -SipAddress sip:Ocschat@contoso.com -PersistentChatPoolFqdn PersistentChatPool.contos.com
If you are migrating multiple Group Chat pools, make sure that you identify the Lookup services account linked to each pool. This will help you to create as many PersistentChatEndPoint instances as needed. To achieve this, repeat Steps 1 and 2 for each migrating pool.
The legacy client will now be able to use Persistent Chat services and take part in the chat room.
Scenario 2: Creating a new endpoint different from Group Chat Server Endpoint
It’s possible to create a new endpoint different from the Group Chat Server Endpoint, but to make the migration easy and transparent; we recommend using the method above.
Scenario 3: Deploy the Lync 2013 client
The Lync 2013 Persistent Chat client is the same as the Lync 2013 IM client, if Persistent Chat Services is enabled. Using the Lync 2013 client involves migrating the user from the Lync Server 2010 Front End pool to the Lync Server 2013 Front End pool.
After deployment, the Persistent Chat administrator must enable users for Persistent Chat Services through a Lync policy. Here are the steps:
1. Open the Lync Server Management Shell.
2. Run the following cmdlet, if you want to manage Persistent Chat access at the global level: Set-CsPersistentChatPolicy -Identity "global" -EnablePersistentChat $True
At this time, Lync 2010 Group Chat (clients) or Office Communicator 2007 R2 Group Chat (clients) can connect transparently to the new Persistent Chat Server pool.
Persistent Chat servers support Group Chat R2 and 2010 clients. But Lync 2013 Persistent Chat clients do not support connection to legacy servers. Features, such as the upload/download file, are not available at this time in the Lync 2013 client for Persistent Chat usage. However, you can use the Group Chat client to upload and download files in a chat room.
About the Author
Nice Article and Helpful procedure.