Pages

Wednesday, April 10, 2013

Recently I was bulk enabling users for Exchange Unified Messaging for users on 2010. For just a few of the users, I received the following error message when trying to enable them for UM:

Error: Unable to save Unified Messaging PIN for mailbox xxxx: The administrative limit for this request was exceeded.

After using my favorite search engine, I came up empty on this exact error message. I did get a few hits on the generic “The administrative limit for this request was exceeded” message.

After a little research, signs were pointing me to the AD user account had a “runaway” attribute with too many entries in it causing other applications to fail when making changes to other attributes. I reviewed one of the problem user’s attributes and found the userCertificate filled with a bunch of entries.

After clearing out the userCertificate attribute the mailbox was able to be UM enabled.

Monday, January 28, 2013

With a background in Exchange Server, you always had to be careful about installing new versions or decommissioning the last server of an older version within an environment. So I was wondering if it was possible to install/introduce a Lync Server 2010 Front-End server into a completely native Lync Server 2013 environment (an environment that has never had Lync Server 2010 in it). Also, if it is possible, what is the experience and is it actually functional.

Short Answer: YES it is possible

My Environment:

Domain Controller – Windows Server 2012

Lync Server 2013 SE – Windows Server 2012

Exchange Server 2013 – Windows Server 2012

Office Web Apps 2013 – Windows Server 2012

Current Topology:

Adding a Lync Server 2010 SE server in the Topology Builder and published:

I have prepped a server for the Lync Server 2010 SE and installed all pre-req’s. Starting the Deployment Wizard for the Lync Server 2010 shows that Active Directory is already fully prepared!

I won’t bore you with the Lync Server 2010 install, but you can see that the Lync Control Panel now shows both 2010 and 2013 in the environment:

Now it is time to rehome some users to the Lync Server 2010 pool and test things out:

Looks like everything is working:

This post explored whether Lync Server 2010 could be introduced into a native Lync Server 2013 environment. The installation went smooth and seems like all functionality works as expected.

Saturday, December 1, 2012

I suppose there are a few reasons that you might want to disable IM functionality for certain users in Lync. This can be easily accomplished by modifying the registry (which can be controlled with a GPO).

Before we get started, let’s look at what typical options would look like for a Lync 2013:

As you can see, the IM button is present and active for my contacts. The location in the registry to implement policies for Lync 2013 are in a different location compared to earlier versions. Now you can locate or create policies in the HKLM (or HKCU)\Software\Policies\Microsoft\Office\15.0\Lync

You can disable IM by running the following command from an elevated command prompt:

Search This Blog

About Me

I am a Lync Architect for Avanade specializing in Microsoft Unified Communications. I am also a Microsoft MVP in Lync.
The views expressed on this site are my own and do not reflect views of Avanade, Microsoft, and any other vendor that I mention.