I was recently testing a Lync deployment prior to cutover, and as part of that process I needed to fail the SBA and the Front-End to ensure the users were all correctly re-directed to a SIP Registrar and that the “Limited Functionality … Outage” message displayed.
That all worked fine, but I was surprised to find that after reinstating the servers, my test user wasn’t able to join a Lync Meeting:
Continue reading ‘Lync: “The provided credentials are not authorized by the server”’ »
Here’s a cute bug in Lync – evident in CU2.
When you create a new Dial Plan, the Lync Control Panel creates a “simple name” from your original name. This Simple Name has invalid characters like spaces removed and replaced with underscores.
Continue reading ‘A bad Lync Dial Plan name will break Call Park’ »
I’ve noticed a few of my Lync installations are intermittently having problems generating an Address Book, reporting Event ID 21022 on the Front-End.
Continue reading ‘Lync 2010 ABS Error 21022–“A full data file is corrupt”’ »
UPDATED 13th MAY 2012 – have a look at the update to C-ChangePHP in this post.
It’s been a long time coming, but today I’m posting the first release of “C-ChangePHP”.
As per my earlier post, this code lets you control your C-Bus installation from any browser, anywhere.
Continue reading ‘DOWNLOAD C-ChangePHP – a home-brew, customisable, browser interface for C-Bus’ »
I seem to spend an inordinate amount of time chasing bugs that *always* turn out to be certificate-related.
It’s been a while coming, but it’s here now (as of today – May 11th, 2011):
Continue reading ‘Now receive your Lync Server & Client updates through WSUS!’ »
I recently decommissioned a Nortel CS1k / CS1000 PABX to which was connected an NET Tenor DX, as well as a UX2000. Before doing so, it was suggested that I might like to suck the config out for others to benefit from. Here it is.
Continue reading ‘Sample Nortel CS1k configurations for NET Gateways’ »
Exchange 2010 has gotten us used to the easy life. An inbuilt certificate request wizard and easy GUI-based management of logging levels… Bliss.
If you then find yourself needing to elevate your logging on an Exchange 2007 box you might be a little lost.
This commandlet will confirm the current logging level of the Exchange 2007 UM services:
Get-EventLogLevel “MSExchange Unified Messaging*”
… and to increase it, it’s as simple as piping it:
Get-EventLogLevel “MSExchange Unified Messaging*” | Set-EventLogLevel –level:expert
Don’t forget to change it back when you’re done:
Get-EventLogLevel “MSExchange Unified Messaging*” | Set-EventLogLevel –level:lowest
If you paste the above directly into Exchange and it fails, it’s probably the funky quotation marks. Or you don’t have the UM role installed. :-)
Back in OCS/R2, deploying updates to your clients was a manual process. It usually worked but was not without its challenges (generally permissions-based). You plonked the Update.msp on the SE server or file share (buried somewhere like C:\Program Files\Microsoft Office Communications Server 2007 R2\Web Components\AutoUpdate\Files\OC\x32\fre\1033 or similar), then went to <pool>\ Filtering Tools \ Client Version Filter\ and added an “Allow and Upgrade” entry with a link to the “OC” folder. (It figured out the “x32\fre\1033” on its own based upon your architecture and language settings – 1033 being US English).
Lync improved upon this by using WSUS to automate the update process.
Continue reading ‘Deploying Lync client updates through WSUS? Not yet…’ »
I have a couple of Polycom CX600s living in common areas. Each is logged-in permanently as a (dummy) user and not tethered to a PC. They’re effectively serving as common-area phones, but setup as real users. I’ve updated my Lync to the CU1 and CU2 updates to the phones (.107 and .250 respectively) as per my earlier post on the subject, and on each occurrence found that the phones fail to apply the updates seamlessly. My old Tanjay went to .250 without issue, but the CX600s – different story.
Continue reading ‘Polycom CX600 fails after updates – stuck / won’t login’ »