We have a 2013 on premises server running Lync. We have noticed when provisoning users that the proxyaddress SMTP attribute is showing as being wiped out

Hi,

Based on my research, the attribute proxy address is set by the system Created by a DLL provided with the Address-Type directory object when the address type is installed:

http://msdn.microsoft.com/en-us/library/ms679424(v=vs.85).aspx

and we can try the following troubleshooting:

1. Check if client can send and receive emails or check if there is something wrong with the client experience.
2. Check the result if you manually change the value.

Additionally, since the issue is related to Lync server, I recommend you ask for more professional help on our Lync server forum:

http://social.technet.microsoft.com/Forums/lync/en-US/home?category=ocs 

If you have any question about Exchange server, please feel free to let me know.

thanks,

we have come across a similar thing. Where the case of 'proxyaddress' attributes are being changed to lowercase i.e SMTP: becomes smtp: same with the SIP: to sip:  in  the AD.

Or, is completely removes  the smtp addresses except for the sip: which is still changed to lowercase. 

Thusly, after a DirSync the Primary SMTP in Office 365 defaults to the onmicrosoft.com address.

Since the Lync onpremise is being managed elsewhere it was tough convincing .

After running some Repadmin at the time of the change before it got  corrected I  could see that it was the Service Account used for the Lync on premise  scripts that was making the changes to the 'proxyaddress'.

Contacted MS but the want us to expand the security logging to point out the change.

Been dealing with this for a few months.

Anyone else come across this?

• Edited by BrianTGrant Tuesday, June 17, 2014 2:12 PM

Hey,

I've been dealing with this issue for the last few weeks. We have an automated script that creates our active directory users, and then creates a mailbox, then a lync account. I've run into the same issue as above. This is actually not a bug, it is by design believe it or not.

When you create an object in active directory it needs to replicate changes to other domain controllers in the forest. I'm sure we can all agree on that yes? What we found was happening in our case was the user was created, we would loop until the account was found in AD, we would then create the mailbox for said user on premise. 30 seconds later we would create the Lync account for said user.

Here's where it goes black box on us. in the background when you create a mailbox the proxy address attribute on the user account gets set with the smtp addresses for the user, this change needs to replicate on your DCs. 30 seconds after creating our mailboxes we create the lync account which also updates the proxy address attribute, which again needs to replicate. Unfortunately if the first change has not sync'd the second change will overwrite the first actions changes, hence seeing only the sip address.

The only way we've found that works for us for 99% of the time is to increase the amount of time between mailbox creation and lync account creation to allow for replication to happen. Thoughts on how to get around this would be using an extension attribute that you set up as a flag, have another script come along every two hours and provision the lync accounts for the users with that flag.

Cheers,