OCS 2007 R2 DEployment Guide by vverge

VIEWS: 3,253 PAGES: 29

More Info
									Microsoft Office Communications
Server 2007 R2

Deploying Microsoft Office
Communicator 2007 R2


Published: June 2009




For the most up-to-date version of the Deploying Microsoft Office Communicator 2007 R2
documentation and the complete set of the Microsoft® Office Communications Server 2007 R2
online server and client documentation, see the Office Communications Server TechNet Library
at http://go.microsoft.com/fwlink/?LinkID=132106.

Note:
In order to find topics that are referenced by this document but not contained within it, search
for the topic title in the TechNet library at http://go.microsoft.com/fwlink/?LinkID=132106.




                                                                                                   1
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the companies, organizations, products, domain
names, e-mail addresses, logos, people, places, and events depicted in examples herein are
fictitious. No association with any real company, organization, product, domain name, e-mail
address, logo, person, place, or event is intended or should be inferred. Complying with all
applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of Microsoft
Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, ActiveX, Excel, Hyper-V, Internet Explorer, MSN, MSDN, OneNote,
Outlook, PowerPoint, RoundTable, SharePoint, SQL Server, Visio, Visual Basic, Visual C++,
Visual J#, Visual Studio, Windows, Windows Live, Windows Media, Windows Mobile, Windows
NT, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft
group of companies.
All other trademarks are property of their respective owners.




                                                                                                  2
Contents
Deploying Communicator ................................................................................................................ 5

Communicator 2007 R2 Deployment Overview .............................................................................. 5
 New Features and Required Server Roles .................................................................................. 5

Communicator 2007 R2 Upgrade and Interoperability Issues ........................................................ 6
 Special Considerations when Migrating from Live Communications Server 2005 with SP1 ....... 7
 Audio and Video Interoperability with Communicator 2005 is not supported .............................. 7
 Updating from Office Communications Server 2007.................................................................... 7
 Group Policy Deployment Strategies ........................................................................................... 8

Deploying Communicator 2007 R2.................................................................................................. 8
 IT-Managed Installation ................................................................................................................ 8
   Installing on Machines with Multiple Users ............................................................................... 8
   Windows Installer Command Line Options ............................................................................... 9
 User-Managed Installation ........................................................................................................... 9
 Client Post-Setup Verification .................................................................................................... 10
 Uninstalling Communicator 2007 R2.......................................................................................... 10

Customizing Communicator 2007 R2 ............................................................................................ 10
 Configuring Custom Tabs in Communicator 2007 R2 ............................................................... 11
   Configuring Context-Sensitive Custom Tabs .......................................................................... 11
   Defining the Registry Setting .................................................................................................. 12
   Creating the Custom Tab Definition File ................................................................................. 12
     Tab definition file example ................................................................................................... 14
 Configuring Custom Presence States in Communicator 2007 R2 ............................................. 15
   To localize custom presence states using Locale ID schemas .............................................. 16
   To add custom presence states to Office Communicator 2007 R2 ........................................ 16
 Adding Commands to the Communicator 2007 R2 Menus ....................................................... 17
   Defining a Custom Command ................................................................................................. 18
   Accessing a Custom Command ............................................................................................. 19
 Integrating a Third-Party Collaboration Program with Communicator ....................................... 20
   Integrating an Internet-Based Collaboration Program with Communicator 2007 R2 ............. 20
   Integrating a Server-Based Collaboration Program with Communicator 2007 R2 ................. 23
 Customizing the Communicator 2007 R2 Help Menu ................................................................ 24
 Adding Custom Text to the Communicator 2007 R2 Instant Messaging Page ......................... 25
 Executing the Communicator 2007 R2 Shell ............................................................................. 25

Settings Information for Communicator 2007 R2 .......................................................................... 27
 Office Communicator 2007 R2 Group Policy Settings ............................................................... 27
    Group Policy Precedence ....................................................................................................... 27
    Group Policy Updates ............................................................................................................. 28
 Media Port Range Registry Keys ............................................................................................... 29


                                                                                                                                         3
Deploying Communicator
These topics describe how to deploy Microsoft Office Communicator 2007 R2 in your
organization by highlighting the new deployment considerations and changes from the Microsoft
Office Communicator 2007 release. It is assumed that you have already completed the setup for
Microsoft Office Communications Server 2007 R2 in either the Enterprise Edition or Standard
Edition topologies.
In This Document
     Communicator 2007 R2 Deployment Overview
     Communicator 2007 R2 Upgrade and Interoperability Issues
     Deploying Communicator 2007 R2
     Customizing Communicator 2007 R2
     Settings Information for Communicator 2007 R2



Communicator 2007 R2 Deployment
Overview
You can deploy Communicator 2007 R2 across your organization using any method that supports
a Microsoft Windows Installer package (.msi file). In addition, you can control key features and
settings using installation scripts or Active Directory Domain Services Group Policies.


