Migration to Skype for Business Server 2019 - Phase 7 (part 7) - Perficient Blogs
Blog
  • Topics
  • Industries
  • Partners

Explore

Topics

Industries

Partners

Migration to Skype for Business Server 2019 – Phase 7 (part 7)

Welcome back! Or if you’re new, then welcome! In yesterday’s blog we discussed Phase 6 which included moving from a pilot to a production deployment. Today we work on sealing the deal by going over our post-migration tasks. The list of tasks is pretty extensive but we’ll be sure to cover each one in detail so you don’t feel stranded. Also, if you haven’t checked out Phases 1-6, you find them here.

Phase 7: Complete post-migration task

Congrats! You’re in the home stretch! Now that the migration to Skype for Business Server 2019 is complete, we’ll just need to discuss the post-migration tasks that you will need to perform. This list may seem quite extensive but it crucial to cover all of your bases to ensure a smooth transition from the legacy system to your new one. The post-migration list includes:

Migrate existing meetings and meeting content

  • When a user account is moved to a Skype for Business Server 2019 server, the following information is moved with that user account
    • Meetings already scheduled by the user. This includes moving the conferencing directories and conferencing data.
    • User’s personal identification number (PIN). The user’s current PIN continues to work until it expires or the user requests a new PIN.
  • The following user account information does not move to the new server.
    • Meeting content. In order to move the content shared during a meeting, such as PowerPoint, Whiteboard, attachments, or poll data, use the -MoveConferenceData parameter as part of the Move-CsUser cmdlet.

 

Migrate dial-in access numbers

  • Migrating dial-in access numbers to Skype for Business Server 2019 requires running the Move-CsApplicationEndpoint cmdlet to migrate the contact objects.
  • Dial-in access numbers that you created in the legacy install but moved to Skype for Business Server 2019, or that you created in Skype for Business Server 2019 before, during, or after migration, have the following characteristics:
    • Do not appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number page.
    • Appear on the legacy install meeting invitations and the dial-in access number page.
    • Appear on Skype for Business Server 2019 meeting invitations and the dial-in access number page.
    • Cannot be viewed or modified in the Office Communications Server 2007 R2 administrative tool.
    • Can be viewed and modified in the legacy install Control Panel and in the legacy install Management Shell.
    • Can be viewed and modified in the Skype for Business Server 2019 Control Panel and in Skype for Business Server 2019 Management Shell.
    • Can be re-sequenced within the region by using the Set-CsDialinConferencingAccessNumber cmdlet with the Priority parameter.
  • You must finish migrating dial-in access numbers that point to the legacy install pool before you decommission the legacy install pool. If you do not complete dial-in access number migration as described in the following procedure, incoming calls to the access numbers will fail.

Important: You must perform this procedure prior to decommissioning the legacy install pool.

 

Identifying and moving dial-in access numbers

  1. Start the Skype for Business Server Management Shell: Click Start, click All Programs, click Microsoft Skype for Business Server 2019, and then click Skype for Business Server Management Shell.
  2. To move each dial-in access number to a pool hosted on Skype for Business Server 2019, from the command line run: Move-CsApplicationEndpoint -Identity <SIP URI of the access number to be moved> -Target <FQDN of the pool to which the access number is moving>
  3. Open Skype for Business Server Control Panel.
  4. In the left navigation bar, click Conferencing.
  5. Click the Dial-in Access Number tab.
  6. Verify that no dial-in access numbers remain for the legacy install pool from which you are migrating.

Note: When all dial-in access numbers point to the Skype for Business Server 2019 pool, you can then decommission the legacy install pool.

 

Verifying the dial-in access number migration using Skype for Business Server Control Panel

  1. From a user account that is assigned to the CsUserAdministrator role or the CsAdministrator role, log on to any computer in your internal deployment.
  2. Open Skype for Business Server Control Panel.
  3. In the left navigation bar, click Conferencing.
  4. Click the Dial-in Access Number tab.
  5. Verify that all the dial-in access numbers are migrated to the pool hosted on Skype for Business Server 2019.

 

