Check out the most comprehensive, actively managed Lync blog roll in the known universe, your one-stop source for links to over 100 of the very best Lync blogs. Here you will also find weekly blog highlights and a feed for a dozen of the top blogs.
Lync Server Support Home
Top Lync Solutions RSS Feed
Microsoft Senior Support engineers walk you through real-life support cases, giving you an insider’s view into the systematic approach they use to troubleshoot Lync Server issues.
The DrRez and Lync PowerShell blogs are now retired, and we migrated their awesome content to NextHop. No worries, all your favorite articles from these two ground-breaking blogs are now available here. And DrRez on FaceBook and Twitter will continue his stellar work as the Voice for NextHop on those social media channels. Thanks for your support!
When running Office Communications Server Setup to create an Enterprise pool, the Create Enterprise Pool Wizard requires a SQL Server instance as shown in Figure 1. This is a database instance that the Enterprise pool uses as its back-end server. After the SQL Server instance field, the wizard provides an example that can be confusing. The reason is that unless you plan to reuse an existing instance, most installations are new installations. The language in the wizard might make you think that you need to specify a database instance name that is to be created or that you have to create the instance yourself.
If you find yourself frequently using Remote PowerShell to start up Communications Server Management Shell, you might have thought about how nice it would be to have a handy desktop shortcut to do this. If you have thought that - or even if you haven't, but now that we mention it it sounds like a pretty useful thing - take a look at this script.