Lync 2010 Migration to another domain

Hi 

I would approach this way 

 1) Stand up the Lync infrastructure in the new forest.
 2) Create "linked" accounts in the new forest.( users not residing in the target would authenticate via edge ). Later after the password cache entry is made end users wouldn't be prompted for the password ,since edge server  allows communication with federated companies.
 3) Enable all the users in the new target forest (probably do it by batch to see the behaviour) 
 4) User DBIMPEXP to export their contacts, conf dir to the new forest. Use Importcsuserdata commandlets to import on lync 2013

 5) During the final cutover date you can break the linked accounts (source account) by clearing "msRTCSIP-OriginatorSID" attribute and enabling the target account.

Very Imp Note : 

This will be a disruptive migration and this needs to be planned properly in all phases and done over the weekend.
You cannot share the same address space between  two different forests.

June 7th, 2015 4:44pm

Hi I need to plan a migration of Lync 2010 servers to another domain. What is the best migration approach?
After finish migrating the AD users using ADMT, can I unjoin the Lync server and rejoin to another domain and reconfigure the topology and certificate?
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2015 11:32am

Hi 

I would approach this way provided the users in the target forests share the same   primary email domain as the source

 1) Stand up the Lync infrastructure in the new forest.
 2) Create "linked" accounts in the new forest.( users not residing in the target would authenticate via edge ). Later after the password cache entry is made end users wouldn't be prompted for the password ,since edge server  allows communication with federated companies.
 3) Enable all the users in the new target forest (probably do it by batch to see the behaviour) 
 4) User DBIMPEXP to export/import their contacts to the new forest.
 5) During the final cutover date you can break the linked accounts (source account) by clearing "msRTCSIP-OriginatorSID" attribute and enabling the target account.

Very Imp Note : 

This will be a disruptive migration and this needs to be planned properly in all phases and done over the weekend.
You cannot share the same address space between  two different forests.

June 8th, 2015 12:42pm

Hi,

Would you please elaborate the migration information (migration from one domain to another in the same forest or in different forest)?

If it is migration from one domain to anther domain in the same forest, you can just deploy another Lync pool in the new domain, test the function of it, and then move users from old one to the new Lync pool, and finial decommission the legacy Lync pool.

It is similar like migration from Lync Server 2010 to Lync Server 2013:

https://technet.microsoft.com/en-us/library/jj205369%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

Best Regards,
Eason Huang

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

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

Other recent topics Other recent topics