Monthly Archives: October 2013

Lync 2010 In A Resource Forest Topology

I came across a user not being able to sign in to the Lync 2010 client when Lync 2010 server was deployed in a resource forest.

The user was getting the normal error message.

Cannot sign in to Lync. You may have entered your sign-in address, user name, or password incorrectly. If your sign-in information is correct and the problem persists, please contact your system administrator.

Since the error message pointed to login credentials, I verified the following.

  • I reset the user password to be sure.
  • Account was not locked out.
  • I could sign in from the user machine, which confirms that it is not a machine issue.

The problem was that a required attribute was not set for the user. When Lync 2010 is deployed in a resource forest along with Exchange, the MSRTCSIP-OriginatorSID attribute should match the msExchMasterAccountSid. In this user’s case, the attribute was not set (blank).

Once I set the attribute using ADSIEdit, the user was able to sign in straightaway.

Where Is Lync MSI File?

A question that came via email from an AD admin was about ways to package an MSI file for Lync 2010 client installation via group policy.

It is a common practice to deploy software using group policies and Lync is no exception. But, when you have a look at the downloaded Lync 2010 client, it is an exe and not an msi file. So, how do we go about packaging the Lync client?

Fortunately, Microsoft does provide an MSI, but not in a straightforward fashion. install the Lync 2010 client on a machine and the MSI file is created as part of the install in C:\Program Files (x86)\OCSetup folder. There it is!

Lync2010MSIFile_thumb

Use this msi file to push the Lync 2010 client using group policy. One hurdle that you need to overcome is the fact that msi install of Lync client is not allowed by default. A registry edit takes care of this problem. Read KB2477965 for the fix.

Happy installing icon_wink