New Features and Required Server Roles
Communicator 2007 R2 provides several new features, some of which require deployment of
additional Office Communications Server 2007 server roles.
   New Calling Features. No additional server roles required. Use alternate phone numbers to
     invite participants; use the keyboard during a call; and copy and paste numbers into the
     dialpad.
   Contact List Enhancements. No additional server roles required. Sort contacts
     alphabetically, display Delegates, or display your Team-Call Group. Search for a contact that
     corresponds to a Response Group and add it to your Contact List.
   Phone-only contacts. No additional server roles required. Add phone numbers to your
     Contact List for quick calling (for example, add phone numbers for friends and family
     members).
   Voice Mail Enhancements. No additional server roles required. Access a contact’s
     voicemail directly, or change your voice mail greeting.



                                                                                                 5
   Call Delegation. No additional server roles required. Select one or more assistants
     (delegates) to receive your incoming phone calls. Delegates must use Office Communicator
     2007 R2 Attendant instead of Communicator.
   Team Call. No additional server roles required. Set up a group of contacts who can answer
     your incoming phone calls.
   Dial-In Audio Conferencing. Requires Unified Communications Application Server. Add a
     conference call number to a Communicator conference so that invitees can dial into the audio
     using any phone.
   Response Groups. Requires Unified Communications Application Server. Create workflows
     to route and queue incoming phone calls to one or more designated agents.
   Desktop Sharing. Requires Application Sharing Conferencing Server. Display entire
     computer desktop to other Communicator participants.
   Meet Now. Requires Application Sharing Conferencing Server. Quickly create a conference
     and invite internal or external (anonymous) participants through e-mail. Participants use
     Communicator or Communicator Web Access to join the conference.
   Automatic Updates. No additional server roles required. Configure Communicator to receive
     automatic updates.
   Archiving, Call Detail Records, and QoE. New Monitoring Server combines Call detail
     record (CDR) and Quality of Experience (QoE) functionality. Archiving Server provides
     archiving.
   Video enhancements. Requires in-band provisioning option to enable/disable receiving
     video capabilities. VGA (640x480 at up to 25 frames/sec ) and HD (1280x720 @ up to 25
     frames/sec) resolution format supported for peer-to-peer calls as long as hardware, webcam
     and bandwidth requirements are met.
   Desk Phone Integration. No additional server roles required. When the USB cable is used
     to connect the desk phone to the computer, the desk phone becomes the preferred audio
     device for calls, conferences, and Microsoft Office Live Meeting sessions.



Communicator 2007 R2 Upgrade and
Interoperability Issues
The Communicator 2007 deployment documentation addresses several interoperability factors to
consider when you move from Communicator 2005 to Communicator 2007. These considerations
are also important when you move from Communicator 2005 to Communicator 2007 R2.




                                                                                                  6
Special Considerations when Migrating from Live
Communications Server 2005 with SP1
During a migration from Live Communications Server 2005 with SP1 to Office Communications
Server 2007 R2, users are re-homed on Office Communications Server 2007 R2 servers so that
they have access to new features and capabilities. Users do not need to update their clients
before they are re-homed on the new servers. However, Office Communicator 2005 users will
operate in legacy mode until they are switched to rich presence mode, after which they can use
Office Communicator 2007 R2, Microsoft Office Communicator Web Access 2007 R2, and
telephony devices that provide rich presence capabilities.


Audio and Video Interoperability with
Communicator 2005 is not supported
Audio and video interoperability with Office Communicator 2005 is not supported in Office
Communicator 2007 R2.


Updating from Office Communications Server
2007
To access new features and capabilities, Office Communicator 2007 R2 users must be homed on
Office Communications Server 2007 R2. When you update from Office Communications Server
2007, you can update clients to Communicator 2007 R2 by using managed installation software
(such as, Microsoft Systems Management Server 2003), a Group Policy object, or Windows
logon scripts.
Moving users from Office Communications Server 2007 to Office Communications Server 2007
R2 involves re-homing users on the new servers. However, clients are not required to be
upgraded in advance before they are re-homed on new servers, so the process of updating
clients can be phased over time.
To enforce the use of Communicator 2007 R2, you can use the client version control feature in
Office Communications Server 2007.

Note:
     In Office Communications Server 2007, if you configured the media port range registry
    key settings to reduce the ports that can be used for media, the recommendations have
    changed. For details about port recommendations, see Media Port Range Registry Keys.
After a Communicator user upgrades to Communicator 2007 R2, the Call Forwarding settings in
earlier versions of Communicator may become unavailable. For example, if the user has already
upgraded Communicator on one computer and then signs in to an earlier version of
Communicator on another computer, the user may be unable to change some or all of the Call
Forwarding settings. The user should upgrade all instances of Communicator or sign in to the
Communicator 2007 R2 version to change Call Forwarding settings.

                                                                                                 7
Group Policy Deployment Strategies
For details about the additions, changes, and deletions to Group Policies for Communicator 2007
R2, see Office Communicator 2007 R2 Group Policy Settings.



Deploying Communicator 2007 R2
You deploy the Communicator 2007 R2 client using the Microsoft Installer package (.msi file).
You can perform an IT-managed roll-out, or allow your end users to install Communicator
individually. The method you choose depends on the size and security requirements of your
organization, the deployment methods you already have in place, and the experience level of
your users, among other factors. The following sections discuss these options in more detail.


IT-Managed Installation
Office Communicator 2007 R2 can be deployed in a managed-desktop environment using the
following methods:
   Microsoft Systems Management Server 2003 (SMS) or Microsoft System Center
     Configuration Manager 2007 R2. Use these products for more complex software installation
     scenarios, where scheduling, inventory, reporting, status, and support for an installation
     across a wide-area network (WAN) are required.
   Active Directory Group Policy. You can create a Group Policy object to deploy Communicator
     2007 R2 to specific users or computers based on group memberships.
   Windows logon scripts. The logon script performs an unattended installation of
     Communicator 2007 R2 when a user logs on. Group policy objects can be used to target
     logon scripts to specific devices or users.

Note:
     The new Office Communicator 2007 R2 Automatic Update feature cannot be used to
     upgrade to Office Communicator 2007 R2 from Office Communicator 2007 or other
     previous Communicator versions.


Installing on Machines with Multiple Users
After Communicator 2007 R2 is installed on an individual computer, it is available to all users of
that computer. Configuration settings for each user are stored in the HKEY_CURRENT_USER
registry hive. Communicator 2007 R2 cannot be installed on a per-user basis on an individual
computer.




                                                                                                     8
