On a recent window-shopping expedition through the event logs on a customer’s Front-End I stumbled across instances of warnings 31137 & 31138. These are generated when Lync realises that users belonging to RGS Agent Groups are no longer EV-enabled, or no longer exist. During the Active Directory update non-UC enabled agents were found. The following …
I encountered an interesting fault this week: calls were being presented to Lync Response Group Agents, but they couldn’t answer them. Callers would be listening to hold, cursing the delays in the queue while the agents were desperately trying to answer the calls. At the same time it also transpired that one of their two …
Just in case you missed this week’s kb, Lync Server 2010 can now be installed into an Active Directory where the forest and domain are at the Server 2012 functional level. This brings Lync Server 2010 into alignment with Lync Server 2013 plus Exchange 2010 & 2013, all of which are OK on functional levels …
It’s a relatively light update for Lync Server 2010 this quarter, but there are still some interesting fixes in there. This update takes the server up one increment, from 4.0.7577.216 to 217. (The current client update is last week’s hotfix release, taking it to 4.0.7577.4392. That’s HERE).
ACMA has today mailed the industry to point out that last year they issued numbers in the “02 79xx xxxx” range to several carriers, and that lucky customers with the new prefixes are complaining they can’t be called. Clearly there are plenty of PABXs (and perhaps the odd Lync or OCS installation) that don’t cater …
Microsoft has published an Important security bulletin (MS13-041) detailing a “Vulnerability in Lync [That] Could Allow Remote Code Execution (2834695)”. The bulletin is HERE. Products impacted Communicator 2007 R2 (3.5.6907.268) Lync 2010 (4.0.7577.4388) x86 x64 Lync 2010 Attendee (4.0.7577.4388) User installer Admin installer Lync Server 2013 I’ve also placed the download links on the respective …
Continue reading ‘Lync Remote Code Execution Vulnerability – May 2013’ »
I’ve lamented before that we suffer from time to time in our efforts to localise American-designed products for the Rest Of the World. When things do misbehave, a common diagnostic step – and frequent cure – is to reset language settings back to their “native” US English. Our latest gotcha has come from Lync’s Location …
Continue reading ‘Lync Attendant – “Your Location Is Not Set”’ »
March 14th, 2013: Lync 2010 CU8 has landed. It takes the server to .216 and the client to .4378. Of interest to me in this update: Server Side 2796755 Registrar service crashes on a Lync Server 2010 server when the SBA or SBS are deployed in branch sites 2796747 Intercluster routing component does not route …
Those of us with a telephony background have been rejoicing of late with the release of several Call Pickup solutions for Lync. Long conspicuous by its absence from the OCS and Lync feature list, it’s been at the top of the Cisco competitive playbook for those aiming to shoot down a Lync Enterprise Voice opportunity. …
Here’s an ad-hoc post with a collection of snippets of PowerShell I often seem to find myself needing to refer to. There are some more good ones here from Paul Bloem, over the pond. How do I find (and/or count) the users homed to a given FE/pool? Get-CsUser | Where-Object {$_.RegistrarPool -match “<POOL FQDN>”} | …