Step by Step Installing Lync Server 2013 Persistent Chat Collocated on Standard Edition Front End - Part 3

We are on a journey installing the various Lync Server 2013 roles. Today we will install the Persistent Chat role collocated on our Lync Server 2013 Standard Edition Front End! I would like to give Elan Shudnow credit as I read over his excellent Persistent Chat with Enterprise Pool articles before launching on installing this collocated edition.


  • Presumes a Lync Server 2013 Std. FE called FE01.lab.local (see)
  • Since we are installing Chat on an existing Std. Front End, most things are taken care of already
  • Install full SQL (SQL 2008 R2 or SQL 2012) as a new instance called CHAT. You can follow the instructions here.

Next will define a Persistent Chat pool in our topology. Let’s Open Topology Builder

add chat pool

Define the new Chat Pool. Use the FQDN of our trusty Front End: FE01.lab.local and check Single computer pool.

define pool

Next. Now give this Chat pool a name. (just anything is fine)

name of chat pool

Next. Click new to define a new SQL Server Store. We will use the SQL instance we installed for our chat role, so SQL Server FQDN = FE01.lab.local and Named Instance = CHAT

sql store

Our next item is defining the file store. Since this is a lab we will just use the existing Front End share we already setup for the FE which is \\FE01.lab.local\share. Click Finish.


We are done with the topology and you are given a chance to review it—everything looks great!

finished topology

Let’s publish our topology by going Action | Topology | Publish…


Click Next.


Watch the publish Wizard complete. when done click Finish.


The next thing we will do is open the Lync Deployement Wizard and Update the Lync Server System by clicking Install or Upgrade Lync Server System. (this will install the chat services and install the SQL database)

install or update lync server system

Click the Run button with Step 2.


Click Next.


Watch as install happens and click Finish when done.


Now we are ready to start our newly installed Chat services. Click Run.


We can checkup that Lync Server Persistent Chat is successfully running…sure enough, great!

is running

Next we need to login to the Lync Server Control Panel to configure our shiny new Persistent Chat server. Click on Persistent Chat | Persistent Chat Policy and check Enable Persistent Chat and click Commit.


Next we will add a Category. Click Category and New.

chat category

Next we need to add our Administrator user (user we are using to run Lync Powershell further down) to the “RTC Local Administrators” group. This is a local group on the Lync Front End Server, so to do this Open the “Computer Management” and open “Local Users and Groups”.

add user to RTC local admins

After this, log out and back into Windows get the new rights.

Next we will add a new chat room. Let’s drop into Lync Powershell and run

New-CsPersistentChatRoom -Name “XXX” -Category “FE01.lab.local\rd

Next we will add a user to this new Chat room by running the below Powershell:

add member to chatroom

After this we can login to our Lync client and use the Chat!

lync client