Verifying the dial-in access number migration using Skype for Business Server management shell

  1. Open Skype for Business Server Management Shell.
  2. To return all the dial-in conferencing access numbers migrated, from the command line run: Get-CsDialInConferencingAccessNumber -Filter {Pool -eq "<FQDN of the pool to which the access number is moved>"}
  3. Verify that all the dial-in access numbers are migrated to the pool hosted on Skype for Business Server 2019.

 

Migrate Call Park application settings

  • The migration of the Call Park application includes provisioning the Skype for Business Server 2019 pool with any custom music-on-hold files that have been uploaded in the legacy install, restoring the service-level settings and re-targeting all Call Park orbits to the Skype for Business Server 2019 pool.
  • If customized music-on-hold files have been configured in the pool, these files need to be copied to the new Skype for Business Server 2019 pool.
  • The customized music-on-hold files for the Call Park application are stored in the file store of the pool. To copy the audio files from a pool file store to a Skype for Business Server 2019 file store, use the Xcopy command with the following parameters: Xcopy <Source: legacy Pool CPS File Store Path> <Destination: Skype for Business Server 2019 Pool CPS File Store Path>
    • Example usage: Xcopy “<legacy File Store Path>\OcsFileStore\coX-ApplicationServer-X\AppServerFiles\CPS\” “<Skype for Business Server 2019 File Store Path>\OcsFileStore\coX-ApplicationServer-X\AppServerFiles\CPS\”
  • When all customized audio files have been copied to the Skype for Business Server 2019 file store, the Call Park application settings of the Skype for Business Server 2019 pool must be configured, and the Call Park orbit ranges that are associated with the legacy pool must be reassigned to the Skype for Business Server 2019 pool.
  • The Call Park application settings include the pickup timeout threshold, enabling or disabling music on hold, the maximum call pickup attempts, and the timeout request. You must manage Call Park application settings by using the Skype for Business Server Management Shell to run the Set-CsCpsConfiguration cmdlet. You cannot manage the Call Park application settings using the Skype for Business Server Control Panel.

 

Reconfiguring the Call Park Service Settings

  1. From the Skype for Business Server 2019 Front End Server, open the Skype for Business Server Management Shell.
  2. At the command line, type the following: Set-CsCpsConfiguration -Identity “<LS2013 Call Park Service ID>” -CallPickupTimeoutThreshold “<LS2010 CPS TimeSpan>” -EnableMusicOnHold “<LS2010 CPS value>” -MaxCallPickupAttempts “<LS2010 CPS pickup attempts>” -OnTimeoutURI “<LS2010 CPS timeout URI>”

Note: If your Skype for Business Server 2019 Call Park application settings are identical to the legacy settings, you can skip this step. If Call Park application settings are different for the Skype for Business Server 2019 and legacy environments, use the cmdlet below as a template to update those changes.

To reassign all Call Park orbit ranges from the legacy pool to the Skype for Business Server 2019 pool, you can use either the Skype for Business Server Control Panel or the Skype for Business Server Management Shell.

 

Reassigning all Call Park Orbit Ranges using Skype for Business Control Panel

  1. Open Skype for Business Server Control Panel.
  2. In the left pane, select Voice Features.
  3. Select the Call Park tab.
  4. For each Call Park orbit range assigned to a legacy pool, edit the FQDN of destination server setting and select the Skype for Business Server 2019 pool that will process the Call Park requests.
  5. Select Commit to save the changes.

 

Reassigning all Call Park Orbit Ranges using Skype for Business Management Shell

  1. Open Skype for Business Server Management Shell.
  2. At the command line, type the following: Get-CsCallParkOrbit

This cmdlet lists all of the Call Park orbit ranges in the deployment. All Call Park orbits that have the CallParkServiceId and CallParkServerFqdnparameters set as the legacy pool must be reassigned.

To reassign the legacy Call Park orbit ranges to the Skype for Business Server 2019 pool, at the command line, type the following:

Set-CsCallParkOrbit -Identity "<Call Park Orbit Identity>" -CallParkService "service:ApplicationServer:<Skype for Business Server 2019 Pool FQDN>"