Windows Installer Command Line Options
   Quiet-Mode Installation
     When deploying Communicator 2007 R2, you can suppress the installation user interface by
     using the Windows Installer command-line option /qn in your script, as follows. (The filename
     Communicator.msi is used as an example only. The actual name of the Communicator 2007
     R2 .msi file that you deploy may be different.)
     msiexec /qn /i Communicator.msi
     Windows Installer command line options are not case sensitive. For details, see Windows
     Installer documentation on the Microsoft Developer Network (MSDN) Web site.
   Generating a Log File
     You can generate a log file during Communicator 2007 R2 setup by adding /l*v followed by a
     file name to the Windows Installer command line. For example:
     msiexec /qn /i Communicator.msi /l*v logfile.txt
     The asterisk specifies that all possible errors, warnings, and status messages are written to
     the log file, and the v specifies that all messages are verbose. Other log file flags are
     possible. For example, /lem generates a log file that contains only errors and out-of-memory
     or fatal exit information. For a complete list of log file options, see the Windows Installer
     documentation on the MSDN Web site. Event trace log (ETL) files, which may also be
     generated on your computer in the <username>/Tracing folder, enable administrators and
     Microsoft support technicians troubleshoot problems. For details, contact your Microsoft
     support representative.


User-Managed Installation
Communicator 2007 R2 can be installed in your organization using a file server on your network
as a software distribution point for the Communicator 2007 R2 Windows 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.

Note:
     Administrator privileges or administrator credentials (in Windows Vista Standard User
     mode) are required to install Communicator 2007 R2. The files in the installation package
     are protected from tampering by using digital signatures.

Note:
     When you try to download and run the .msi installation file, if users see the error
     message “A network error occurred while attempting to read communicator.msi,” the file
     was corrupted during the download. The user should download the installation file and
     run it again.




                                                                                                   9
Client Post-Setup Verification
To complete a quick check of address book and telephony integration on a client machine, locate
a contact name and try to call the contact from within Communicator 2007 R2.


Uninstalling Communicator 2007 R2
To uninstall Communicator 2007 R2 using a script, include the following command line in your
script:
msiexec /x Communicator.msi
To uninstall Communicator 2007 R2 manually, do the following:
1. Log on to your computer with administrative credentials.
2. Click the Start button, click Control Panel, and then click Programs and Features.
3. Click Microsoft Office Communicator 2007 R2.
4. Click Uninstall at the top of the window.



Customizing Communicator 2007 R2
With Office Communications Server 2007 R2, administrators can add organization-specific
elements to the Communicator 2007 R2 user interface. Customization enables a company or
organization deploying Office Communications Server to provide links, content, or Web-based
applications in the Office Communicator window.
There are various ways to customize Communicator 2007 R2 to meet the needs of your
organization. For example, you can add custom tabs to the Office Communicator window, add
custom presence states, and add commands to Communicator 2007 menus. You can also
integrate Communicator 2007 R2 with any third-party online collaboration program, add Help
menu items, add custom text to the instant messaging window, and execute the Communicator
shell.
The following sections discuss each of these options in more detail.
   Configuring Custom Tabs in Communicator 2007 R2
   Configuring Custom Presence States in Communicator 2007 R2
   Adding Commands to the Communicator 2007 R2 Menus
   Integrating a Third-Party Collaboration Program with Communicator
   Customizing the Communicator 2007 R2 Help Menu
   Adding Custom Text to the Communicator 2007 R2 Instant Messaging Page
   Executing the Communicator 2007 R2 Shell




                                                                                               10
Configuring Custom Tabs in Communicator 2007
R2
In Communicator 2007 R2, the procedure for configuring context-sensitive custom tabs has been
modified in the following ways:
   The context-sensitive custom tab definition includes a new <client> attribute, which
     enables the custom tabs to appear in Office Communicator as well as the Communicator
     Web Access client. Custom tabs do not display in other clients (such as Office
     Communications Server 2007 R2 Attendant).
   The custom tab area is limited in size to one-third of the overall height of the Office
     Communicator contact list window.
   In Communicator 2007, when a tab was added to the Office Communicator contact list
     window, you could pass the URIs of the current user and any selected contacts to the custom
     tab. In Communicator 2007 R2, the URI of the current user can still be passed to the custom
     tab, but the URIs of selected contacts can no longer be passed.
   You can now add custom tabs to the contact card. The URI of the contact displayed can be
     passed to the Web page or application defined on the custom tab.
This topic discusses configuring context-sensitive tabs in more detail.

Note:
     Only Communicator Web Access can be specified in the <client> attribute; other clients
     are currently not supported by this attribute. When you configure custom tabs for both
     Office Communicator and Communicator Web Access, make sure that you test the
     functionality in both clients to ensure that it works as expected.


Configuring Context-Sensitive Custom Tabs
You can extend the Office Communicator 2007 R2 user interface by adding pages of Web-based
content to the Office Communicator window. The pages appear in a pane just below the Contact
List, and the user switches between pages by clicking tabs at the bottom of the pane. Custom
tabs are particularly powerful because they enable Office Communicator to pass the URI of the
current user to the tab defined in the Office Communicator window.
In Communicator 2007 R2, you can now also add tabs to the contact card. The tabs appear at the
bottom of the contact card, and clicking a tab opens a browser window with the defined page. The
URI of the contact displayed in the contact card can be passed to the page defined in the custom
tab.
The process for displaying a custom tab in Office Communicator consists of the following steps:
   Creating the content that you want to load in the custom tab. Save the content to a location
     on your network that will be accessible to Communicator and any other clients that need to
     display custom tabs. Content can be a static Web page or a Web application that includes
     HTML, JavaScript, ActiveX controls, and pop-up windows.



                                                                                                    11
   Creating and configuring the XML file that is used to configure custom tabs for Office
     Communicator. The format of this XML file has been modified to include a new <client>
     attribute, which specifies whether the custom tab should also appear in Communicator Web
     Access clients.
   Defining a registry entry in the \Software\Policies\Microsoft\Communicator registry hive that
     gives the location of the tab definition file.
   Creating a graphic in Portable Network Graphics (PNG) format for the tab. The graphic can
     be up to 16 pixels high by 16 pixels wide, or exactly 32 pixels high by 32 pixels wide. If you
     intend to display the graphic in Communicator Web Access, the graphic must be located on a
     secure (HTTPS) site. Otherwise, a security warning appears when the graphic is displayed.


