Lync/SfB: How to change Persistent Chat Privacy Web Form

Recently we were asked to disable the Open Room creation in Persistent Chat. The purpose was to only allow users to create Private or Closed Rooms from the website.


After some research we didn’t find any setting/policy that could disable or remove that option.

The only option was to try to find in the web pages if there was anything we could change. It turns out that the easiest way is to change the JavaScripts for Persistent Chat Room Management webpages. These are located in:

Internal Website- C:\Program Files\Microsoft Lync Server 2013\Web Components\PersistentChat\Int\RM\JScripts

External Website – C:\Program Files\Microsoft Lync Server 2013\Web Components\PersistentChat\Ext\RM\JScripts


We need to change the RoomForm.js file. In this file look for the function MainForm.prototype.cleanUpRoomPage:


The radio button is radOpen, so we simply disable it. For this we need to add the following line:

this.radOpen.disabled = true;


Note: You need to change it in all relevant servers and also in both Internal and External Websites.

Since we changed the JavaScript, there’s no need to recycle the application pool or execute iisreset.

Now reload the page and the Open radio button should be grayed out:


Note: This will also change the form for the creation and editing of a Room.

Persistent Chat: Your chat room access may be limited due to an outage.

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.