Export (0) Print
Expand All

Checklist for Deploying Lync Phone Edition

Lync Server 2010
 

Topic Last Modified: 2012-10-01

When deploying IP phones in your organization, use this checklist to guide you through the process.


If you are migrating devices from a previous version (Microsoft Office Communications Server 2007 R2 or Microsoft Office Communications Server 2007) to Lync Server, move the user accounts from the previous version to Lync Server. After you have moved to Lync Server and the user accounts have been moved to Lync Server, the next time the device receive an update, it will restart and automatically migrate from the previous version to Lync Server.

  1. Decide how many devices to deploy and what kind. For details, see Choosing New Devices in the Planning documentation.

  2. If you’re buying new phones, identify and purchase the devices that you want. For details, see Choosing New Devices in the Planning documentation.

  3. Identify the documentation that users can read to guide them through setup. For details, see relevant Quick Start and Work Smart guides.

  1. Deploy Lync Server, Front End Server, and check that Web Services is running.

  2. Deploy Lync Server, Mediation Server or gateways for telephony. For details, see Deploying Enterprise Voice.

  3. Set up your network for external access, if you’re allowing it. For details, see System and Infrastructure Requirements for Devices in the Planning documentation.

  4. Set up dial plans and call routes for users.

  5. Enable Enterprise Voice for users. For details, see Deploying Enterprise Voice.

    tipTip:
    Run a script to verify that users are enabled correctly for Enterprise Voice. For a list of all enabled users, at the command prompt, run:
    Get-CsUser | Where-Object {$_.EnterpriseVoiceEnabled -eq $True} | Select Identity, EnterpriseVoiceEnabled
    For a list of all users that includes information about which users are enabled, at the command prompt, run:
    Get-CsUser | select DisplayName, EnterpriseVoiceEnabled

  1. Create the required DNS and DHCP records. For details, see System and Infrastructure Requirements for Devices in the Planning documentation.

  2. Adjust dial plans and outbound call routes for users, and set up voice policies, as needed. For details, see Create a Dial Plan and Configuring Voice Policies, PSTN Usage Records, and Voice Routes. Set up the appropriate voice policies for users, or review default polices by running the Grant cmdlet for the policy. For details about the Lync Server Management Shell, at the command prompt, run:

    Get-Help Grant-CsClientPolicy -Full
    
  3. If you’re deploying common area phones, create a contact object for each device, and configure the phones. For details, see Configuring Common Area Phones.

  4. Set up test devices.

  1. Run a script to verify that users are enabled correctly for Enterprise Voice, if you’re using it. For a list of all enabled users, at the command prompt, run:

    Get-CsUser | Where-Object {$_.EnterpriseVoiceEnabled -eq $True} | Select Identity, EnterpriseVoiceEnabled
    

    For a list of all users that includes information about which users are enabled, at the command prompt, run:

    Get-CsUser | select DisplayName, EnterpriseVoiceEnabled
    
  2. Set the in-band policies, with logging levels, for devices.

  3. If you are deploying any of the new IP phones (the Aastra 6721ip common area phone, Aastra 6725ip desk phone, HP 4110 IP Phone [common area phone], HP 4120 IP Phone [desk phone], Polycom CX500 IP common area phone, Polycom CX600 IP desk phone, and/or Polycom CX3000 IP conference phone), assign an authentication personal identification number (PIN) to each user, or decide to let users set the PIN for themselves. An administrator can set the PIN from the Lync Server Control Panel or from Lync Server Management Shell (by using the Set –CSClientPIN cmdlet); for details, see Set-CsClientPin in the Lync Server Management Shell documentation. A user can set the PIN by visiting the Dial-in Conferencing Settings and PIN Management page.

  4. Download the latest software updates from the Microsoft website, and deploy them to test devices

  5. Or, ensure that users can access the documentation that you are providing about how to use the device. For details, see relevant Quick Start and Work Smart guides.

  1. If the devices are being deployed externally, make sure that the devices have been logged on to the network successfully before being used externally. Devices must download certificates internally once before they can be used externally. For details, see the “Connection Process for External IP Phones” section in Device Connection Process in the Troubleshooting documentation.

  2. Give the user the device, documentation, and PIN, if available.

  3. Check call detail recording (CDR) to make sure that the user has received and made calls and successfully logged in while in the corporate environment. For details, see Call Detail Recording (CDR) Database Schema in the Reference documentation.

  1. Use Quality of Experience (QoE) reports. For details, see Quality of Experience (QoE) Database Schema in the Reference documentation.

  2. Generate device update reports by using the IP Phone Inventory tool.

  3. Use other monitoring tools, including CDR reports. For details, see Call Detail Recording (CDR) Database Schema in the Reference documentation.

  4. Check the Microsoft website every three months for updates.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft