Evolution - Lynctastic will merge into new Blog

I was originally concentrating in Enterprise Voice, and so I created Lynctastic... but as the reality of my new position settles in, I am working in the entire Unified Communications Area. So, I have abandoned this blog, and will be launching "Unified Communications Station" on October 24, 2011. Please look there.

Lync Error ID 3110 (source ID 243)

In our implementation of Lync, we had users that would consistantly get an error 3110 when trying to join recurring meetings. troubleshooting revealed that the servers were originally deployed in default mode with Enterprise Voice enabled. We soon discovered that our network couldn't handle so much simultaneous real-time traffic, so we disabled enterprise voice for all but a small, select group of users. While we were troubleshooting, I found a workaround:

So, the workaround allowed users to enter the meetings, but it was not solving the issue. I spent a good deal of time troubleshooting this and I believe the root cause is the fact that we disabled EV for the vast majority of users. The meeting URI created when the users were initially created meant the meeting had audio rights, and since the user's didn't anymore, the join for the user was trying to open an audio session. Since the users didn't have audio conference rights, the join fails for audio, but you can see by the picture above, you are in the lobby. To join the meeting, all you have to do is click on IM and type something in. The true fix would be to either have the users cancel all preexisting recurring meetings, or set the meeting configs to force a new URI to be generated for each and every meeting as shown below:

That should make your 3110 errors a distant memory.

Script to Gauge Size of Exchange 2010 Log Files

I know this is supposed to be a Lync blog, but since Lync depends on Exchange, I thought this might be pertinent. We had an issue at our company where the backups for Exchange weren't working properly and the log files weren't truncating as designed. We just had no convenient means of visability into the status of the the log files or their back ups. as a quick, down and dirty way to get a status on where the log files were, I whipped up the below powershell script. The script just pulls the size of the log file directories, the idea being that if any grows above the baseline size (in our case that was 10 GB), it should be apparent to us that there's an issue with log truncation. It uses Sysinternal's Disk Updater, du.exe to pull the stats from the volumes. it also sends an email to the appropriate DG for action, and just for some sort of audit trail, it writes the stats to the application event log. See the text below for the script. Use it at your own risk. 
################################################################################
# Get-LogLength.ps1 [Version 1.0] - for server ServerNameHere
#
# This script will get the size of the mailbox database log directories for a
# down and dirty look at whether or not the log files are truncating as designed
# This script requires sysinternal's DU.EXE to be in the local directory
#
# Usage: Get-LogLength.ps1
# Author: Sean McNamara
# Date: July 26, 2011
################################################################################
$strBody = "Log Size for " + $env:computername + ":" + [Environment]::NewLine
$path = "DB1PathHere"
$result = & .\du -q $path
$strBody = $strBody + "DB1 " + "--  " + $result + [Environment]::NewLine
#
$path = "DB2PathHere"
$result = & .\du -q $path
$strBody = $strBody + "DB2 " + "--  " + $result + [Environment]::NewLine
#
$path = "DB3PathHere"
$result = & .\du -q $path
$strBody = $strBody + "DB3 " + "--  " + $result + [Environment]::NewLine
#
# add as many db lines as needed.
# This section will email the results to $To
$SmtpClient = new-object system.net.mail.smtpClient
$SmtpServer = "smtprelay.yourcompany.com"
$SmtpClient.host = $SmtpServer
$From = "Youremail.address@yourcompany.com"
$To = "Youremail.address@yourcompany.com"
$Title = "Log File Report - " +  $env:computername
$SmtpClient.Send($from,$to,$title,$strBody) 
# This section creates an event log entry for audit purposes
write-eventlog -logname Application -source application -eventID 1111 -entrytype Information -message $strBody

View Lync Client Configuration

 You can easily view the configuration information of the Lync 2010 client by following these simple steps.

1.

Hold the Control key down while right-clicking the green Lync client icon in the notification area.

2.

This will enable the Configuration Information menu option. Click it and you will see a pop-up window that displays all the Lync 2010 configuration information for the client.