One of the new features in Lync 2013 is the Persistent Chat. Maybe not everyone will deploy this, but nonetheless it’s a great feature. Persistent Chat is basically a group chat that we can collocate in the Front End Server.
In my lab I was discovering new settings and policies, and after a while I got this message: “Your chat room access may be limited due to an outage”.
I thought, “Why am I receiving this message if I didn’t deploy Persistent Chat?”. The thing is, when we enter the Persistent Chat menu, we receive a warning that we need, at least, one pool with Persistent Chat installed to add a Persistent Chat category.
However, if we go to Persistent Chat Policy, we don’t get the same warning.
And if we want we can enable Persistent Chat in Global Policy.
As it shows in the following image, after enabling Persistent Chat in the Policy we don’t receive the same warning or any warning at all.
After we enable Persistent Chat on a topology without having Persistent Chat installed, the clients will display the message: “Your chat room access may be limited due to an outage.” And you know that even if users don’t use chat room they will complain about this message.
This is only a warning. As we know, in a real deployment no one usually enables an option they don’t need/deploy.