A chat room has been disabled. Perhaps a user did it through the GUI
Or perhaps you did it via PowerShell
Set-CsPersistentChatRoom -Identity “pchat.domain.com\chatroom” -Disabled $True
Now you want it back. When you run Get-CsPersistentChatRoom, you don’t see it. You didn’t remove it, you just set it to disable. Where is it?
Unless you’re one of the fortunate ones, we’ve all had our heart stop with this once as administrators. Fortunately, you’re just missing a single, but very important parameter. Try this to see your disabled chat rooms:
Get-CsPersistentChatRoom -Disabled $true
I ran into an interesting issue the other day, I have a client with Dell AIO (all-in-one) desktops. Each one has a dual monitor configuration and they’re running Lync 2013. In Lync 2013->Tools->Video Device Settings you can see the webcam video fine. However when you attempt to share your video it gets stuck on “Loading” forever and never displays the video. If you just start the video, it just shows a blank or grey box. I tried several things, swapping video drivers, updating the webcam driver, disabling other webcam related management applications, but nothing helped. I noticed that not only were there two monitors, there were two video cards, an Intel HD and an AMD Radeon. When I would disable one in device manager video would work but the second monitor was disabled. The same effect occurred when I disabled the other video card and re-enabled the first. In the end, the quick fix turned out to be the disabling of hardware acceleration in Microsoft Office. This is easiest found in Microsoft Word options.
This can also be disabled via Outlook or via the following registry key:
DWORD: DisableHardwareAcceleration = 1
For more information, check out the following support article: http://support.microsoft.com/kb/2761977
So you’ve set up mirroring for your Lync front ends, and you know you need that witness for automatic failover. You’ve decided to use SQL Express so you don’t need another full license for this, but when you try to specify it as the witness, you get the following error:
Error: An error occurred: “Microsoft.SqlServer.Management.Common.ConnectionFailureException” “Failed to connect to server sqlwitness.domain.com\lyncwitness.”
It’s not a firewall or port issue, it’s not a permissions issue, it’s just not working. Here’s the trick: by default the SQL Browser Service is disabled with a SQL Express install. Set this service to automatic and start it up. You may need to remove the witness from your topology, publish, add it back in and republish, but you should be fine after this.