Defining the Registry Setting
A registry string value, TabURL, contains a URL that points to the XML descriptor file. TabURL
can be added to the following registry keys.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator
The TabURL setting can be added to either section of the registry. However, settings in the
HKEY_LOCAL_MACHINE\SOFTWARE section take precedence.


Creating the Custom Tab Definition File
Office Communicator 2007 R2 uses an XML tab definition file to define the displayed tabs and the
address of the each tab’s main page. The tab definition file has the following format:
<?xml version="1.0" ?>
<tabdata>
<tab>
     <image>https://site/image.png</image>
     <name>Tab title</name>
     <tooltip>Tooltip text</tooltip>
     <contenturl> http://site/content</contenturl>
     <userid>true</userid>
     <contactid>true</contactid>
     <accessibility>inside</accessibility>
     <client>
         <communicatorWebAccess>true</communicatorWebAccess>
     </client>
 </tab>
</tabdata>

                                                                                                     12
XML elements in the Custom Tab Definition file

XML Element                               Description                        Required Element

!ELEMENT tabdata tab*                     Contains 0 or more tab             No
                                          elements. The maximum
                                          number of tab elements is 32.

!ELEMENT tab (image, name,                Contains image, name, tooltip, No
tooltip, contenturl, userid, contactid,   contenturl, userid, contactid,
accessibility, client)                    and accessibility elements.

!ELEMENT image %URI                       Provides a URL for the tab         No
                                          image icon. The image must
                                          be in PNG format.

