Current Environment:- Lync 2010 Enterprise

Migrated From OCS 2007 R2.

Lync Configuration still stored in System container. During migration it did not migrate on Configuration partition.

Issue Details:- Followed Microsoft deployment guide and lot of articles.

First of all it is not mentioned anywhere the following command is pool specific command.Everywhere it is mentioned we have to use MS Lync FE server after -identity.

Anyway when i am running following command from any of the Lync FE server Lync management shell.

It creates Two Guids under  Domain naming context-->System-->Microsoft-->RTC Service---->Trusted Services.

Guid's contains Lync FE server name MCXInternal 5086 and Mcxecternal 5086 for each node.If i ran the following command two times it creates total four Guids.It means Two duplicate records but with Unique Guid.If i ran this command third time it create total 6 Guids for each node.

Set-CsWebServer -Identity Pool.domain.com -McxSipPrimaryListeningPort 5086
Set-CsWebServer -Identity Pool.domain.com -McxSipExternalListeningPort 5087

Is there anyone who can help me to answer my question why this is happening.

If i am doing the samething in my Test Lab where all my Lync configuration stored in AD configuration partition it did not create duplicate GUID's.Only Two Guids created one for MCXinternal and one for MCXexternal.

This is Only Gap i saw in the enviornment.

Please help me to find the answer of this quesiton i will really appreciate yoru help.

Sandeep Deswal Tech Lead Wipro.

Do you have multiple DCs in your environment ?

From my point of view, this may be caused by AD replication. The second running of the command-let connected to a domain controller which had not received replication yet, resulting in the creation of the second extraneous object. You may remove the newer duplicate objects and waiting for AD replication to complete, then run Enable-CsTopology command to see if it is able to run successfully.

Best regards,

Eric

Hi Eric,

Thanks for your reply.

I checked with Directory team who is managing the DC's in my environment and i found there is no replication issue.

Second things after deleting the duplicate records it will allow to publish the topology.

We have total 4 DC's for that site.

I have a confusion when i do the same thing in my QA environment no problem even i ran that command multiple times in gaps of second.

But in prod environment i ran that command two times and it created duplicate entries.

Anyway is there a way to find out or track when i am running that command to which dC's it is going to make connection.

Thanks for your reply Eric.

Hi Sandeep Deswal Tech Lead,

Since this command cannot be specified with the DomainController parameter, You may capture the traffic by using netmon or Wireshark to see which DC is the Server exchanges information with.

Best regards,

Eric