After much searching you will find there isn’t much in the way of guidance provided on TechNet when migrating from Lync 2013 to Skype for Business Server as there is when migrating from Lync 2010 to Lync 2013. I was working on a Lync 2013 to Skype for Business Migration and wanted to make sure we didn’t forget anything when moving from a Lync 2013 Pool to a Skype for Business Pool. The following should help. Essentially the process is the same so refer to https://technet.microsoft.com/en-us/library/jj205369%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396 for more details.
Pre-requisites
This process assumes that your new pool is built and tested with pilot users. You have validated that all aspects and functionality are working as they should be including Edge server functionality. You have also cutover the required DNS records to support primary user sign on to this new pool as well as Public DNS records that support Skype for Business. It is best to dump all your DNS and SRV records and ensure you have not missed anything here. Again, the article above will provide guidance if you need it.
Don’t forget any topology changes with respect to your Edge servers communicating with your next hop front end servers. You likely need to make changes here. Lastly if you have deployed phones, you may have to make DHCP changes with respect to your certificate publishing. Guidance provided here.
Once you have addressed these prerequisites you can move on.
Response Groups
Step 1: Make a Copy
Export-CsRgsConfiguration -Source "service:ApplicationServer:LyncPool01.contoso.com" -FileName "D:\software\RGSExportCopy1.zip"
Step 2: Make a copy and then delete the source
Export-CsRgsConfiguration -Source "service:ApplicationServer:LyncPool01.contoso.com" -FileName "D:\software\RGSExportCopy2.zip" -RemoveExportedConfiguration
Step 3: Recreate the whole thing on new pool
Import-CsRgsConfiguration -Destination "service:ApplicationServer:SkypePool01.contoso.com" -FileName "D:\software\RGSExportCopy2.zip" -OverwriteOwner -ReplaceExistingRgsSettings
Common Area Phones
Get-CsCommonAreaPhone -Filter {RegistrarPool -eq "LyncPool01.contoso.com"} | Move-CsCommonAreaPhone -Target SkypePool01.contoso.com
Exchange Unified Messaging Contacts
Get-CsExUmContact -Filter {RegistrarPool -eq "LyncPool01.contoso.com"} | Move-CsExUmContact -Target SkypePool01.contoso.com
Dial in Conferencing PSTN Numbers
Get-CsDialInConferencingAccessNumber | where {$_.Pool -eq "LyncPool01.contoso.com"} | Move-CsApplicationEndpoint -TargetApplicationPool SkypePool01.contoso.com
Users
Get-CsUser -Filter {RegistrarPool -eq "LyncPool01.contoso.com"} | Move-CsUser -Target SkypePool01.contoso.com
After you move users make sure they are not assigned to any Site Level Voice Policies in the old pool. If both your pools are in the same site you don’t have to worry about this. If you are moving between sites then you should create all the required voice policies on the new pool and then change this for any users using them. As an example, the following changes
get-CsUser -Filter {VoicePolicy -eq "Site1:InternationalCalling"} | Grant-CsVoicePolicy -PolicyName "Site2:InternationalCalling"
Conference Directories
Get-CsConferenceDirectory | Where-Object {$_.ServiceID -match "LyncPool01.contoso.com"} | Move-CsConferenceDirectory -TargetPool "SkypePool01.contoso.com"
Lync Meeting Room Systems
Assuming all your Lync Room Systems are on the old pool you can run the following to move them to the new pool
Get-CsMeetingRoom | Move-CsMeetingRoom -Target SkypePool01.contoso.com
Comments