!ELEMENT name (#PCDATA)                   A friendly name for the XML        Yes
                                          node. This is not displayed in
                                          the user interface.

!ELEMENT tooltip (#PCDATA)                Displays the text of the tooltip   No
                                          when the mouse pauses over
                                          the tab.

!ELEMENT contenturl %URI                  Provides the URI of the page    Yes
                                          to be displayed when the user
                                          selects the tab. The file must
                                          be located on the intranet, or
                                          on a secure or trusted site on
                                          the internet. The link must be
                                          in https:// format
                                          (recommended), or in http:// or
                                          file:/// format.

!ELEMENT userid (“true” | “false”)        Determines whether                 No
                                          Communicator will pass the
                                          user’s Session Initiation
                                          Protocol (SIP) account ID
                                          information to the tab URL.
                                          The default value is “false.”

!ELEMENT contactid (“true” | “false”) Determines whether the tab     No
                                      appears in the contact card.
                                      Tabs defined without contactid
                                      or with contactid=false will
                                      appear only in the
                                      Communicator window. Tabs
                                      defined with contactid=true

                                                                                                13
XML Element                            Description                        Required Element
                                       will appear in the contact card,
                                       and Communicator will pass
                                       the selected contact to the
                                       defined page. The default
                                       value is “false.”

!ELEMENT accessibility (“inside” |     Determines whether the URL         No
“outside” | “both”)                    must be displayed when the
                                       user logs in from inside the
                                       enterprise, outside the
                                       enterprise, or both. This is
                                       provided so that
                                       Communicator 2007 R2 does
                                       not attempt to display intranet
                                       pages when the user logs in
                                       from outside the company,
                                       resulting in a “page not found”
                                       error.

!ELEMENT client                        Specifies the clients that         No
(communicatorWebAccess)                should display the tab, in
                                       addition to Office
                                       Communicator.

!ELEMENT                               Specifies that Communicator        No
communicatorWebAccess (“true” |        Web Access clients should
“false”)                               display the tab.


Note
       The tab icon must be in Portable Network Graphics (PNG) format. If the PNG file cannot
         be found or is not in the correct format, Communicator displays a default icon.
       The HTML file containing the tab content must be in a trusted location on the network.
         The XML and PNG files can be stored in the same location as the HTML file, or on a
         network server or local machine. For example:


Tab definition file example
The following example shows a tab definition file with two tabs.
<?xml version="1.0" ?>
<tabdata>
<tab>
    <image>https://site/news.png</image>

                                                                                                  14
   <name> News</name>
   <tooltip>Technology News</tooltip>
   <contenturl>http://www.contoso.com/news</contenturl>
   <userid>true</userid>
   <contactid>true</contactid>
   <accessibility>inside</accessibility>
   <client>
        <communicatorWebAccess>true</communicatorWebAccess>
   </client>
 </tab>
<tab>
   <image>https://site/sports.png</image>
   <name>Sports</name>
   <tooltip>Sports News</tooltip>
   <contenturl>http://www.contoso.com/sports</contenturl>
   <userid>true</userid>
   <contactid>true</contactid>
   <accessibility>inside</accessibility>
   <client>
        <communicatorWebAccess>true</communicatorWebAccess>
   </client>
 </tab>
</tabdata>


Note:
   The XML file can be used to configure up to 32 tabs on the client. However, exercise
   some caution, because a long list of tabs on a client computer that uses a low-resolution
   screen can become difficult for the user to manage.


Configuring Custom Presence States in
Communicator 2007 R2
To define custom presence states in Office Communicator, you create an XML custom presence
configuration file, and then specify its location with the CustomStateURL registry key.



                                                                                               15
Caution:
     Incorrectly editing the registry may severely damage your system. Before making
     changes to the registry, you should back up any valued data on the computer.
Configuration files have the following properties:
   Custom states can be configured with Available, Busy, and Do Not Disturb.
   The availability attribute determines which Presence button is associated with the status text
     of the custom state. In the example below, the status text, Working from Home, is displayed
     to the right of the Presence button.
   The maximum length of the status text is 64 characters.
   A maximum of four custom presence states can be added.
   Valid address types for the CustomStateURL registry key are FILE:, HTTP:, and HTTPS:
Examples of valid addresses are as follows:
http://lspool.corp.contoso.com/LSFileShare/ClientConfigFolder/Presence.xml
https://lspool.corp.contoso.com/ClientConfigFolder/CustomPresence.xml
file:///c:/LSFileShare/ClientConfigFolder/Group_1_Pres.xml
file://\\\\lspool.corp.contoso.com\\LSFileShare\\ClientConfigFolder\\Presence.xml


To localize custom presence states using Locale ID schemas
Localize your custom presence state by specifying one or more Local ID (LCID) schemas in the
XML configuration file. The example in the next section, To add custom presence states to Office
Communicator 2007 R2, shows localization into English - United States (1033), Norwegian -
Bokmål (1044), French - France (1036), and Turkish (1055). For a list of LCIDs, see List of Locale
ID (LCID) Values as Assigned by Microsoft at
http://r.office.microsoft.com/r/rlidEM?clid=1033&p1=7&p2=LCIDTable.


To add custom presence states to Office Communicator 2007 R2
1. Create an XML configuration file, following the format of the example below and modifying
   the attribute values shown in bold.
     <?xml version="1.0"?> <customStates
     xmlns="http://schemas.microsoft.com/09/2009/communicator/customState
     s"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://schemas.microsoft.com/09/2009/communicato
     r/customStates
     http://livecommteam/sites/main/ice/Wave%2012%20Docs/CustomActivities
     .xsd">       <customState ID="1" availability="online">                        <activity
     LCID="1033">Working from Home</activity>                     <activity
     LCID="1044">activity 2 for 1044</activity>                      <activity
     LCID="1055">activity 3 for 1055</activity>                   </customState>


                                                                                                 16
     <customState ID="2" availability="busy">                       <activity
     LCID="1033">In a Live Meeting</activity>                       <activity
     LCID="1036">Equivalent French String for - In a Live Meeting
     </activity>        </customState>            <customState ID="3"
     availability="busy">               <activity LCID="1033">Meeting with
     Customer</activity>              <activity LCID="1055">meeting with
     client</activity>              <activity LCID="1036">Equivalent French String
     for - Meeting with Customer</activity>                    </customState>
     <customState ID="4" availability="do-not-disturb">                            <activity
     LCID="1033">Interviewing</activity>                  </customState></customStates>
2. Save the XML configuration file to a location on a trusted network site or on the local
   computer. In this example, the file is named Presence.xml, and is placed on the network
   share \\server\comshare.
3. Exit Communicator.
4. In a text editor, prepare a Registry Editor (.REG) file similar to the following:
     Windows Registry Editor Version 5.00
     [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator] @=""
     "CustomStateURL"="file://\\\\server\\comshare\\Presence.xml"
5. Save the file with a .REG extension, and then double-click it to add the CustomStateURL
   value to the computer's registry. Note that you can also add this registry key to the
   HKEY_CURRENT_USER section of the registry, but entries in HKEY_LOCAL_MACHINE
   take precedence.
6. Restart Communicator as usual. The Office Communicator Status menu now contains the
   custom presence states you defined.


Adding Commands to the Communicator 2007 R2
Menus
You can add customized commands to various Communicator menus, and pass the SIP URI of
the current user, and selected contacts, to the application launched by your custom command.
The custom commands that you define appear on the following menus:
   The Tools menu.
   The Actions menu off the Conversation window.
   The right-click menu off the Contact List.
See the "Accessing a Custom Command" section, later in this topic.
You can define custom commands for two types of applications:
   Applications that apply only to the current user and are launched on the local machine.
   Applications that involve additional users, such as an online collaboration program, and must
     be launched on each user's machine.

                                                                                                17
When the application you want to integrate involves other users, the custom command can be
invoked by:
   Selecting one or more users, and then choosing the custom command.
   Starting a two-party or multi-party conversation, and then choosing the custom command.
For a detailed example, see Integrating a Third-Party Collaboration Program with Communicator
in the Client Technical Reference documentation.


Defining a Custom Command
Use the registry settings in the table below to add a command to the Office Communicator
menus. These entries are placed in the registry at
HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\[GUID
of Application].
Custom command registry entries


Name                         Type          Data

Name                         REG_SZ        Name of the application as it appears on the menu.

ApplicationType              DWORD         0 = Executable (default)

                                           Note:
                                               Requires ApplicationInstallPath.
                                           1 = Protocol

ApplicationInstallPath       REG_SZ        Full path of the executable.

                                           Note:
                                               Must be specified if ApplicationType is 0
                                               (Executable).

Path                         REG_SZ        Full path to be launched along with any parameters,
                                           including the default parameter of %user-id% and
                                           %contact-id%.

SessionType                  DWORD         0 = Local session. The application is launched on the
                                           local computer.
                                           1 = Two-party session (default). Communicator 2007
                                           R2 launches the application locally, and then sends a
                                           desktop alert to the other user. The other user clicks
                                           the alert and starts the specified application on their
                                           computer.
                                           2 = Multi-party session. Communicator 2007 R2
                                           launches the application locally, and then sends
                                           desktop alerts to the other users, prompting them to

                                                                                                18
Name                          Type           Data
                                             launch the specified application on their own
                                             computer.

ExtensibleMenu                REG_SZ         A list of the menus where this command will appear,
                                             separated by semi-colons. Possible values are:
                                             MainWindowActions MainWindowRightClick
                                             ConversationWindowActions
                                             ConversationWindowContextual
                                             ConversationWindowRightClick
                                             If ExtensibleMenu is not defined, the default values
                                             of MainWindowRightClick and
                                             ConversationWindowContextual are used.


For example, executing the following Registry Editor (.REG) file results in the addition of the
Contoso Sales Contact Manager menu item to the Actions menu.
Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps
\{1F9F07C6-7E0B-462B-AAD7-98C6DBEA8F69}]
"Name"="Contoso Sales Contact Manager"
"HelpMessage"="The Contoso Sales Contact Manager is not installed.
Contact the Help Desk for more information."
"ApplicationType"="REG_DWORD:00000000"
"ApplicationInstallPath"="C:\\cltest.exe"
"Path"="C:\\cltest.exe %user-id% %contact-id%"
"SessionType"="REG_DWORD:00000001"
"ExtensibleMenu"="ConversationWindowActions;MainWindowRightClick"


Accessing a Custom Command
To access a custom command after it is added
       Do one of the following, depending on the ExtensibleMenu values you define:
            MainWindowActions: On the Office Communicator Title bar, click the down arrow,
              point to Tools, and then click your custom command.
            MainWindowRightClick: Right-click a contact in the Contact List or Search
              Results pane, and then click your custom command.
            ConversationWindowActions: In the Conversation window Title bar, click the


                                                                                                  19
             Menu button, point to Actions, and then click your custom command.
           ConversationWindowContextual: In the Conversation window, click the contextual
             actions drop-down arrow in the top right corner, below the Title bar, and then click
             your custom command.
           ConversationWindowRightClick: In the Conversation window Participant List,
             right-click a contact name, and then click your custom command.




Integrating a Third-Party Collaboration Program
with Communicator
You can integrate Communicator 2007 R2 with any third-party online collaboration program by
adding the same registry settings as those used by Live Meeting 2007.
The integration process described here is the one used for Live Meeting 2007. Therefore, some
steps might not apply to other online collaboration programs.
You can use Communicator 2007 R2 to start data conferencing sessions hosted on an in-house
server, an Internet-based service, or both. The collaboration or data conferencing session can be
started from the Contact List, or from an existing instant messaging, voice, or video session.
Communicator acts only as the vehicle for starting the program. Any existing Communicator 2007
R2 conversations remain active after the online collaboration session has begun.
The following sections describe how Communicator 2007 R2 is integrated with Internet-based
and server-based collaboration programs.


Integrating an Internet-Based Collaboration Program with
Communicator 2007 R2
Generally, the steps involved in integrating a third-party collaboration program are as follows:
1. Information about how the program is added to the registry, as described in the following
   table.
2. The organizer signs in to Communicator and selects contacts for data sharing and
   collaboration. Or, the organizer may already be in a conversation and decides to add data
   conferencing.
3. Communicator 2007 R2 reads the registry, starts the collaboration program, and then sends
   a custom SIP message—an appINVITE—to the selected participants.
4. Participants accept the invitation, and the collaboration program is started on each persons
   computer. Communicator 2007 R2 uses the registry to determine which collaboration
   program to use, and then starts that program by using the parameters included in the
   appINVITE message.
The following table describes the registry entries required to integrate an Internet-based
collaboration program with Communicator 2007 R2.


                                                                                                   20
Registry entries for an Internet-based collaboration program
(HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\<GUI
D of Application>)

Name                    Type     Data

Name                    REG_SZ   The program name for Communicator 2007 R2 menus.

SmallIcon               REG_SZ   Path to 16-pixel x 16-pixel icon, BMP or PNG.

LargeIcon               REG_SZ   Path to 28-pixel x 28-pixel icon, BMP or PNG.

Path                    REG_SZ   Participant path for starting the online collaboration
                                 program.

OriginatorPath          REG_SZ   Organizer path for starting the online collaboration program.
                                 This path can contain one or more custom parameters as
                                 defined in the Parameters subkey. For example,
                                 https://meetserv.adatum.com/cc/%param1%/join
                                 ?id=%param2%&role=present&pw=%param3%

SessionType             DWORD    0 = Local session. The application is started on the local
                                 computer.
                                 1 = Two-party session (default). Communicator 2007 R2
                                 starts the application locally, and then sends a desktop
                                 message to the other user. The other user clicks the
                                 message and starts the specified application on their
                                 computer.
                                 2 = Multiparty session. Communicator 2007 R2 starts the
                                 application locally, and then sends desktop alerts to the
                                 other users, prompting them to start the specified
                                 application on their own computer.

LiveServerIntegration   DWORD    0 or not present = The application has its own conferencing
                                 mechanisms and does not require Office Communications
                                 Server 2007 R2 (default).
                                 1 = Integrates with an in-house server.

ApplicationType         DWORD    1 = Sets the application type to protocol. The other possible
                                 values do not apply in this case. If not present,
                                 ApplicationType defaults to 0 (executable).

ExensibleMenu           REG_SZ   A list of the menus where this command appears,
                                 separated by semi-colons. Possible values are as follows:
                                    MainWindowActions
                                    MainWindowRightClick
                                    ConversationWindowActions


                                                                                              21
Name                    Type        Data
                                       ConversationWindowContextual
                                       ConversationWindowRightClick
                                       ConversationWindowButton
                                    If ExtensibleMenu is not defined, the default values of
                                    MainWindowRightClick and
                                    ConversationWindowContextual are used.

ButtonPriority          DWORD       0 = Application is displayed on the button (default).


Registry entries for an Internet-based collaboration program
(HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\Para
meters<GUID of Application>)

Name                    Type        Data

Param1                  REG_SZ      Used in tokenized format (%Parm1%) to add user-specific
                                    values to the OriginatorPath registry key.

Param2                  REG_SZ      See Param1.

Param3                  REG_SZ      See Param1.


The following example registry settings integrate ADatum Collaboration Client with Communicator
2007 R2.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps
]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps
\{C3F6E17A-855F-44a0-B90D-C0B92D38E5F1}]
"Path"="https://meetingservice.adatum.com/cc/%param1%/meet/%param2%"
"OriginatorPath"="https://meetserv.adatum.com/cc/%param1%/join?id=%para
m2%&role=present&pw=%param3%"
"SessionType"=dword:00000002
"ApplicationType"=dword:00000001
"LiveServerIntegration"=dword:00000000
"Name"="ADatum Online Collaboration Service"
"Extensiblemenu"="MainWindowActions;MainWindowRightClick;ConversationWi
ndowActions;ConversationWindowContextual;ConversationWindowRightClick"


                                                                                              22
