PAGES

Migration from Lync 2010 to SKB

Migration from Lync 2010 to S4B 
  
Migrations are always inside out  
  
Make sure Pre-req are available by: 
Ensure Lync 2010 server OS windows is up to date 
Lync  2010 is patched with latest CU 
Run Lync Best practice Analyzer to confirm no issues reported. 
Take backup of Schema and current Lync Topology (i.e. .TBXML) 
  
on a S4B machine  
  
Install windows features for S4B pre-req via Powershell 
From the S4B installation media and run the setup. (this will install the c++ runtime, S4B core components, powershell Shell and deployment wizard) 
  
Now from the deployment wizard and click on Prepare AD, under which you will get: 
  
Prepare Schema (to verify open schema, from ADSIEDIT > schema partition look for MS-RTC-SIP-SchemaVersion and confirm range upper and lower values) 
  
Prepare Forest (to verify open ADUC and confirm groups starting with "CS...." is created) 
  
Prepair Domain (to verify open skype for Business PS and run Get-CsAdDomain it will give output as DOMAINSETTINGS_STATE_READY) 
  
Now from the deployment wizard click on Install Admin tools, this will give you access to 
S4B topology builder. Once the admin tools are installed exit the deployment wizard 
  
open up the S4B topology builder, download the current topology. Define the New S4B server/pool and finally publish the topology. Upon sucessful poblication it will give a to do list. i.e. to run run the setup wizard and install the S4B binaries 
  
Open up the Deployment Wizard, click on "Install or Update S4B" complete the 3 step process 
Now you have installed the S4B 
  
open up S4B control pannel > User > selct some poilt users > Action > Move selected user 
select the S4B pool > move 
  
After all the users are moved to S4B, modify the DNS enteries to point to new S4B server like 
lincdiscoverinternal, dial, meet, sip, admin, , _sipinternaltls SRV record, schedular (This is a new DNS record in S4B it helps to schedule meetings via web page) 
  
Now we will start migrating the applications and services using the S4B PS and control pannel 
  
1. Dial in conferencing Access No. migration from Lync to S4B 
  
S4B CSCP > Conferencing > Dialin Access Number you will see it is with Lync 2010 server 
Now goto S4B PS  Get-CsDialinConferenceingAccessNumber 
  
now lets move it to S4B 
  
Move-CsApplicationEndPoint -Identity sip:conferencingline1@uc.com -Target s4bpool.uc.com 
  
2. Response Group from Lync to S4B 
Move-CsRsgConfiguration -Source Lync2010.uc.com -Destination S4Bpool.uc.com 
NOTE- S4B CSCP > Response Group > WORKFLOW, QUEUE, GROUP you will see additional entries DO NOT DELETE THEM. 
  
3. Trusted Application. The trusted applications might not get migrated so you will have to manually create them on S4B and remove them from Lync 
  
4. Call Park Services.  
  
S4B CSCP > Voice Features > Call Park you will notice the orbit and it belongs to 2010 pool.  Here we need to consider 3 things: 
  
I - Music on Hold, the music file will be in the Lync share i.e ApplicationServer > AppServerFiles > CPS copy the music file and paste it in the same location in the S4B share 
  
II - Call Park Service, Get-CsCpsConfiguration everything you see in the output mimic the same in Set-CsCpsConfiguration 
  
III - S4B CSCP > Voice Features > Call Park > drop down destination server and select S4B Pool 
  
  
5.Number Normalization, If you are leveraging the "companyPhoneNumberNormalizationRule" it will be under Lync Share > WebServices > ABSFiles 
  
if you are using it then from PS Import-ScCompanyPhoneNormalizationRules -FileName 
  
6. Common Area Phones, Get-CsCommonAreaPhone if there are any migarte them to S4B pool 
Get-CsCommonAreaPhone | Move-CSCommonAreaPhone -Target S4BPool.uc.com 
  
7. If you have any Analog Devices in the lync 2010 pool, migrate them as well 
Get-CsAnalogDevice 
Get-CsAnalogDevice | Move-CsAnalogDevice -Target S4Bpool.uc.com 
  
8. Move the CMS, first crate a place holder for CMS in SQL DB of S4B  
Install-CsDatabase -CentralManagementDatabase -SqlServerFQDN S4Bpool.uc.com -SqlInstanceName RTC (is Standrad edition of S4B elase the Instance name of the SQL) 
  
Enable-CsTopology 
Move-CsManagementServer 
Ensure that CMS has moved to the S4B, involke replication and make sure it is working fine. 
Now goto Lync 2010 server open the shell and unisntall the CMS 
  
UnInstall-CsDatabase -CentralManagementDatabase -SqlServerFQDN Lync2010pool.uc.com -SqlInstanceName RTC (is Standrad edition of lync2010 elase the Instance name of the SQL) 
Enable-CsTopology 
  
9. Conferencing Directory, migrate them as well, S4B PS 
Get-CsConferenceDirectory 
Move-CsConferenceDirectory -Identity "1" 
  
10. Move the Trunks, open topology builder and Rt. Click on the trunk > Properties >Associated Mediation Server > change to S4B 
  
If you are using EV and have desk phones which are using the DHCP options from the Lync 2010 server then move them to S4B 
  
If you are using EV and Exchange UM then the subscriber access and Auto Attendent needs to be migrated to S4B 
  
11. Delete the Lync 2010 FE from the topology builder, it will remove the associated FileShare, Delete the SQL Instance associated with Lync 2010 and publish the topology, upon publishing the topology it will provide to do list 
  
12. Run Step 2 

No comments:

Post a Comment