• Decide how many devices to deploy and what kind. (See Choosing New Devices.)
  
  
• If you’re buying new phones, identify and purchase the devices that you want. (See Choosing New Devices.)
  
  
• Identify the information that users can read to guide them through setup and use and the medium through which the information will be delivered. (See relevant Quick Start and Work Smart documents.)
  
  

• If you’re allowing external use, deploy Edge server. (See System and Infrastructure Requirements for Devices.)
  
  
• Deploy the mediation server/gateways for telephony. (See Deploying the Enterprise Voice Workload, in the Deployment Guide.)
  
  
• Start Web Services. (See Start or Stop Communications Server Services, in the Communications Server Control Panel Help.)
  
  
• Identify users, and enable Enterprise Voice for them. (See Deploying the Enterprise Voice Workload, in the Deployment Guide.)
  
  

Tip:

Run a script to verify that users are enabled correctly for Enterprise Voice. For a list of all enabled users, at the command prompt, type 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, type Get-CsUser | select DisplayName, EnterpriseVoiceEnabled.Set up dial plans and call routes for users. (See <Information to come>, in the Communications Server Control Panel Help.)

• If you’re deploying IP phones, open the required port and create the required DNS and DHCP records. (See System and Infrastructure Requirements for Devices.)
  
  
• Create a contact object for each device. This is only applies to as conferencing or common area phones.
  
  
• Set up the appropriate voice policies for users, or review default polices by running the Grant- cmdlet for the policy. (Run Get-Help Grant-CsClientPolicy –Full | more from the Communications Server Management Shell.) If you’re deploying common area phones, plan usage scenarios, and configure polices and objects, as needed. (See Appendix A: Configuring Common Area Phones.)
  
  
• If your deployment includes analog devices, configure the gateway and devices. (See Appendix B: Configuring Analog Gateways and Devices.)
  
  

• If you are deploying the new IP phones, assign an authentication PIN to each user, or decide to let users set the PIN for him or herself.. An administrator can set the PIN from the Communications Server Control Panel or from Communications Server Management Shell (Set -CSClientPIN). (See Set-CsClientPin, in the Shell Help, or, Set A User's PIN, in the Control Panel Help.) A user can set the PIN by visiting the Dial-in Conferencing Settings and PIN Management page.
  
  
• Set the logging levels. (See Modify Settings for Log Files of Device Update Activity, in the Control Panel Help.)
  
  
• Download the latest software updates from Microsoft.com, and deploy them to test devices. (See View Software Updates for Devices in Your Organization, in the Control Panel Help.) Once you are satisfied with these, deploy them to all phone devices.
  
  
• Ensure that users can access the end-user documentation that you are providing.
  
  

• Give the user the device, documentation, and PIN, if available.
  
  
• 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. (See Call Detail Recording (CDR) Database Schema, in the OCS_14_ITPro.chm.)
  
  

• Use Quality of Experience (QoE) reports. (See Quality of Experience (QoE) Database Schema, in the OCS_14_ITPro.chm.)
  
  
• Generate device update reports. (From IP Phone Inventory tool.)
  
  
• Use other monitoring tools, including CDR reports. (See Call Detail Recording (CDR) Database Schema, in the OCS_14_ITPro.chm.)
  
  
• Check Microsoft.com every three months for updates.
  
  

When a device is upgraded, it will be on the latest version of Communications Server, for example Microsoft Communications Server 2010. To have it point to a different server, you would move the users from Microsoft Office Communications Server 2007 R2 to Communications Server 2010 and have the user to sign off and then sign back on.