After reassigning all Call Park orbit ranges to the Skype for Business Server 2019 pool, the migration process for the Call Park application will be completed and the Skype for Business Server 2019 pool will handle all future Call Park requests.

 

Migrating response groups

  • Migrating response groups includes copying agent groups, queues, workflows, audio files, and moving Response Group contact objects from the legacy deployment to the Skype for Business Server 2019 pool. After you migrate your legacy response groups, calls to the response groups are handled by the Response Group application in the Skype for Business Server 2019 pool. Calls to response groups are no longer handled by the legacy pool.
  • Before you migrate response groups, you must have deployed a Skype for Business Server 2019 pool that includes the Response Group application. The Response Group application is installed and activated by default when you deploy Enterprise Voice. You can ensure that the Response Group application is installed by running the Get-CsService -ApplicationServer cmdlet.

Note: Although you can migrate response groups before you move all users to the Skype for Business Server 2019 pool, we recommend that you move all users first. In particular, users who are response group agents will not have full functionality of new features until they are moved to the Skype for Business Server 2019 pool. Additionally, you can create new Skype for Business Server 2019 response groups in the Skype for Business Server 2019 pool before you migrate your legacy response groups.

To migrate response groups from a legacy pool to the Skype for Business Server 2019, you run the Move-CsRgsConfiguration cmdlet.

Important: The Response Group migration cmdlet moves the Response Group configuration for the entire pool. You cannot select specific groups, queues, or workflows to migrate.

After you migrate the response groups, you need to use Skype for Business Server Control Panel or Skype for Business Server Management Shell cmdlets to verify that all agent groups, queues, and workflows moved successfully.

When you migrate response groups, the legacy response groups are not removed. When you manage response groups after migration by using either Skype for Business Server Control Panel or Skype for Business Server Management Shell, you can see both the legacy response groups and the Skype for Business Server 2019 response groups. You should apply updates only to the Skype for Business Server 2019 response groups. The legacy response groups are retained only for rollback purposes.

CAUTION: After the migration has been completed and the new response groups have been created, the Skype for Business Server Control Panel and the Skype for Business Server Management Shell will display the legacy and Skype for Business Server 2019 versions of each response group. Do not use Skype for Business Server Control Panel or Skype for Business Server Management Shell to remove the legacy response groups. If you do remove one, the corresponding response group that was created during migration will stop working. The legacy response groups will be removed when you decommission the legacy pool.

Important: We recommend that you do not remove any data from your previous deployment until you decommission the pool. In addition, we strongly recommend that you export response groups immediately after you migrate. If a legacy response group should get removed, you can then restore your response groups from the backup to get Skype for Business Server 2019 response groups running again.

Skype for Business Server 2019 introduces a new Response Group feature called Workflow TypeWorkflow Type can be Managed or Unmanaged. All response groups are migrated with Workflow Type set to Unmanaged and with an empty Manager list.

When you run the Move-CsRgsConfiguration cmdlet, the agent groups, queues, workflows, and audio files remain in the legacy pool for rollback purposes. If you do need to roll back to the legacy pool, however, you need to run the Move-CsApplicationEndpoint cmdlet to move contact objects back to the legacy pool.

The following procedure for migrating Response Group configurations assumes that you have a one-to-one relationship between your legacy pools and the Skype for Business Server 2019 pools. If you plan to consolidate or split up pools during your migration and deployment, you need to plan which legacy pool maps to which Skype for Business Server 2019 pool.

 

Migrating Response Group configurations

  1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or has equivalent administrator rights and permissions.
  2. Start the Skype for Business Server Management Shell: Click Start, click All Programs, click Microsoft Skype for Business Server 2019, and then click Skype for Business Server Management Shell.
  3. Run: Move-CsRgsConfiguration -Source <source pool FQDN> -Destination <destination pool FQDN>
  4. For example: Move-CsRgsConfiguration -Source skype-old.contoso.net -Destination skype-new.contoso.net
  5. After you migrate response groups and agents to the Skype for Business Server 2019 pool, the URL that agents use to sign in and sign out is a Skype for Business Server 2019 URL and is available from the Tools menu. Remind agents to update any references, such as bookmarks, to the new URL.

 

