A quick post about a misleading error you might experience in a Lync Server 2013 topology with one Persistent Chat Pool servicing multiple sites and front-end pools. Using one Persistent Chat (PS) pool for multiple sites or pools is a supported Topology configuration, but the errors outlined in this blog post are triggered after deploying Persistent Chat, or a new Lync Site using an existing PS Pool, and forgetting to set a Persistent Chat Site or Pool policy. I assume this experience is the same with Skype for Business Server, but I have not verified that.
Forgetting to set the Persistent Chat Policy can be tricky because to the end-user, the Persistent Chat functionality will show up as available in the client, but an erroneous error message will be shown that says “Your chat room access may be limited due to an outage” as shown in the screen shot below:
When a user attempt to enter a Persistent Chat room, they will receive this error:
From an Administrative point of view this can be easily overlooked because the bulk of the PS chat configuration is done in the Topology Builder. However, there is a group of PS Chat administrative settings in the Lync Control Panel (and also available through Lync cmdlets) that should be configured during your deployment. Specifically pay attention to the “Persistent Chat Policy” tab on the Lync Control Panel. Users must be enabled for Persistent Chat either Globally or with specific policies for each site or pool. Many deployments do not enable Persistent Chat globally, so a PS Chat policy per site which PS Chat enabled is required.
Another aspect that can get overlooked by Administrators is that if the Persistent Chat policy set on Lync user accounts is set to “Automatic” – the default – Lync will use the most granular PS Chat policy that applies, which will be a Pool or Site specific policy (if one exists). If this is the case and a Lync user account is moved from a site or pool with PS Chat enabled to a site or pool with no PS Chat policy defined, they will get the errors shown in the first two screen shots above.