Verify Configuration Settings

 

Topic Last Modified: 2011-04-05

After you merge the topology and run the Import-CsLegacyConfiguration cmdlet, verify that your Microsoft Office Communications Server 2007 R2 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:
Instant messaging (IM) and conferencing	Presence policy Conferencing policy
Dial-in conferencing	Dial-in access numbers Dial plans
Enterprise Voice	Voice policy Voice routes Dial plans PSTN usage settings
Communicator Web Access	Simple URLs
External users	External access policies
Archiving	Archiving policy

For most of these policies and settings you can use either Microsoft Lync Server 2010 Control Panel or Lync Server Management Shell cmdlets. For the presence policy, however, you must use a cmdlet.

Note

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

Note

For Mediation Server, legacy configuration settings like server ports and protocols are not merged to Lync Server 2010. The administrator can configure these settings using the Topology Builder. Additionally, the default encryption level for Lync Server 2010 Mediation Server is RequireEncryption. Ensure that your legacy Office Communications Server 2007 R2 pool matches this default encryption level setting.

To verify policies and settings

1. In your Office Communicator 2007 R2 environment, make note of the names of dial plans (formerly known as location profiles), dial-in access numbers (Conferencing Attendant access phone numbers and regions), voice routes, and the policies listed in the preceding table, in addition to the URLs used for Communicator Web Access.

2. Log on to the computer with an account that is a member of the RTCUniversalUserAdmins or RTCUniversalServerAdmins group or minimally is a member of 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 imported conferencing policies, click Conferencing, click Conferencing Policy, and then verify that all the conferencing policies in your Office Communicator 2007 R2 environment are included in the list.

   Note

   The Meeting policy from previous versions of Office Communications Server is now known as the conferencing policy in Lync Server. Additionally, the Anonymous Particpants setting from previous versions of Office Communications Server is now a setting in the Lync Server conferencing policy.

   Note

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

   Note

   If Anonymous Participants is set to Enforce per user in your Office Communications Server 2007 R2 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 Communicator 2007 R2 environment are included in the list.

   Note

   In Lync Server 2010, location profiles are now referred to as dial-plans.

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

   Note

   If voice policy is not set to use per user in your Office Communications Server 2007 R2 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 Communicator 2007 R2 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 Communicator 2007 R2 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 Communicator 2007 R2 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 R2 environment are included in the list.

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

12. To verify presence policies, run:

    Get-CsPresencePolicy
    

    By looking at the name in the Identity parameter, verify that all the presence policies in your Office Communications Server 2007 R2 environment were imported.

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 minimally is a member of 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 syntax of these cmdlets is like the following example:

   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:
   Presence policy	Get-CsPresencePolicy
   Conferencing policy	Get-CsConferencingPolicy Note If conferencing policy is not set to use per user in your Office Communications Server 2007 R2 environment, only global policy settings are imported. No other conferencing policies are imported in this situation. Note If AnonymousParticipants is set to Enforce per user in your Office Communications Server 2007 R2 conferencing policy, two conferencing policies are created during migration: one with AllowAnonymousParticipantsInMeetings set to True and one with AllowAnonymousParticipantsInMeetings set to False. Note To enable federated users from your legacy Office Communications Server 2007 R2 deployment to join meetings scheduled by Lync Server 2010 users, the meeting policy assigned to the Lync Server 2010 user must allow anonymous scheduling. To configure anonymous scheduling, from the Lync Server Management Shell run Get-CsConferencingpolicy , then run Set-CsConferencingPolicy -Identity <ConferencingPolicyName> -AllowAnonymousParticipantsInMeetings $True
   Dial-in access numbers	Get-CsDialInConferencingAccessNumber Note This cmdlet returns only Lync Server 2010 dial-in access numbers. It does not return any Office Communications Server 2007 R2 dial-in access numbers.
   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 R2 environment, only global policy settings are imported. No other voice policies are imported in this situation.
   Voice routes	Get-CsVoiceRoute
   PSTN Usage	Get-CsPstnUsage
   URLs	Get-CsSimpleUrlConfiguration
   External access policies	Get-CsExternalAccessPolicy
   Archiving policy	Get-CsArchivingPolicy