Continue your lab with more articles in this Lync Server 2013 Step by Step Series:


  1. Went throught your scenario and got "all channel servers are down"! Any ideas?


  2. Me too same message in the control panel....

  3. Did anyone found a solution for the issue?

  4. have you installed an instance of full SQL?
    also, at what point are you all getting this message?

  5. Yes, I've installed a Full SQL Instance.

    I'm getting one warning on the creation category menu... that says: "all channel servers are down"

    I found some help on this link:

    However, unfortunately the powershell command is not working, it says:

    Set-CsPersistentChatActiveServer : A positional parameter cannot be found that
    accepts argument 'Add=""'.
    At line:1 char:1

  6. I am getting the same error, when i open the Persistent Chat Tab > Category it gives (1 Warning: All the channel servers are down) , i noticed that the "Lync Server Persistent Chat" service always stops by itself i run it manually, i see its status green in the topology but after sometime it stops again.
    the event viewer doesn't have any error logs.
    the machine has 12 GB RAM and 110 GB disk space....
    any idea about this !!!! ???

    1. M,

      When i get a chance (could be a while) i will look at this. In the mean time post the question here:

  7. Hi Matt,
    Thank you for creating yet another detailed documentation for Lync 2013.

    I ran into the same issue where I too got the "all channel servers are down" warning which turns into an error when I try to add users.

    Here is what I did to fix it-
    1. First, I went to Topology Builder and deleted the Chat Pool I had created.

    2. Second, I went to Lync Deployement Wizard and Update the Lync Server System by clicking Install or Upgrade Lync Server System.

    3. I made the sa account I am using for Lync as an enterprise admin.

    4.I then went back and followed your steps again with a few changes. I did not create another instance for SQL but used the default instead.

    Now I did not receive the warning and error messages in the Microsoft Lync Server Control Panel>Persistent Chat.

    Hope this helps someone!

    1. what do you mean by "I made the sa account I am using for Lync as an enterprise admin."

  8. Hi Again,
    For some reason the New-CsPersistentChatroom command that you provided didn't work for me.

    Below is an example of what did.

    New-CsPersistentChatRoom -Name "ITChatRoom" -PersistentChatPoolFqdn ""-Category "IT"

  9. This comment has been removed by the author.

  10. This comment has been removed by the author.

  11. You may also consider that you can setup Chat using the SQL Express database that is already installed on the SE Lync server - see comments from This would be yet another nice way to reduce the server count.

    Persistent Chat Server can be deployed on the Standard Edition server. The Persistent Chat Server Back End Server and the Persistent Chat Compliance database can be collocated on the Standard Edition server on the local SQL Server Express Back End Server. For details about components that can be collocated there, see Supported Server Collocation in the Supportability documentation.

  12. I've been reading your posts and they have helped me immensly deploy Lync. For that i thank you.

    I have deployed PC and am able to create a room via the powershell script, however i cannot from the client. When i do, i get an error that states "User is not SIP-Enabled". I get the same error when i try to manage a room that i was made member of through powershell. *i have added myself as a creator and am a memer of every Cs and RTC group possible.

    Any insight would be graciously accepted.

    thank you.

  13. Hey Matt nice post...

    I followed through and created the Category and Rooms fine, they look exactly the same as yours when I run the get-cspersitentchatroom -identity cmdlet. However for some reason my users I enabled for this room are not getting the corresponding persistent chat button on their Lync clients (and yes they are on the 2013 client). Any idea what is up with that?

  14. Hi Matt,

    Have you got any guidance for deploying a stand-alone Persistent Chat server?



  16. By selecting the default db instance this worked for me. However, I had to delete the previous chat instance, run setup again and restart the server.

  17. I get an error that the fqdn is already in use.
    So unfortunatly I can't seem to add a persistent chat pool on the front end server. Step 1 works but Step 2 gives a warning that the fqdn is already in use.
    Anyone know a way around it?

  18. Getting the same error: All the channel servers are down.

    I have tried everything within all of the links provided and still dead in the water. Any other bright ideas?

    1. You have to have the "Message Queuing" feature installed.
      1) Open Server Manager
      2) Right click features - Click Add Features
      3) Expand Message Queuing
      4) Expand Message Queuing Services
      5) Select Message Queuing Server and Directory Service Integration
      6) Click Install
      7) Publish the topology in the tomology builder (ensure no errors)
      8) Rerun all steps in the deployment wizard
      It should be working now.

  19. Hello
    I am getting this error

    "the following principals are not known"

    any help on how to solve this??

  20. hi,

    I tried to install lync server std 2013 following your above instructions and recive an error in "step 2 setup lync server components, the error message is:

    "Prerequisite not satisfied: The following Internet Information Services (IIS) role services must be installed before attempting to install this product: Static Content, Default Document, HTTP Errors, ASP.NET, .NET Extensibility, Internet Server API (ISAPI) Extensions, ISAPI Filters, HTTP Logging, Logging Tools, Tracing, Client Certificate Mapping Authentication, Windows Authentication, Request Filtering, Static Content Compression, Dynamic Content Compression, IIS Management Console, IIS Management Scripts and ToolsPrerequisite not satisfied: You must install the Media Foundation feature or Desktop Experience feature of Windows before attempting to install this product."

    can you help

  21. I also had an issue with the Persistent Chat service starting (then stopping a short time later) which made the chat channel unavailable.

    Since all my Lync services runs as "Network Service" I resolved it by creating a new SQL Express instance on the standard server (I called it LyncChat) and adding Network Service to the DB Admins for that instance.

    After that, I removed the unhappy Persistent Chat service (remove it from the topology, publish, run the Lync add/remove components wizard) then configured the Persistent Chat service again (with my new settings) in the Topology Manager then published. After running the Lync add/remove components wizard on my server again everything worked perfectly.

    Personally I do not like using SQL Authentication unless I absolutely have to. This worked for me even though it would be more secure to use a domain user with permissions restricted to the ones Lync needs (and only the ones that Lync needs).

    Thanks for the great writeup, it got me 99% of the way there!

  22. Great articles Matt. However upon installing (co-locating) persistent chat on my Lync 2013 Standard Edition with SQL Express, the services won't start. I get this error in the eventvwr:

    The server is not compatible with the database at Data Source=(local)\rtc;Initial Catalog=mgc;Integrated Security=SSPI


    Microsoft Lync Server 2013, Persistent Chat could not start due to the following exception:
    Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Exceptions.StopServerException: Unexpected DB version.
    at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.TransportServerBase.Initialize()
    at Microsoft.Rtc.Internal.Chat.Server.Channel.Server.ChannelServer.Initialize()
    at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.MgcServiceBase.startServer()
    at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.MgcServiceBase.createAndStartServer().

    It isn't SQL Express 2012 SP1, should I install SP1 from Windows Update?

    1. You need to install CU3 and restart the server running chat. you can find CU3 here

  23. thanks for the article i have gone through it and got everything working,

    i was getting the error where I was unable to start the persistent chat service and this would then show the error where chat channel unavailable.

    i installed the hotfix found at

    installed the lyncserver update and let this run.

    restarted the server and the service started and i was able to set up the persistent chat category.

    hope this help out

  24. Many thanks for this. Please can you confirm if i can install SQL onto the front end server for running persistent chat, or if SQL needs to be installed on a seperate server? Or will persistent chat run using SQL express?

    Many thanks

  25. Hi Matt, I have installed Persistent Chat in my Lync 2013 environment, but I continuously get the banner on the client saying "Your chat room access may be limited due to an outage" I have un-installed and reinstalled Persistent chat, over, using a default and instance and named instance, to no avail. I have also removed and re applied all the updates, this still has not rectified the issue. I noticed in my snooper logs that I get SIP/2.0 481 Call Leg/Transaction Does Not Exist now I am getting a SIP/2.0 486 Busy Here.

    It shows a connection between myself and the endpoint 100 trying then 200 OK before I get those errors, what could be the issue?