Verifying Response Group migration by using Skype for Business Server Control Panel

  1. Log on to the computer with an account that is a member of RTCUniversalReadOnlyAdmins group or is minimally a member of the CsViewOnlyAdministrator role.
  2. Open a browser window, and then enter the Admin URL to open the Skype for Business Server Control Panel. For details about the different methods you can use to start Skype for Business Server Control Panel, see Open Skype for Business Server 2019 administrative tools.
  3. In the left navigation pane, click Response Groups.
  4. On the Workflow tab, verify that all the workflows in your legacy environment are included in the list.
  5. Click the Queue tab, and verify that all the queues in your legacy environment are included in the list.
  6. Click the Group tab, and verify that all the agent groups in your legacy environment are included in the list.

 

Verifying Response Group migration by using Skype for Business Management Shell

  1. Log on to the computer with an account that is a member of RTCUniversalReadOnlyAdmins group or is minimally a member of the CsViewOnlyAdministrator role.
  2. Start the Skype for Business Server Management Shell: Click Start, click All Programs, click Microsoft Skype for Business Server 2019, and then click Skype for Business Server Management Shell.
  3. For details about the following cmdlets, run:Get-Help <cmdlet name> -Detailed
  4. Run:Get-CsRgsAgentGroup
  5. Verify that all the agent groups in your legacy environment are included in the list.
  6. Run:Get-CsRgsQueue
  7. Verify that all the queues in your legacy environment are included in the list.
  8. Run:Get-CsRgsWorkflow
  9. Verify that all the workflows in your legacy environment are included in the list.

Migrating the Address Book

  • In general, the Address Book is migrated along with the rest of your topology. However, you might need to perform some post-migration steps if you customized the following in your legacy environment:
    • Set the PartitionbyOU WMI property to group Address Book entries by organizational unit (OU).
    • Customized the Address Book normalization rules.
    • Changed the default value for the UseNormalizationRules parameter to False.

Grouped Address Book Entries

  • If you set the PartitionbyOU WMI property to True to create address books for each OU, you need to set the msRTCSIP-GroupingId Active Directory attribute on users and contacts if you want to continue grouping address book entries. You might want to group address book entries to limit the scope of Address Book searches. To use the msRTCSIP-GroupingId attribute, write a script to populate the attribute, assigning the same value for all of the users that you want to group together. For example, assign a single value for all the users in an OU.

Address Book Normalization Rules

  • If you customized Address Book normalization rules in your legacy environment, you must migrate the customized rules to your pilot pool.
  • The default normalization rules for Skype for Business Server 2019 are the same as the default rules for the legacy install. Follow the procedure later in this section to migrate customized normalization rules.

Note: If your organization uses remote call control and you customized Address Book normalization rules, you must perform the procedure in this topic before you can use remote call control. The procedure requires membership in the RTCUniversalServerAdmins group or equivalent rights.

UseNormalizationRules Set to False

  • If you set the value for UseNormalizationRules to False so that users can use phone numbers as they are defined in Active Directory Domain Services without having Skype for Business Server 2019 apply normalization rules, you need to set the UseNormalizationRules and IgnoreGenericRulesparameters to True. Follow the procedure later in this section to set these parameters to True.

 

Migrating Address Book normalization rules

  1. Find the Company_Phone_Number_Normalization_Rules.txt file in the root of the Address Book shared folder, and copy it to the root of the Address Book shared folder in your Skype for Business Server 2019 pilot pool.

    Note: The sample Address Book normalization rules have been installed in your ABS Web component file directory. The path is $installedDriveLetter:\Program Files\Microsoft Skype for Business Server 2019\Web Components\Address Book Files\Files\ Sample_Company_Phone_Number_Normalization_Rules.txt. This file can be copied and renamed as Company_Phone_Number_Normalization_Rules.txt to the address book shared folder’s root directory. For example, the address book shared in $serverX, the path will be similar to: \$serverX \SkypeForBusiness-FileShare\2-WebServices-1\ABFiles.

  2. Use a text editor, such as Notepad, to open the Company_Phone_Number_Normalization_Rules.txt file.
  3. Certain types of entries will not work correctly in Skype for Business Server 2019. Look through the file for the types of entries described in this step, edit them as necessary, and save the changes to the Address Book shared folder in your pilot pool.Strings that include required whitespace or punctuation cause normalization rules to fail because these characters are stripped out of the string that is input to the normalization rules. If you have strings that include required whitespace or punctuation, you need to modify the strings. For example, the following string would cause the normalization rule to fail:
    \s*\(\s*\d\d\d\s*\)\s*\-\s*\d\d\d\s*\-\s*\d\d\d\d
    

    The following string would not cause the normalization rule to fail:

    \s*\(?\s*\d\d\d\s*\)?\s*\-?\s*\d\d\d\s*\-?\s*\d\d\d\d

 

Setting UseNormalizationRules and IgnoreRules to True

  1. Start the Skype for Business Server Management Shell: Click Start, click All Programs, click Microsoft Skype for Business Server 2019, and then click Skype for Business Server Management Shell.
  2. Do one of the following:
    • If your deployment includes only Skype for Business Server 2019, run the following cmdlet at the global level to change the values for UseNormalizationRules and IgnoreGenericRules to True: Set-CsAddressBookConfiguration -identity <XdsIdentity> -UseNormalizationRules=$true -IgnoreGenericRules=$true
    • If your deployment includes a combination of Skype for Business Server 2019 and a legacy install, run the following cmdlet and assign it to each Skype for Business Server 2019 pool in the topology: New-CsAddressBookConfiguration -identity <XdsIdentity> -UseNormalizationRules=$true -IgnoreGenericRules=$true
  3. Wait for Central Management store replication to occur on all pools.

  4. Modify the phone normalization rules file, “Company_Phone_Number_Normalization_Rules.txt”, for your deployment to clear the content. The file is on the file share of each Skype for Business Server 2019 pool. If the file is not present, then create an empty file named “Company_Phone_Number_Normalization_Rules.txt”.
  5. Wait several minutes for all Front End pools to read the new files.
  6. Run the following cmdlet on each Skype for Business Server 2019 pool in your deployment: Update-CsAddressBook

 

Configure the meeting join page

When a user clicks a meeting link in a meeting request, the meeting join page detects which client is already installed on the user’s computer. If a client is already installed, that client opens and joins the meeting. If a client is not installed, by default the Web App opens.

You can modify the behavior of the meeting join page if you want to allow users to join meetings. These configuration options have been removed from the Control Panel, but you configure them by using the CsWebServiceConfiguration cmdlet.

Meeting Join Page CsWebServiceConfiguration Parameters

CsWebServiceConfiguration Parameter Description
ShowJoinUsingLegacyClientLink If set to True, users joining a meeting by using a client application other than Lync will be given the opportunity to join the meeting. The default value is False.
ShowAlternateJoinOptionsExpanded
When set to True, alternate options for joining an online conference will automatically be expanded and shown to users. When set to False (the default value), these options will be available, but the user will have to display the list of options for themselves.
Configuring the meeting join page by using Skype for Business Server 2019 Management Shell
  1. Start the Skype for Business Server 2019 Management Shell: Click Start, click All Programs, click Microsoft Skype for Business Server 2019, and then click Skype for Business Server Management Shell.

  2. Run the following cmdlet:
    Get-CsWebServiceConfiguration
    

    This cmdlet returns the web service configuration settings.

  3. Run the following command, with the parameters set to True or False, depending on your preference (for details about the parameters for this cmdlet, see the Skype for Business Server Management Shell documentation):

    Set-CsWebServiceConfiguration -Identity global -ShowJoinUsingLegacyClientLink $True

Removing legacy Archiving and Monitoring servers

  • If your legacy deployment contained an Archiving Server or a Monitoring Server, after migrating to Skype for Business Server 2019, those servers can be removed from the legacy environment, provided all users have been removed from any remaining legacy pools. You can remove the Archiving Server or Monitoring Server in any sequence. The key requirement is that all users have been removed from any remaining legacy pools. You can move users to Skype for Business Server 2019 by referencing the move procedures in “Phase 4: Moving test users to pilot pool“.
  • After you have confirmed that all users have been removed from any remaining pools, decommision the server and remove roles. A dated, but relevant, example is “Uninstalling Microsoft Lync Server and Removing Server Roles,” which can be downloaded at https://go.microsoft.com/fwlink/p/?linkId=246227.

 

