Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2 Administrator's Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Software
  5. TELEPRESENCE MANAGEMENT SUITE EXTENSION 2.2 - FOR MICROSOFT...
  6. Administrator's manual
Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2 Administrator's Manual

Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2 Administrator's Manual

Hide thumbs Also See for TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
Cisco TelePresence
Management Suite
Extension for

Microsoft Exchange

Administrator Guide
Software version 2.2
D14197.06
February 2011

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2 and is the answer not in the manual?

Questions and answers

Related Manuals for Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2

Summary of Contents for Cisco TELEPRESENCE MANAGEMENT SUITE EXTENSION - ADMINISTRATOR GUIDE FOR MICROSOFT EXCHANGE 2.2

  • Page 1: Microsoft Exchange

    Cisco TelePresence Management Suite Extension for Microsoft Exchange Administrator Guide Software version 2.2 D14197.06 February 2011...

  • Page 2: Table Of Contents

    Resolving Custom Attribute Conflicts .................... 41 Additional Reference Materials for Administrators ................41 Functional Overview of Cisco TMSXE Integration ................. 41 Changes and Impact of Cisco TMSXE Installation on Existing Servers ........42 Licensing Requirements ........................ 43 Explanation of Resource Booking Models ..................44 Cisco TMSXE Administrator Guide 2.2...
  • Page 3 Creating the Organization Forms Library in Exchange Server 2007 ... 46 Relevant Microsoft articles: ......................46 Setting up an Organizational Forms Library .................. 46 Appendix B. Using Cisco TMSXE with Redundant Cisco TMS Servers ....49 Pre-Installation ..........................49 Installation ............................49 Operation ............................49 Appendix C.

  • Page 4: Introduction

    Only one Cisco TMSXE installation is required per Exchange organization as long as all users have access to the resource accounts hosted by that server. There should never be more than one Cisco TMSXE installation in a single domain. Installations with complex security models where users cannot see accounts across domains should contact their Cisco sales representatives for assistance planning more complex deployments.

  • Page 5: Requirements

    Connectivity between Exchange Server and Cisco TMS–The Integration requires that the Exchange Server where Cisco TMSXE is installed can open a HTTP/HTTPS connection to the Cisco TMS server. Also required is that the Mail Server Cisco TMS is defined to use, can send emails to the Exchange server‘s domain.

  • Page 6: Client Requirements

    Separate Admin Roles for information on installing via manual methods. During the installation you will also setup a service user on the Cisco TMS Server. If not reusing an existing account for the Cisco TMS Service User, you must supply user credentials that can create a new one.

  • Page 7: Installation And Upgrades

    If you are currently using Exchange Server 2003 and plan to upgrade to Cisco TMSXE without changing to Exchange Server 2007, review the section Upgrading to Cisco TMSXE on Exchange 2003 for pre-installation steps and information on changes in how your integration will differ with the new Cisco TMSXE product before continuing.

  • Page 8: Installer Finds An Existing Account

    3. Restart the installation. To reuse the detected user: 1. Click Next. 2. Let the Cisco TMSXE software know the password for the service user by choosing to either: a. Reset the Password to a strong password b. Supply a new password c.
  • Page 9 Select the Service Account for Cisco TMS. Next, the installer must configure the service account to use on the Cisco TMS Server. You have the option to let the installer detect a previously used account and create a new account if needed (recommended), or manually specify an existing account on the Cisco TMS Server.

  • Page 10: Initialization Of Resource Accounts

    Initialization of Resource Accounts Each Cisco TMS system that you wish to be scheduled from Exchange will have a Domain user account and mailbox in the Exchange environment. The accounts must be configured with specific properties and settings to operate with Cisco TMSXE.

  • Page 11: Existing Resources Or Equipment Accounts Used For Scheduling

    Note: When Cisco TMSXE Integration has been installed and operational, any new systems added to Cisco TMS that will be integrated with Exchange should not be booked in Cisco TMS until after they have been integrated with Exchange using the Configuration tool.
  • Page 12 Cisco TMS via Cisco TMSXE. Select one or more Cisco TMS systems you wish to enable in Exchange from the left hand list. Use the shift or control keys to select multiple systems. Click the  button.
  • Page 13 Directory design these changes may take upwards of an hour to replicate across domain controllers. If you experience errors or inconsistencies with account creation, please shutdown the Configuration tool and allow time for your Active Directory changes to propagate. Cisco TMSXE Administrator Guide 2.2 Page 13 of 60...
  • Page 14 Note: The password for resource accounts is not needed by users or in normal use. It is only for administrators that may wish to log into the account/mailbox directly. The resource account passwords can be changed using standard AD tools afterwards without affecting the Cisco TMSXE integration.

  • Page 15: Starting The Synchronizer

    Note: Meetings with no end date can not be booked in Cisco TMS and will not synchronize to Cisco TMS. After Cisco TMSXE is installed, any meetings of this type should be edited using Outlook to a new meeting with a fixed end-date.

  • Page 16: Optional-Deploying The Tandberg Form

    These will limit how a user can book a meeting from Outlook, but will not limit bookings made from Cisco TMS or directly in the Resource‘s calendar. Administrators may need to tune these restrictions to their desired values to control booking by Outlook users.
  • Page 17 Each should be completed for new installations that wish to use the TANDBERG form. For customers upgrading Cisco TMSXE without changing your Exchange Server version, only the Publishing the Form section is necessary. The other sections were completed in your previous installation.
  • Page 18 Properties. In the pop-up window, select the Permissions tab. ‘Folders’ may reside on root level if the Exchange System Manager is not configured to show administrative groups Cisco TMSXE Administrator Guide 2.2 Page 18 of 60...
  • Page 19 .In this folder is the file VideoConference.oft . Copy the VideoConference.oft file using the method of your choice to a client computer with Outlook installed. Using Outlook, log in as the user you assigned ‗owner‘ permission to. Cisco TMSXE Administrator Guide 2.2 Page 19 of 60...
  • Page 20 Click the Browse button to locate the folder where you copied the OFT file to and click OK. VideoConference should be seen in the list, highlight it and Click Open You can now continue with the normal publishing steps Cisco TMSXE Administrator Guide 2.2 Page 20 of 60...
  • Page 21 Form name: VideoConference  The screen should look like the image below. Click Publish when complete The form is now published and available for users to choose as their appointment form. Cisco TMSXE Administrator Guide 2.2 Page 21 of 60...
  • Page 22 Pane in Outlook, calendar events can not be previewed if the entry was created using the TANDBERG form. Users must open the item to view it. The examples in this document reference other forms, the TANDBERG form replaces the IPM.Appointment form Cisco TMSXE Administrator Guide 2.2 Page 22 of 60...

  • Page 23: Uninstalling Or Repairing The Installation

    To repair the installation: Start the original Cisco TMSXE setup file on the server if available. If not, the Cisco TMSXE installer is located on the Cisco TMS installation media. Open the index page using browse.bat and click the Install link to start the installation program.

  • Page 24: Upgrading

    TMS-side service account, when prompted, use the Let the installer create a service account if needed option. This will cause the service user on the Cisco TMS server to be reused, and have its password and Service flag in Cisco TMS reset as part of the installation.

  • Page 25: Upgrading To Cisco Tmsxe And Migrating To Exchange 2007

    Since Exchange 2007 is not installed in-place over an existing Exchange 2003 server, these instructions assume you will install Cisco TMSXE on a different Exchange server then what was used previously. Migration of an organization from Exchange 2003 to 2007 is out of the scope of this document and will only cover moving the Integration product.
  • Page 26 Cisco TMS-side service account, when prompted, use the Let the installer create a service account if needed option. This will cause the service user on the Cisco TMS server to be reused, and have its password and Service flag in Cisco TMS reset as part of the installation.
  • Page 27 Asynchronous Booking model, the users will immediately be allowed to save the meeting, and shortly after will receive a meeting accept/reject notice from each resource booked in the meeting. Please see the Error! Reference source not found. section regarding End-user operation. Cisco TMSXE Administrator Guide 2.2 Page 27 of 60...

  • Page 28: Software Reference Guide

    When the Configuration tool is launched, it will perform a series of tests on the components of the integration and the accounts it discovers as integrated with Cisco TMS. These tests are diagnostics tests to detect any changes to the resource accounts, server, or service accounts that may adversely affect the integration.
  • Page 29 CAL for the server‘s components themselves. Adding Systems Button The Arrow button between the columns in the Operation tab is used to link systems from Cisco TMS to resource accounts in Exchange. Details regarding this functionality are covered in section Enabling Cisco TMS systems in Exchange.
  • Page 30 Synchronizer. Clicking the button will restart the Synchronizer from where it last left off. If the Synchronizer has been told to start since installation, the button will be labeled Restart Synchronizer. The Synchronizer keeps track of a transaction history in Cisco TMS so that it only has Cisco TMSXE Administrator Guide 2.2...

  • Page 31: Configuration Tab

    Clicking Restart Synchronizer will reset the Integration‘s start point in that transaction history and begin processing all scheduling changes in Cisco TMS from the beginning. Restarting the Synchronizer is not needed in normal operation and is only for specific, advanced situations.
  • Page 32 Integration. To change the password of the service account itself, do so using Windows and then enter the password here to update the Cisco TMSXE integration. Server The network address of the Cisco TMS server. If using a load balancer for Cisco TMS, enter the shared address of Cisco TMS. Secure...

  • Page 33: Resource Calendar Permissions

    Configuration tool. In Exchange 2003 installations, these groups are defined during installation, and users must be a member of the Author group to be able to Cisco TMSXE Administrator Guide 2.2 Page 33 of 60...

  • Page 34: Enabling Cisco Tms Systems In Exchange

    Exchange accounts that have been determined to be integrated with Cisco TMS via Cisco TMSXE. Select one or more Cisco TMS systems you wish to enable in Exchange from the left hand list. Use the shift or control keys to select multiple systems. Click the  button.
  • Page 35 The center panel displays a list view of your user account and mailbox to be associated Active Directory‘s organizational structure. with the Cisco TMS system. Select Use an Existing AD Account. The center panel will Expand the tree if necessary and highlight the show you your domain‘s organizational...

  • Page 36: Manually Enabling Auto-Accept

    Note: Meetings with no end date can not be booked in Cisco TMS and will synchronize to Cisco TMS. After Cisco TMSXE is installed, any meetings of this type should be edited using Outlook to a new meeting with a fixed end-date.
  • Page 37 When the mailbox opens, select from the menu Tools > Options. Cisco TMSXE Administrator Guide 2.2 Page 37 of 60...
  • Page 38 Mark the checkbox for Automatically accept meeting request and process cancellations and click If you are prompted about setting default permissions, accept the change Click OK to close the Calendar Options, and click OK again to close the Options panel. Close Outlook Cisco TMSXE Administrator Guide 2.2 Page 38 of 60...

  • Page 39: Cisco Tmsxe Logging Features

    The Loglevel value is used for controlling the amount of detail that is logged for a particular component. To set the LogLevel for a particular component, create a new String Value in the Cisco TMSXE registry key whose name is LogLevel ComponentName replacing ComponentName with one of the valid Component names.
  • Page 40 This registry setting is used to control size. The log size is a string whose value is the maximum size of a log files in bytes. To set the Log Size, create a new String Value in the Cisco TMSXE registry key whose name is Log Size .

  • Page 41: Resolving Custom Attribute Conflicts

    When running the Cisco TMSXE installer and Configuration tool, they will now use the custom attribute ID defined in the registry key. If you need to make these changes and Cisco TMSXE has already been installed; uninstall, set the key, and then reinstall Cisco TMSXE.

  • Page 42: Changes And Impact Of Cisco Tmsxe Installation On Existing Servers

    Cisco TMS, and a meeting is created in Cisco TMS based on the details of the Exchange invitation. If the meeting is able to be saved in Cisco TMS, the meeting is allowed to be saved in Exchange, and the booking user gets an acceptance message followed by an email with the meeting details from Cisco TMS.

  • Page 43: Licensing Requirements

    The Cisco TMSXE Integration has no impact on your Exchange licenses from Microsoft. Cisco TMS Licensing Each system that is to be integrated with Exchange must already exist in Cisco TMS and be properly licensed itself in Cisco TMS. For licensing of Cisco TMSXE Integration, the licensing can be per system, or per Exchange Server integrated with Cisco TMS depending on the type of license you purchase.

  • Page 44: Explanation Of Resource Booking Models

    Direct Resource Booking model and therefore it is no longer the default method and is not covered by the standard instructions in this manual. Notes on using Direct Resource Booking in Exchange 2007 with Cisco TMSXE can be found in the section Using Direct Resource Booking in Exchange 2007..
  • Page 45 To use Direct Resource Booking, an account must be a user mailbox type, not a room or equipment type. This means you can not use the Configuration tool to create new mailbox accounts. You may follow the steps in the Appendix for using Cisco TMSXE with Separate Admin roles to manually create accounts.

  • Page 46: Appendix A. Creating The Organization Forms Library In Exchange Server 2007

    Public Folder Database. When completed, you should be able to open the Public Folder Management Console, and be able to expand System Public Folders and see EFORMS REGISTRY Cisco TMSXE Administrator Guide 2.2 Page 46 of 60...
  • Page 47 Right click the row with the Display Name Public Folders and select Open Store Expand the tree in the left panel down to the TANDBERG Form folder. Public Root > NON_IPM_SUBTREE > EFORMS REGISTRY > TANDBERG Form Cisco TMSXE Administrator Guide 2.2 Page 47 of 60...
  • Page 48 This completes the steps necessary to create the Organizational Forms Library. Administrators performing an installation can continue onto the Publishing the TANDBERG Form and Configuring clients to use the Form sections of the documentation. Cisco TMSXE Administrator Guide 2.2 Page 48 of 60...

  • Page 49: Appendix B. Using Cisco Tmsxe With Redundant Cisco Tms Servers

    TMS server and enter the credentials of the Domain user you designated to use as the service user. For the Cisco TMS address, be sure to enter the address that is shared by your Cisco TMS servers (the DNS hostname, or load balanced address, etc). Do not select the HTTPS option unless all servers have been properly configured for HTTPS operation.

  • Page 50: Appendix C. Using Cisco Tmsxe With Exchange 2007 Clustering

    Exchange Server that is a node of a Clustered Mail Server (CMS) and will fail-over along with the Exchange Service. In a CMS setup, Cisco TMSXE is installed on each node in the Exchange Cluster. The Cisco TMSXE Integration itself will not be clustered, and therefore will not show up in the Services/Applications of the Failover Management Console.

  • Page 51: Upgrades

    Full Control. Click OK to save the changes. Install on the Active Node – You will perform the complete installation of Cisco TMSXE on the Active Node of the cluster as if it were a stand-alone installation following the instructions under...
  • Page 52  Most of the configuration elements of the Cisco TMSXE installation shown on the Configuration and Resource Defaults tabs are stored locally on each node, and therefore must be updated on each node if changed. To update the settings, open the Configuration tool on each node and update the value.

  • Page 53: Appendix D. Using Cisco Tmsxe With Separate Admin Roles

    The AD-Admin must create or decide which OU in Active Directory will be used for accounts related to the Cisco TMSXE Integration. Accounts are not required to be in the same OU, but the policy should be followed for consistency with the standard product.
  • Page 54 TMS-Service account created in the earlier steps. Ensure the user is a member of a Cisco TMS group that has the book on behalf of permission and book permission on all systems that will be integrated (recommend using Site Administrator group which will allow access to all systems).
  • Page 55 Service User Password, select I have the password and will provide it below and enter the password set during pre-installation.  When prompted for the Cisco TMS Service user account, select I have created a service user on the TMS server and enter the credentials of the tmsconfuser account setup during pre- installation.

  • Page 56: Upgrades

    Repeat the previous step for each of the following actions Enable Autobooking (Re-) Book all Meetings The pre-staged accounts are now properly integrated with Cisco TMSXE. Completing the Installation When the initial resource accounts have been fully enabled using the Configuration tool. The remainder of the installation should be completed using the standard installation instructions under: Starting the Synchronizer –...
  • Page 57 TMS-Service account the full mailbox access permission granted to the TMS-Service Account To remove an account from both the Cisco TMSXE Integration and Exchange-only booking, simply have the AD-Admin delete both the user account and mailbox.

  • Page 58: Checking For Updates And Getting Help

    If you experience any problems when configuring or using Cisco TelePresence Management Suite Extension for Microsoft Exchange, consult the documentation at http://www.tandberg.com/support/video-conferencing-...

  • Page 59: References And Related Documents

    The following table lists documents and web sites referenced in this document. All product documentation can be found on our site. Name Document reference Conferencing eXtensions for Microsoft D14753.01 Exchange User Guide Cisco TMSXE Administrator Guide 2.2 Page 59 of 60...
  • Page 60 THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners.

Table of Contents