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.
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!
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.
Enabling a user for Lync and enterprise voice is easy, if you know how the Enable-CsUser cmdlet works.
You can always enable a user for Lync and enterprise voice in one go from the Lync control panel. You can assign all the policies as well from the GUI.
If you want to enable a user for Lync from the shell, the cmdlet we need to use is Enable-CsUser. In order to find user(s), the cmdlet is Get-CsUser.
The Get-CsUser cmdlet gives us most of the info regarding a user – like the SIP address, pool fqdn, whether the user is enabled for enterprise voice, various policies etc.
Hence, you would think that you can use the Enable-CsUser to enable a user for Lync and enterprise voice using the same cmdlet. Wrong! You need to use the Enable-CsUser and Set-Csuser. The reason for this is that the Enable-CsUser cmdlet doesn’t pass objects through the pipeline by default. You need to use the –PassThru paramter and pipe the output to the Set-CsUser cmdlet.
For example, to enable a user for Lync and EV, the command is as follows.
Enable-CsUser “user” –RegistrarPool “pool fqdn” –SIPAddressType EmailAddress –PassThru | Set-CsUser –EnterpriseVoiceEnabled $true
The Enable-CsUser does not have a EnterpriseVoiceEnabled parameter which you can set to $true. You can always break the commands into two and avoid using the –PassThru parameter as well.
This piece of info will come in handy if you are scripting the Lync administration – maybe in a migration or new Lync deployment.
I came across a deployment in which the work number was the default option while selecting the “Call” option in the Lync client.
How to change it so that the default is always a Lync call? Pretty straightforward – All that is needed is a change to the client policy. Run the command below in the Lync Shell.
Set-CsClientPolicy “Policy Name” –EnableVOIPCallDefault $true
Once the change is made, the default option is always the Lync call.
If you have custom client policies defined, say a site level or user level one, make sure that the change is made on the policy that gets applied to the end user.
What are the different ways to join a Lync online meeting with Chrome set as the default browser?
You want the Lync 2010 thick client to be “the client” for everything including joining online meetings. But when Chrome is set as the default browser, it comes up with a webpage asking us to join the meeting using the browser or to download the Lync Attendee. If IE is your default browser, there is no issue.
One workaround is to use the IE Tab extension from the chrome web store.
Once the extension is active, you can join the meeting as you would when you have IE as the default browser. You can of course copy and paste the meeting url into an IE browser and join the meeting that way.
Any other workaround guys?
Microsoft has released cumulative update (CU) 7 for Lync Server 2010
Knowledge Base article 2493736 goes through the updates released for Lync server 2010.
Download the CU 7 from here
One of my previous article explains how to install cumulative updates on Lync server 2010.
The title might confuse you, as many of you might have heard that everything is setup correctly in Office 365. I found that the external communications was disabled for my tenant for some reason.
While checking out the settings for Lync Online, I found the status for external communications to be Enabled, but the status was listed as disabled for all my domains, including the onmicrosoft.com one.
In order to fix it, I had to disable the external communications using the Disable button. That changed all my domain status to Connection Pending.
It took more than a day for me to get all my domains enabled for external communications.
Next time you play with Office 365, check all the settings. Don’t just assume that everything is setup correctly & will work out of the box . I learned this the hard way while setting up my on-premise Lync to federate with Lync Online, covered here. I was troubleshooting the on-premise deployment, while the problem was clearly with the Office 365 setting!
One of the selling features of Lync 2010 is the ability to communicate with users outside your organization – be it a remote user, federated or PIC. How can we communicate with a company who has Office 365 subscription?
Lync 2010 doesn’t allow communication with Lync Online (Office 365) out of the box. You need to add a provider for Lync Online for the communication to work. Let me explain.
I have an Office 365 subscription with a Lync user Rajith@uclab.me. My on-premise Lync has an account Chakka@exchangemaster.me. I want my on-premise Lync deployment to communicate with Office 365. How can I do it?
Launch Lync Control Panel and navigate to External User Access –> Provider. There are only three provders by default.
We need to create a new provider for Lync Online. Hit the New button and create a new Hosted Provider. Give LyncOnline as the name of the provider and sipfed.online.lync.com as the access edge fqdn. Select Allow all communications with this provider, unless you want something granular. Hit the Commit button.
Make sure that the new provider is enabled.
That’s it. If you are into PowerShell, open up Lync Shell and run the following command to achieve the same result.
New-CSHostingProvider –identity LyncOnline –ProxyFqdn sipfed.online.lync.com –Enabled $True
You should now be able to add the Office 365 user in your on-premise Lync client and the presence will be updated immediately & you can chat straightaway (provided that you have enabled external communications, covered here).
Sure enough, the Office 365 side (OWA and Lync client) picks up the on-premise presence as well.