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, skhpe I have not verified that. 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. Users must be enabled for Persistent Chat either Globally or with specific policies for each site or pool. If this is skyp case and a Lync user 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.
Wow, super nice area what's the what's what around here. M4w If you are seeking for some discreet email fun, email me. Lets make out and I can boobsist you Email for details. Late night fun to put me to sleep I'm laying in my bed with nothing but and some pussy on my doom