[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager]
[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps]
[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\
Parameters]
[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\
Parameters\{C3F6E17A-855F-44a0-B90D-C0B92D38E5F1}]
"Param1"="meetserv"
"Param2"="admin"
"Param3"="abcdefg123"


Integrating a Server-Based Collaboration Program with
Communicator 2007 R2
The settings to add commands for starting a server-based collaboration program from within
Communicator 2007 R2 are similar to those described in the section, Integrating an Internet-
Based Collaboration Program with Communicator 2007 R2. However, the OriginatorPath is not
required, and some values are changed, as described in the following table.

Registry entries for a server-based collaboration program
(HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\<GUI
D of Application>)

Name                  Type          Data

Name                  REG_SZ        Name of the application as it appears on the menu.

ApplicationType       DWORD         Value = 1. Sets the application type to protocol. The other
                                    possible values do not apply in this case. If not present,
                                    ApplicationType defaults to 0 (executable).

Path                  REG_SZ        Protocol used to execute the collaboration program. For
                                    Live Meeting 2007, the value of Path is set to
                                    meet:%conf-uri%.

SessionType           DWORD         0 = Local session. The application is launched on the local
                                    computer.
                                    1 = Two-party session (default). Communicator 2007 R2
                                    launches the application locally, and then sends a desktop
                                    alert to the other user. The other user clicks the alert and
                                    starts the specified application on their computer.
                                    2 = Multi-party session. Communicator 2007 R2 launches
                                    the application locally, and then sends desktop alerts to the
                                    other users, prompting them to launch the specified
                                    application on their computer.


                                                                                               23
Name                  Type         Data

LiveServerIntegration DWORD        1 = Hosted on the in-house server.

MCUType               REG_SZ       DATA = The type of server.

ExtensibleMenu        REG_SZ       A list of the menus where this command appears,
                                   separated by semi-colons. Possible values are:
                                      MainWindowActions
                                      MainWindowRightClick
                                      ConversationWindowActions
                                      ConversationWindowContextual
                                      ConversationWindowRightClick
                                   If ExtensibleMenu is not defined, the default values of
                                   MainWindowRightClick and
                                   ConversationWindowContextual are used.


The following example adds commands to launch ADatum Collaboration Client from within
Communicator 2007 R2.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps
]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps
\{27877e66-615c-4582-ab88-0cb2ca05d951}]
"Path"="meet:%conf-uri%"
"SessionType"=dword:00000002
"LiveServerIntegration"=dword:00000001
"ApplicationType"=dword:00000001
"Name"="ADatum Collaboration Client"
"MCUType"="Data"
"Extensiblemenu"="MainWindowActions;MainWindowRightClick;ConversationWi
ndowActions;ConversationWindowContextual;ConversationWindowRightClick"


Customizing the Communicator 2007 R2 Help
Menu
To add your own link to the Office Communicator Help menu, add the HelpMenuText and
HelpMenuURL registry keys to

                                                                                             24
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator. This policy can
also be set in either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER, but settings in
HKEY_LOCAL_MACHINE take precedence.
For example, setting the HelpMenuURL registry key to a valid network address and the
HelpMenuText key to "Contoso Help Desk" adds the Office Communicator Help menu to both
the main window and the Conversation window.


Adding Custom Text to the Communicator 2007
R2 Instant Messaging Page
You can add a text message that appears in the instant messaging pane of the Conversation
window every time an instant messaging session starts.
To do this, use the IMWarning policy key under
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator. This policy can
also be set in HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Communicator, but
settings in HKEY_LOCAL_MACHINE take precedence.


Executing the Communicator 2007 R2 Shell
You can use command line parameters to quick-launch the Communicator 2007 R2 shell. For
example, if a user clicks on a phone number in another application, the shell can start an instance
of Communicator 2007 R2.
Communicator 2007 R2 can also recognize a semicolon-delimited list of contact names for multi-
party conferencing.
If Communicator 2007 R2 is configured to automatically sign in at launch, the shell execution will
launch the Contact window. If Communicator 2007 R2 is not configured to automatically sign in at
launch, the sign-in window is displayed.
The following table shows the available extensions.
Shell Extensions


Extension               Format of Data                Action

tel:                    tel URI                       Opens the Office Communicator Conversation
                                                      window for an audio call, but does not dial the
                                                      specified number.

callto:                 tel:, sip:, or typeable tel   Opens the Office Communicator Conversation
                        URI                           window for an audio call and dials the specified
                                                      number.

sip:                    SIP URI                       Opens the Office Communicator Conversation
                                                      Window with the specified SIP URI in the
                                                      participant list.

                                                                                                   25
Extension               Format of Data            Action

Sips:                   SIP URI                   If Office Communicator is configured to use the
                                                  Transport Layer Security (TLS) protocol, it
                                                  functions exactly like sip:. If TLS is not being
                                                  used, it displays a dialog box informing the user
                                                  that a higher level of security is required.

