How to change sip domain?

Hi Team,

Currently we are running Lync 2010 with (sip.abc.com) and the company name is (abc.com). Recently, we changed our company name to (xyz.com). Please find the below details:

Environment:

AD domain : abc.com

Lync 2010 Front end server FQDN : sip.abc.com

Lync 2010 Edge Internal FQDN : Internaledge.abc.com

Lync 2010 Ede External FQDN : Accessedge.abc.com

Requirement:

Planning to change the company domain name to (xyz.com) to reflect the below:

AD domain : xyz.com

Lync 2010 Front end server FQDN : sip.xyz.com

Lync 2010 Edge Internal FQDN : Internaledge.xyz.com

Lync 2010 Edge External FQDN : Accessedge.xyz.com

Questions:

1.Do we need to decommission the old Lync 2010 server with FQDN (sip.abc.com)?

2. And then do we need to build a new Lync 2010 server with the FQDN (sip.xyz.com) ?

3. Is there anything to backup for restoration?

4. Is there any other way to complete this requirement?

Many thanks.

May 26th, 2015 10:02am

Hi,

You can represent the organization name in Lync SIP URI without re-structuring active directory.

  • Need add new SIP domain to the Lync topology
  • Assign new name SIP URI to the user account (I believe Email address also follow the SIP URI)
  • Add new DNS records
  • Update the certificates with  new SIP domain Names

If you planning to build new AD, you have to re-build Lync infrastructure as well.

You may need to consider back up up following information;

  • Lync Compliance information such as Archive messages
  • Users Buddy list
  • Scheduled Conferences (Anyway users has to recreate those meetings again)

Regards,

Malinda

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 10:36am

No need to decommission or rebuild anything, I would just add the new domain to AD and Lync and leave the servers alone. Then you just need to worry about the users.

This is an article which I often reference in regards to the SIP domain part - http://blog.insidelync.com/2013/06/anatomy-of-a-sip-domain-change/

May 26th, 2015 7:38pm

Hi SBHV,

 

Agree with Andrew, Lync Server 2010 supports Single forest with multiple trees topology, you just need to add the new domain in existing forest.


 

 

Here are some suggestions for your reference.

1. Add the new domain (xyz.com) into existing forest.

2. Move AD users to the new domain.

3. Add additional sip domain and deploy new FE servers in the new domain, also other Lync server roles.

4. Move Lync users to the new pool (server).

5. (Option) Decommission the old Lync servers.

 

Best regards,

Eric

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 10:21pm

Hi All,

Thank you very much for your inputs.

In my case, my old AD (abc.com) has been decommissioned. So, we are planning for the below steps. Please confirm if these are correct:

  1. Add (xyz.com) as Additional Supported SIP Domain. Publish topology.

  1. Run the below command to set (xyz.com) as default sipdomain.

Set-CsSipDomain Identity xyz.com -IsDefault $True

  1. Remove (abc.com) from Supported SIP Domain through topology builder. Publish Topology.

  1. Ensure that you have changed the simple URLS (https://dialin.xyz.com and  https://meet.xyz.com ) to reflect the new domain (xcy.com). Also requested and assigned new certificate based on new domain changes as well as configure new DNS records.

  1. Then change user accounts which all should be pointing to the new sip domain (xyz.com).

  1. Then check the sign in process and confirm the fix.

Many thanks.

May 27th, 2015 11:37am

Hi All,

Thank you very much for your inputs.

In my case, my old AD (abc.com) has been decommissioned. We now built a new AD with the domain (xyz.com).

So, we are planning for the below steps. Please confirm if these are correct:

  1. Add (xyz.com) as Additional Supported SIP Domain. Publish topology.

  1. Run the below command to set (xyz.com) as default sipdomain.

Set-CsSipDomain Identity xyz.com -IsDefault $True

  1. Remove (abc.com) from Supported SIP Domain through topology builder. Publish Topology.

  1. Ensure that you have changed the simple URLS (https://dialin.xyz.com and  https://meet.xyz.com ) to reflect the new domain (xcy.com). Also requested and assigned new certificate based on new domain changes as well as configure new DNS records.

  1. Then change user accounts which all should be pointing to the new sip domain (xyz.com).

  1. Then check the sign in process and confirm the fix.

Many thanks.

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 3:36pm

Hi Eric,

Can you confirm the above steps?

Many t

May 29th, 2015 9:56am

Hi,

is new AD domain member of old forest?

is old AD domain and Forest decommissioned?

Free Windows Admin Tool Kit Click here and download it now
May 30th, 2015 5:09am

Hi SBHV,

I assume that all of them are in the same forest, and then you can go ahead and perform these steps.

Best regards,

Eric

May 31st, 2015 8:13am


One option to consider is that if you do not have a split domain, or even if you do but DNS are managed separately (internal and external), it is a simple matter of adding xyz.com as a new SIP domain from within Lync topology builder in the existing AD abc.com name space. This preserves your the latter and Lync Server 2010 internal infrastructure. Going further, a resource AD forest topology would be another option.

Thanks / rgds,

Free Windows Admin Tool Kit Click here and download it now
June 8th, 2015 8:28am

Hi SBHV,

Im writing to follow up on this thread. Do you have any updates on this issue? Please post back at your convenience.

 

Best regards,

Eric

June 8th, 2015 9:32am

Hi All,

Many thanks for your i

Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 8:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics