Verify Configuration Settings (Office Communications Server 2007 Migration)

 

Topic Last Modified: 2011-04-06

After you merge the topology and run the Import-CsLegacyConfiguration cmdlet, verify that your Microsoft Office Communications Server 2007 policies and settings were imported to Microsoft Lync Server 2010. The following table lists the policies and settings that you should verify.

Policies and Settings to Verify after Migration

If you use this workload:	Verify these policies and settings:
Conferencing	Conferencing policy
Enterprise Voice	Voice policy Voice routes Dial plans Public switched telephone network (PSTN) usage settings
External users	External access policies
Archiving	Archiving policy

You can use either Microsoft Lync Server 2010 Control Panel or Lync Server Management Shell cmdlets to verify these policies and settings.

Note

• To verify policies, you can compare the policy names that you have in your Office Communications Server 2007 deployment to the names that are now in Lync Server 2010 to ensure that all the policies were migrated. It is not necessary to compare all the settings within a policy.

• For Mediation Server, legacy configuration settings such as server ports and protocols are not imported to Lync Server 2010. You can configure these settings by using Topology Builder. Additionally, the default encryption level for Lync Server 2010 Mediation Server is RequireEncryption. Ensure that your legacy Office Communications Server 2007 pool matches this default encryption level setting.

To verify policies and settings

1. In your Office Communications Server 2007 environment, make note of the names of dial plans (formerly known as location profiles), voice routes, PSTN usage settings, and the policies listed in the preceding table.

2. Log on to the computer with an account that is a member of the RTCUniversalUserAdmins or RTCUniversalServerAdmins group or that is assigned to the CsViewOnlyAdministrator administrative role.

3. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

4. To verify migrated conferencing policies, click Conferencing, click Conferencing Policy, and then verify that all the conferencing policies in your Office Communications Server 2007 environment are included in the list.

   Note

   • Meeting policy in previous versions of Office Communications Server is known as conferencing policy in Lync Server. In addition, the Anonymous Participants setting in previous versions of Office Communications Server is a setting in conferencing policy in Lync Server.

   • In Office Communications Server 2007, if conferencing policy is not set to use per user, only global policy settings are imported. No other conference policies are imported in this situation.

   • If AnonymousParticipants is set to Enforce per user in your Office Communications Server 2007 conferencing policy, two conferencing policies are created during migration: one with AllowAnonymousParticipantsInMeetings set to True and one with AllowAnonymousParticipantsInMeetings set to False.

5. To verify imported dial plans, click Voice Routing, click Dial Plan, and then verify that all the dial plans in your Office Communications Server 2007 environment are included in the list.

   Note

   In Lync Server 2010, location profiles are known as dial plans.

6. To verify migrated voice policies, click Voice Routing, click Voice Policy, and then verify that all the voice policies in your Office Communications Server 2007 environment are included in the list.

   Note

   If voice policy is not set to use per user in your Office Communications Server 2007 environment, only global policy settings are imported. No other voice policies are imported in this situation.

7. To verify imported voice routes, click Voice Routing, click Route, and then verify that all the voice routes in your Office Communications Server 2007 environment are included in the list.

8. To verify imported PSTN usage settings, click Voice Routing, click PSTN Usage, and then verify that the PSTN Usage settings from your Office Communications Server 2007 environment are included in the list.

9. To verify imported external access policies, click External User Access, click External Access Policy, and then verify that all the external access policies in your Office Communications Server 2007 environment are included in the list.

10. To verify archiving policies, click Monitoring and Archiving, click Archiving Policy, and then verify that all the archiving policies in your Office Communications Server 2007 environment are included in the list.

To verify policies and settings by using cmdlets

1. Log on to the computer with an account that is a member of the RTCUniversalUserAdmins or RTCUniversalServerAdmins group or that is assigned to the CsViewOnlyAdministrator administrative role.

2. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

3. Run the cmdlets in the following table to verify policies and settings.

   The following is an example of the syntax of these cmdlets:

   Get-CsConferencingPolicy
   

   For details about these cmdlets, run:

   Get-Help <cmdlet name> -Detailed
   

   Cmdlets to Verify Configuration Settings

   For this policy or setting:	Use this cmdlet:
   Conferencing policy	Get-CsConferencingPolicy Note If conferencing policy is not set to use per user in your Office Communications Server 2007 environment, only global policy settings are imported. No other conferencing policies are imported in this situation. If AnonymousParticipants is set to Enforce per user in your Office Communications Server 2007 conferencing policy, two conferencing policies are created during migration: one with AllowAnonymousParticipantsInMeetings set to True and one with AllowAnonymousParticipantsInMeetings set to False. To enable federated users from your Office Communications Server 2007 deployment to join meetings scheduled by Lync Server 2010 users, the meeting policy assigned to the Lync Server 2010 users must allow anonymous scheduling. To configure anonymous scheduling, from the Lync Server Management Shell, run Get-CsConferencingpolicy, and then run Set-CsConferencingPolicy -Identity <ConferencingPolicyName> -AllowAnonymousParticipantsInMeetings $true
   Dial plans	Get-CsDialPlan
   Voice policy	Get-CsVoicePolicy Note If voice policy is not set to use per user in your Office Communications Server 2007 environment, only global policy settings are imported. No other voice policies are imported in this situation.
   Voice routes	Get-CsVoiceRoute
   PSTN Usage	Get-CsPstnUsage
   External access policies	Get-CsExternalAccessPolicy
   Archiving policy	Get-CsArchivingPolicy