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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

To verify presence policies, run:

	Copy Code
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.

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.

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

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

The syntax of these cmdlets is like the following example:

	Copy Code
Get-CsConferencingPolicy

For details about these cmdlets, run:

	Copy Code
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