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.
These short videos focus on specific tasks and show you how to accomplish them for Microsoft Lync Server 2010.
Author: Thomas Laciano, Sasa Juratovic
Publication date: January 2008
Product version: Office Communications Server 2007 R2
September 28 2009 Update: For those looking for the most recent script for use with R2, see this post for details - http://communicationsserverteam.com/archive/2009/09/28/584.aspx When customers deploy Office Communications Server 2007 Archiving they quickly request tools or sample queries to retrieve their data. The Office Communications Server 2007 Resource Kit includes the ArchivingCDR Reporter tool. This reporting tool has built-in SQL queries to retrieve and view information from the Archiving and Call Detail Records (CDR) Backend. The tool enables the user to view Office Communications Server 2007 usage reports based on the Archiving and CDR tables.
A member of our team worked on a sample* using PowerShell technology to gather all IMs for a given user or all IMs between two users. The result is output to console and a local im.xml file. The script will support the following message types:
To use the tool, you will need to download the zip file (updated to handle special characters on April 17, 2008 (Updated and tested by our Austrian peer Thomas Binder) and extract all files to one common directory and run ps1script. Please note the tool has the following dependencies:
The first two items are mandatory; the third is nice to have as it will create an HTML page for the XML output. July 2008 update from Thomas Binder: Details: As recommended in one of the commentary postings, I replaced the line Add-Content -Path $LocalPath -Value '<?xml version="1.0" encoding="UTF-16"?>' With: Add-Content -Path $LocalPath -Value '<?xml version="1.0" encoding="ISO-8859-2"?>'