Configuring trusted application servers

  • In a mixed environment, if you create a new trusted application server, you must set the next hop pool to be a Skype for Business Server 2019 pool. In a mixed environment, both the legacy pool and the Skype for Business Server 2019 pool appear in the drop-down list. Selecting the legacy pool is not supported.

Important: If you are migrating a trusted application server, you should also update the version of UCMA you are using. If you create a new Trusted Application Pool for Skype for Business Server 2019, you should update UCMA to the version that is included with Skype for Business Server 2019 or the latest version available.

Select Skype for Business Server 2019 as next hop when creating a Trusted application server

  1. Open Topology Builder.
  2. In the left pane, right-click Trusted application servers and click New Trusted Application Pool.
  3. Enter the Pool FQDN of the trusted application pool and select whether it will be single-server or multiple-server.
  4. Click Next.
  5. On the Select the next hop page, from the list, select the Skype for Business Server 2019 Front End pool.
  6. Click Finish.
  7. Select the top node Skype for Business Server, and from the Action menu select Publish.
  8. Verify that the Trusted Application Pool has been created successfully and is associated with the correct Front End pool.

Deploy Skype for Business Server clients

For details, see Deploy clients for Skype for Business Server in the Deployment documentation.

Connect an SBA (Survivable Branch Appliance)

  • Every Survivable Branch Appliance (SBA) is associated with a Front End pool that serves as a backup registrar for the SBA. When the Front End pool is migrated to Skype for Business Server 2019, the SBA must be disassociated from the Front End pool while the pool is upgraded. After the pool has been migrated to Skype for Business Server 2019, the SBA can be re-associated with the upgraded Front End pool. This involves deleting the SBA from the legacy topology in Topology Builder and then adding the SBA to the Skype for Business Server 2019 topology. Users homed on the legacy SBA must first be moved to another Front End pool before removing the SBA from the topology. After the SBA is added to the Skype for Business Server 2019 topology, those users can be moved back to the SBA. These steps are summarized below:
  1. Move branch users homed on the legacy SBA to another Front End pool.
  2. Remove SBA from the legacy topology to disconnect the existing Front End pool as a backup registrar.
  3. Add SBA to the Skype for Business Server 2019 topology and configure this new Front End pool as the backup registrar.
  4. Move the branch users to the new Skype for Business Server 2019 SBA.

Adding a legacy SBA branch site to your topology

  1. Open Topology Builder.
  2. In the left pane, right-click Branch sites, and then click New Branch Site.
  3. In the Define New Branch Site dialog box, click Name, and then type the name of the branch site.
  4. (Optional) Click Description, and then type a meaningful description for the branch site.
  5. Click Next.
  6. (Optional) In the next Define New Branch Site dialog box, do any of the following:
    1. Click City, and then type the name of the city in which the branch site is located.
    2. Click State/Region, and then type the name of the state or region in which the branch site is located.
    3. Click Country Code, and then type the two-digit calling code for the country/region in which the branch site is located.
  7. Click Next, and then, if you are using a Survivable Branch Appliance or Server at this site, be sure to clear the Open the New Survivable Wizard when this wizard closes check box. Click Finish.
  8. To associate the legacy SBA to the Skype for Business Server 2019 Front End pool:
    1. Expand the branch site that has been created.
    2. Right-click on legacy version, and then click New.
    3. Click Survivable Branch Appliance.
  9. Follow the directions in the wizard that opens. For information about wizard items, see

Note: A SBC can only be associated with a monitoring store.

10. If you are not using a Survivable Branch Appliance or Server at this site, clear the Open the New Survivable Wizard when this wizard closes check box, and then click Finish.

11. Repeat the previous steps for each branch site you want to add to the topology.

