Step 4. Plan Your Deployment of Communicator Mobile (2007 R2 Beta)

  • Article

[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

This section lists key steps to consider during the Communicator Mobile for Windows Mobile deployment process.

Verify Office Communicator 2007 R2 Deployment

An Office Communications Server 2007 R2 Standard Edition or Enterprise Edition deployment is required to use Communicator Mobile for Windows Mobile. To enable the various features including instant messaging (IM), Single Number Reach, and Presence, additional server roles are required. The server roles include:

  • Mediation Server
  • Edge Server

Furthermore, the Outside Voice Control application that is automatically installed on each Front End server must be activated and running.

Install the Communicator Mobile for Windows Mobile Software

The Communicator Mobile for Windows Mobile download includes a Communicator Mobile for Windows Mobile installer package (.msi file) for each type of Windows Mobile device (Pocket PC or Smartphone) and installs the appropriate cabinet (.cab file) on the device.

This beta release of Communicator Mobile for Windows Mobile supports the following client installation methods:

Install using Windows Mobile Device Center.

For details about installing Communicator Mobile for Windows Mobile using Windows Mobile Device Center, see Installing Communicator Mobile using WMDC.

Install using ActiveSync.

For details about installing Communicator Mobile for Windows Mobile using ActiveSync, see Installing Communicator Mobile using ActiveSync 4.5 .

Install from a storage card on the mobile device.

For details about installing Communicator Mobile for Windows Mobile from a storage card on the mobile device, see Installing Communicator Mobile for Windows Mobile from a Storage Card .

Software distribution point.

If users in your organization can install their own software, you can use a file server on your network as a software distribution point for the Communicator Mobile for Windows Mobile installer package. At rollout time, you can send an e-mail to users explaining the installation process and provide a link to the distribution point.

Upgrade to Communicator Mobile for Windows Mobile.

If you previously deployed the Communicator Mobile 2007 release in your environment, you can upgrade to Communicator Mobile for Windows Mobile. An upgrade will not retain the Communicator Mobile 2007 settings and configuration information.

This beta release does not support upgrading Communicator Mobile 2005 clients. You must remove Communicator Mobile 2005 from client computers and devices before installing Communicator Mobile for Windows Mobile.

Configure the Client

Communicator Mobile for Windows Mobile must be configured with your account details, including server and account information, before you can sign in. Your Office Communications Server 2007 R2 administrator should provide to you the following information:

  • Sign-in name
  • Domain name, user name, and password
  • Internal and external SIP server names

For details, see Configuring the Client.

Client Post-Setup Verification

Note: The Global Address List Contact Search feature will be available in the RTM version of Communicator Mobile for Windows Mobile. For this Beta release, users must enter a complete email address and add it to their Contact list.

After you configure the client and sign in successfully, use the following test to verify your installation completed successfully:

Global Address List Contact Search

  1. Click Menu, and then click Find/Add Someone.
  2. Search for a contact that exists only in the global address list.
  3. Ensure that the contact name appears in the search results.
  4. Select the contact name, click Menu, and then click Add Contact.