|Attention: DocWiki has reached EOL and will be decommissioned January 25, 2019.|
Cisco Unified MeetingPlace, Release 7.0 -- Prerequisites for Scheduling From Microsoft Outlook
Main page: Cisco Unified MeetingPlace, Release 7.0
Up one level: Integration
Note: This page applies to Cisco Unified MeetingPlace, Release 7.0.2 or higher. For information about this topic for Release 7.0.1, see Integrating with Microsoft Outlook.
- Install the msft_int license. See About Licenses.
- Configure a Cisco Unified MeetingPlace user profile for each user who will schedule Cisco Unified MeetingPlace meetings from Microsoft Outlook.
- If you plan to use the Single sign-on default authentication method, the Cisco Unified MeetingPlace User ID must match the Microsoft Outlook username.
- Enable Secure Sockets Layer (SSL) on the Application Server.
- For Release 7.0.2 and later, SSL is required only to use the Single sign-on user authentication method for Microsoft Outlook integration.
- For Release 7.0.1, we recommend SSL for extra security, especially if external users attend meetings by using an external Cisco Unified MeetingPlace Web Server in a DMZ.
- In order for end users to receive complete and correct Cisco Unified MeetingPlace notifications in Microsoft Outlook, the e-mail accounts set up in the Microsoft Outlook client must be configured to use the Server Type option called "Microsoft Exchange Server." Cisco Unified MeetingPlace for Microsoft Outlook does not support other server types, such as POP3.
- In order for a Microsoft Outlook delegate to schedule Cisco Unified MeetingPlace meetings on behalf of other users, the delegate must have the "Editor" level of delegate access permissions.
- Note: Microsoft Outlook delegates are completely separate from Cisco Unified MeetingPlace delegates. The Type of user and User ID of delegate fields in Cisco Unified MeetingPlace user profiles do not affect the privileges and capabilities of Microsoft Outlook delegates.