Configuring SCOM monitoring 

  • After migrating to Skype for Business Server 2019, you must complete a few tasks to configure Skype for Business Server 2019 to work with System Center Operations Manager.
    • Apply updates to a server elected to manage the central discovery logic.
    • Update the central discovery candidate server registry key.
    • Configure your primary System Center Operations Manager management server to override the candidate central discovery node.

Instructions for carrying out each of these tasks are provided below.

Apply updates to a server elected to manage the central discovery logic.

  1. Elect a server that has the System Center Operations Manager agent files installed and is configured as a candidate discovery node.
  2. Apply updates to this server. See the topic Apply updates.

Update the central discovery candidate server registry key.

  1. On the server elected to manage the central discovery logic, open a Windows PowerShell command window.
  2. At the command line, type the following:

New-Item -Path "HKLM:\Software\Microsoft\Real-Time Communications\Health"

New-Item -Path "HKLM:\Software\Microsoft\Real-Time Communications\Health\CentralDiscoveryCandidate"

Note: Whenever you edit the registry, you may experience an error that the command failed if the registry key already exists. If you experience this, you can safely ignore the error.

Whenever you edit the registry, you may experience an error that the command failed if the registry key already exists. If you experience this, you can safely ignore the error.

  • Migrate Common Area Phones
  • Migrate analog devices

Configuring your primary SCOM management server to override the candidate central discovery watcher node.

  1. On a computer where the System Center Operations Manager console has been installed, expand Management Pack Objects and then select Object Discoveries.
  2. Click Change Scope
  3. From the Scope Management Pack Objects page, select LS Discovery Candidate.
  4. Override the LS Discovery Candidate Effective Value to the name of the candidate server elected in the earlier procedure.
  5. To finalize your changes, restart the health service on the System Center Operations Manager Root Management Server.

Migrating Common Area Phones

Common Area Phones are IP phones that most often reside in a shared workspace or common area, like a lobby, kitchen, or factory floor. Common Area Phones do not need to be connected to a computer to provide Skype for Business Server unified communications (UC) functionality. After migrating a deployment to Skype for Business Server 2019, you must also migrate the contact objects associated with the legacy Common Area Phone. Using Skype for Business Server Management Shell, you will first retrieve all contact objects associated with the legacy Common Area Phones, and then move those objects to the Skype for Business Server 2019 pool.

Migrating Common Area Phones

  1. From the Skype for Business Server 2019 Front End server, open Skype for Business Server Management Shell.
  2. From the command line, type the following: Get-CsCommonAreaPhone -Filter {RegistrarPool -eq "pool01.contoso.net"} | Move-CsCommonAreaPhone -Target pool02.contoso.net
  3. To verify that all contact objects have been moved to the Skype for Business Server 2019 pool, from the Skype for Business Server Management Shell type the following: Get-CsCommonAreaPhone -Filter {RegistrarPool -eq "pool02.contoso.net"}
  4. Verify that all contact objects are now associated with the Skype for Business Server 2019 pool.

Migrate analog devices 

  1. Start the Skype for Business Server Management Shell: Click Start, click All Programs, click Microsoft Skype for Business Server 2019, and then click Skype for Business Server Management Shell.
  2. At the command line, type: Get-CsAnalogDevice -Filter {RegistrarPool -eq "pool01.contoso.net"} | Move-CsAnalogDevice -Target pool02.contoso.net
  3. Verify that all contact objects have been moved to the Skype for Business Server 2019 pool. At the command line, type: Get-CsAnalogDevice -Filter {RegistrarPool -eq "pool02.contoso.net"}
  4. Verify that all the contact objects are now associated with the Skype for Business Server 2019 pool.

Great job! I know this was a longer blog article, but I wanted to make sure we covered all bases so nothing was missed. On that note though, we’re almost done! In Phase 8, we’ll discuss decommissioning our legacy pools! So you can finally say bye bye to Lync Server 2013 or Skype for Business Server 2015 and brag about how your company is using the latest and greatest that Microsoft has to offer (well besides Teams, but that’s a blog for another day 😉 )!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to the Weekly Blog Digest:

Sign Up