Lync 2013. Domain name change sip addresses

  • Tutorial

There was a task of changing the domain name in the sip address of Lync users.
The infrastructure has Lync 2013, Exchange 2013. There is also a federation with another organization.

1) You need to add a new sip domain to additional supported sip domains.
This is done through the Lync Topology Builder.
Open, click Download Topology, save the file with the tbxml extension.
Then we go into the properties of Lync Server and add a new sip domain.


After that you need to publish the topology. In the main window of Topology Builder Action -> Publish Topology.

You can check through the Lync management console - the user should see a drop-down list of sip domains.

2) Add records to the DNS.

For Internal DNS

Type SRV (port 5061)
Type A

For external DNS

SRV type (port 44) (port 5061)
Type A meet. .com

3) We create a new certificate with a new domain.
Go to the Deployment Wizard -> Install or Update Lync Server System -> Request Install or Assign Certificates.
Create a new certificate request. And set it as the default certificate.

DNS Name = Pool.newdomain.corp
DNS Name = LyncWebSvc.newdomain.corp
DNS Name =
DNS Name = LyncServer01.newdomain.corp
DNS Name = meetings.newdomain.corp
DNS Name =
DNS Name =
DNS Name =
DNS Name =

DNS Name = Pool.OldDomain.corp
DNS Name = LyncWebSvc.OldDomain.corp
DNS Name =
DNS Name = LyncServer01 .OldDomain.corp
DNS Name = meetings.OldDomain.corp
DNS Name =
DNS Name =
DNS Name =
DNS Name =

Run Enable-CSComputer

4) Federation
In the Lync management console of the federated organization you need to add our new domain .
This is done through the Lync -> Federation and External Access -> SIP Federated domains management console.

5) Reverse Proxy - you need to make changes and rewrite the certificates (if necessary)

6) Change the sip domain for all Lync users.
We use the script:

$UserList = Get-CsUser 
foreach ($User in $UserList)
   $oldAddress = $User.SipAddress
   $newAddress = $oldAddress -replace "", ""
   Set-CsUser -Identity $User.Identity -SipAddress $newAddress

1) If after a user with a new domain logs in to Lync and a window pops up stating that Lync cannot verify trust.


It is necessary in the registry, along the path [HKEY_CURRENT_USER \ Software \ Microsoft \ Communicator]
In the parameter "TrustModelData" add the address indicated in the message.

It is also necessary to verify that the required domains are specified in IE, on the Local intranet.

2) If the history is not saved in Outlook, you need to check that for the new domain there is an autodiscover entry in DNS that points to Exchange

Also popular now: