Hello,

We have an issue with the "new" lync 2013 client, where some users are having a presence status of "unknown". What we found out is that if you look at the contact card of that user, he or she has 2 IM addresses. The problem is probably that it looks at the first ( and wrong) user.name@domain.local IM address. I am not really familiar with the way Lync syncs these attributes from AD and where these attributes come from. We think we found an attribute "proxy address" for the user and it has both IM address values in there; sip:user.name@domain.com and sip:user.name@domain.local. We think that for some reason, users were incorrectly created and this is some leftover from that. We can also see it in the properties of the user in Exchange.

What my question actually includes is how we can correct this and where to do that best. Should we update it in Exchange, on Lync (powershell or gui doesn't matter) or in Active Directory. Iam really unsure on how the relationship between these 3 is and how and which attirbutes are updated from where.

By the way, we are running a single server Lync 2010 environment. (single in one front-end, one mon/arch and one edge). We only see the issue on Lync 2013 clients.

• Edited by Niels Wes Friday, July 31, 2015 11:54 AM

Did you only find it in the proxyaddresses attribute?  If so, I'd probably work to kill it via AD directly as that's not a Lync attribute.  Whichever method you prefer would likely be fine.  How wide spread is it, do you need a script?  Is the .local domain a valid SIP domain still or for some users?

Hi Niels Wes,

 

You may try deleting the duplicate entry of sip address (.local) in ProxyAddress attribute to see if it works. In general, user only can be assigned with one sip address.

If the issue still persists, you may try recreating the user account.  (You can use Dbimpexp.exe to export and restore data for user.)

Here's a similar thread for your reference.

https://community.office365.com/en-us/f/166/t/215668

Best regards,

Eric

@Athony: Yes we did only find it in the proxyaddress attribute. The issue is that I do not know if there are any other attributes that could have this value. Maybe these attributes are derrived from another attribute? I would not think so, but iam unsure. Especially because I do not understand the fact that the msRTCSIP-PrimaryUserAddress has value "sip:user.name@domain.com", but also the values in the proxyaddress attribute are "sip:user.name@domain.com" and "sip:user.name@domain.local". So what is the relationship and am I looking at the right attribute when for the IM address in the Lync gui. I have removed the faulty address from the proxyaddresss attribute, but no result. The address is the same, also after reloading the local Lync profile. Do we possibly need to do an address book resync on the server or is this just the wrong attribute?

A lot of people have this issue. I was looking for a script to find these users but no luck so far and my scripting knowledge is not so good.

The .local should not be used as a sip domain, only the .com