Lync 2013 to Skype for Business Server Migration Checklist

Lync 2013 - Skype for Business Server 마이그레이션 Check List

 

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. 

많은 검색을 거친 후 Lync 2013에서 Skype for Business Server로 마이그레이션 할 때 TechNet에서 제공되는 안내 방법이 Lync 2010에서 Lync 2013으로 마이그레이션 할 때와 다름을 알 수 있습니다. Lync 2013 to Skype 비즈니스 마이그레이션을 위해 Lync 2013 풀에서 Skype for Business 풀로 이동할 때 우리가 무엇을 잊지 않았는지 확인하기를 원했습니다. 다음은 도움이 될 것입니다. 기본적으로 프로세스는 동일하므로 자세한 내용은 https://technet.microsoft.com/en-us/library/jj205369%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396을 참조하십시오.

 

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.

 

이 프로세스에서는 새 풀이 파일럿 사용자로 구성되어 테스트 된 것으로 가정합니다. Edge Server 기능을 포함해야하므로 모든 측면과 기능이 제대로 작동하는지 확인했습니다. Skype for Business를 지원하는 공용 DNS 레코드뿐만 아니라이 새로운 풀에 대한 기본 사용자 사인온을 지원하기 위해 필요한 DNS 레코드를 컷 오버했습니다. 모든 DNS 및 SRV 레코드를 버리고 여기에서 무엇이든 놓치지 않았는지 확인하는 것이 가장 좋습니다. 위에서 언급 한 기사에서도 필요한 경우 안내를 제공합니다.다음 홉 프런트 엔드 서버와 통신하는 에지 서버와 관련하여 토폴로지 변경 사항을 잊지 마십시오. 여기에서 변경해야 할 가능성이 큽니다. 마지막으로 전화기를 배치 한 경우 인증서 게시와 관련하여 DHCP를 변경해야 할 수도 있습니다. 여기에 안내가 제공됩니다.이 전제 조건을 다룬 후에는 계속 진행할 수 있습니다.

 

 

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

 

 

fyi https://www.ucguys.com/2016/10/lync-2013-to-skype-for-business-server-migration-checklist.html