conf:                   SIP URI of conference     If URI is self, then instantiate the focus and
                        to join                   bring up roster-only view.
                                                  Otherwise bring up roster view, but do not send
                                                  INVITE.

im:                     SIP URI                   Displays IM-only window with the SIP URI.
                                                  Accepts multiple SIP URIs specified inside
                                                  angle brackets (<>) without any separator.
                                                  im:<sip:user1@host><sip:user2@host>


The following table provides examples of the shell extensions in use.
Shell extension examples


Instance                                                                           Results

Tel:+14255550101                                                                   Opens a phone-
                                                                                   only view with
                                                                                   +14255550101.

Callto:tel:+ 14255550101                                                           Opens a phone-
                                                                                   only view with
                                                                                   +14255550101.

Callto:sip:user@example.com                                                        Opens a phone-
                                                                                   only view with
                                                                                   user@example.
                                                                                   com.

sip:user1@example.com                                                              Opens a
                                                                                   Conversation
                                                                                   window with
                                                                                   user1@example
                                                                                   .com.

conf:sip:user@contoso.com;gruu;opaque=app:conf:focus:id:BDD5MWV0B0SG Opens a
RLMV2006121201144110                                                 Conversation
                                                                     window in
                                                                     phone-only view

                                                                                                   26
Instance                                                                          Results
                                                                                  with a Join
                                                                                  Conference
                                                                                  button.




Settings Information for Communicator 2007
R2
For details about Group Policy settings and port range registry key settings, see Office
Communicator 2007 R2 Group Policy Settings and Media Port Range Registry Keys.


Office Communicator 2007 R2 Group Policy
Settings
One way to provide the appropriate registry settings for each user when you are deploying Office
Communicator 2007 R2 is to define Group Policy settings by using an administrative template
(.adm) file. Administrative template files contain specific information about which Group Policy
settings the application implements, where policies are stored, and how to configure policies.
To define Group Policy settings by using the Communicator 2007 R2 administrative
template file
1. Copy the Communicator.adm file from your distribution disk to the %windir%/inf folder.
2. Use Microsoft Management Console Group Policy Object Editor to enable or disable specific
   policy settings.
You can deploy Communicator 2007 R2 Group Policies without affecting users who are running
Communicator 2005.


Group Policy Precedence
Some Communicator 2007 R2 features and behavior can be configured by the administrator who
is using Office Communications Server 2007 in-band provisioning, or by the user through the
Communicator 2007 R2 Options dialog box. However, Group Policy settings take precedence
over both methods.
Table 1 summarizes the order in which settings take precedence when a conflict occurs.




                                                                                                27
Table 1. Order of precedence for Group Policy settings, in-band provisioning, and
Options dialog box settings


Precedence                  Location or Method of Setting

1                           HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator

2                           HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator

3                           Office Communications Server 2007 in-band provisioning

4                           Communicator 2007 R2 Options dialog box



Group Policy Updates
The primary reference for current Group Policy settings is the
Client_2007_R2_Group_Policy_Settings.xls file, which contains a full definition and values for
each policy.
Office Communicator 2007 R2 Group Policy additions are summarized in Table 2.
Table 2. New Group Policy settings


Policy Name                                       Definition

AllowSimultaneousRinging                          Allows "simul-ring" (simultaneously ring an
                                                  additional number when receiving incoming
                                                  calls). WMI class is
                                                  MSFT_SIPGlobalUCPolicyData.

DisableHTMLIM                                     Disables HTML instant messages.

EnableFullScreenVideoPreviewDisabled              Enables full-screen video with the correct
                                                  aspect ratio and disables video preview for all
                                                  Communicator video calls.

PlayAbbrDialTone                                  Changes the length of the dial tone from a 30-
                                                  second dial tone to a fading, 3-second dial
                                                  tone.

ConferenceAccess                                  Controls whether a conference uses Open
                                                  Authenticated access or Anonymous access.

PC2PCASEncryption                                 For peer-to-peer desktop sharing, controls
                                                  whether encryption is turned on or off.
                                                  Note: For conferences, desktop sharing reuses
                                                  the pool setting for A/V encryption, which also
                                                  turns desktop sharing encryption on or off


                                                                                                 28
Policy Name                                        Definition

DisableApplicationSharingControl                   Prevents the user from sharing control with
                                                   anyone during desktop sharing. This setting
                                                   applies regardless of who started or organized
                                                   the conference.




Media Port Range Registry Keys
If you use the port range registry key settings to reduce the ports that can be used for media, we
recommend that you do this according to the minimums described in this section.
For client endpoints, the port range should not be reduced to the point where it can compromise
the ability of the media stack to negotiate audio, video, and desktop sharing communication ports
during session setup or during a call. More specifically, for an Office Communicator 2007 R2
client, the minimum port range should be 40. A smaller range of ports can result in errors during
call transfer, when starting desktop sharing, and conference escalation scenarios.
Configuring a minimum of 40 ports will enable the client to evaluate the candidate transport
addresses that it can use to stream audio, video, and data to another client, as described in the
IETF Interactive Connectivity Establishment (ICE) protocol. Candidate addresses include local
addresses and an address on the A/V Access Edge server. A minimum of 40 ports in the port
range will also accommodate any escalations from a peer-to-peer call to a conference. (An
escalation of a peer-to-peer call to a conference triggers a temporary doubling of the ports in
use.)
The registry keys for these settings are as follows:
   HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\Portrange\Enabled
     REG_DWORD 1

        HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\Portrange\MaxMed
     iaPort REG_DWORD 40039 (for example)

       HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\Portrange\MinMedi
     aPort REG_DWORD 40000 (for example)




                                                                                                    29

								
To top