See the Known Issues and Limitations for the Webex Meetings Desktop Application (WBS39.10 and Later) for more info on the desktop app.

Windows and Mac

Can't edit migrated meetings scheduled with Webex Productivity Tools

After installing the Microsoft Office 365 add-in, users may see two Webex icons in their Microsoft Outlook window. The icon in the Webex section uses Productivity Tools, and the icon in the Cisco Webex section uses the Cisco Webex Meetings Scheduler.

If a user signs in to the Cisco Webex Meetings Scheduler, meetings scheduled with Productivity Tools are migrated so that the Cisco Webex Meetings Scheduler can edit them. However, users can't edit Webex meeting options such as the alternate host, join before host time, or audio type with Productivity Tools or the Cisco Webex Meetings Scheduler. The meeting start time, topic, and invitees can still be edited. As a workaround, we recommend scheduling meetings with the Cisco Webex Meetings Scheduler until this issue is resolved in a future update.


If a user scheduled a meeting on a host’s behalf using Productivity Tools, the meeting will be migrated into the host’s calendar, even if they do not install or sign in to Cisco Webex Meetings Scheduler. The scheduler or host will only be able to edit the meeting time, topic, and invitees using the Cisco Webex Meetings Scheduler or Productivity Tools.

Windows

For the Webex Productivity Tools integration with Microsoft Word, Excel, and PowerPoint, the buttons (Share This File > Share to Meeting) for files stored within Microsoft OneDrive or SharePoint is not supported. Sharing of files within meetings (Share Content > Share File) from OneDrive and SharePoint is supported.

Mac

Microsoft Outlook interface updates

In Microsoft Outlook for Mac, version 16.32, there are two UI interfaces. Users can enable or disable the new interface in the top right corner of the app window.

When New Outlook is enabled, Productivity Tools doesn't work as the Webex icon doesn't appear in the toolbar. The Microsoft Office 365 add-in also doesn’t work with this setting enabled. We recommend either not upgrading to the latest version of Microsoft Outlook for Mac, or keeping New Outlook disabled.

IBM Lotus Notes Support

The Cisco Webex Meetings integration to IBM Lotus Notes is part of the Cisco Webex Meetings desktop app. IBM Lotus Notes 8.5.X (32 bit, In Notes)/Domino Server 8.5, 8.5.1, 8.5.2, 8.5.3 and IBM Lotus Notes 9.0.X (32 bit)/Domino Server 9.0 are supported on Windows 7,8, 8.1, and 10. However, HCL Lotus Notes 10.X and above is not supported on Windows 7,8, 8.1, and 10.

Windows and Mac

The issues noted here affect all Webex services unless indicated otherwise.

Known interoperability issues between Windows and Mac

If a meeting series has exceptions that were scheduled or updated with the Windows version of the desktop app, Mac desktop app users can't update the meeting series.

Any meeting that is scheduled or updated with the Windows version of the desktop app can’t be canceled with the Mac version of the desktop app.

Lockdown

The desktop app doesn’t support to lockdown to a specific version once automatic upgrading is enabled.

Some customers may stay on a specific desktop app version by disabling the automatic upgrade option. However, Cisco may ask all desktop app users to upgrade to a minimum version if security compliance is necessary. This is an option that can be enabled by Cisco administrators.

Missing meeting links

The meeting link doesn't appear when opening an ICS invitation in a Windows text editor if the meeting was scheduled using the desktop app for Mac. This is a known issue acknowledged by Microsoft.

Windows

The issues noted here affect all Webex services unless indicated otherwise.

Address button on the desktop app panel

On the desktop app panel, the address button that allows you to select email addresses from your Microsoft Outlook address book isn't supported for the 64-bit version of Microsoft Outlook.

Cross-platform support

The desktop app available for the Microsoft Windows and Mac platforms only. Linux, Unix, and Solaris platforms aren't supported.

Customized email templates

A site administrator can customize Microsoft Lync links in the email templates Invitation to a Meeting in Progress_PR(Productivity Tools) and MC MeetingInfo For Attendee(Productivity Tools). The customized link is available for all users, so the link is invalid in invitations sent by users without Webex Video Conferencing. The site administrator should be aware of this and should add a reference when customizing the templates.

If a site administrator customizes host and attendee email templates to be the same, only attendee versions are sent to hosts and attendees.

%MeetingDate% isn't a supported parameter when scheduling Personal Room meetings from the desktop app.

Email invitation templates

  • Attendee version only (without host information)

  • Host and attendee email versions both sent out

If a site has video device-enabled meetings enabled, only one email invitation template is available. Attendee versions don't contain host information like the host key and access code.

The Mac version of the desktop app still uses a single email template. If a Mac user edits meetings that were created on the Webex Productivity Tools version WBS29.13 or later for Windows, a new template is generated. The content's based on the unified email template for hosts and attendees.

Sometimes, if a host forwards a Webex meeting invitation, an attendee email is sent instead.

Hosts can cancel an individual meeting that's an exception to a series and then edit that meeting series. Sometimes, the cancellation notice to attendees would actually contain updated information for the updated meeting series.

If a host creates a video device-enabled meeting series, changes an occurrence, and then updates the series to Webex meetings, the exception email changes to plain text.

The desktop app doesn't support the %MeetingDate% parameter in the invitation email body. The meeting date and time is handled by the calendar system.

IBM Lotus Notes integration

If a user has IBM Lotus Notes as the default email application opens the desktop app, enters an email address of an invitee, and then selects Meet Now, the meeting invitation that's sent to that invitee is empty and doesn't include any meeting information.

Adding HTML content in the Webex calendar invitation results in an error in IBM Lotus Notes version 8.5.

Lotus Notes can only display plain text content of iCalendar mail. Formatting that's done in HTML isn't supported.

The IBM Lotus Notes integration supports only limited rich text format features, such as hyperlinks and images.

It isn't possible to specify TSP telephony while scheduling a Webex meeting using the IBM Lotus Notes integration.

The IBM Lotus Notes integration requires a script to be inserted on the Domino database for each user. As a result, a user with editor privileges can't install the IBM Lotus Notes integration by just running an MSI available from the Support page. For an IBM Lotus Notes user with editor privileges, a Domino administrator must insert a Webex script into the IBM Lotus Notes database using the administrator tool.

Using the IBM Lotus Notes integration MSI file, only an IBM Lotus Notes user with manager or designer privileges can install the Integration.

If a single occurrence of a recurring Webex meeting is deleted or rescheduled, the meeting information isn't updated on the Webex site. The host's and attendees' IBM Lotus Notes calendars, however, display the meeting correctly.

When a recurring Webex meeting is scheduled to recur on alternate weeks in an IBM Lotus Notes calendar, the recurring meeting appears to be scheduled on the Webex service site as occurring weekly instead. The host's and attendees' IBM Lotus Notes calendars, however, display the meeting correctly.

Attendee registration can't be enabled for recurring Webex meetings scheduled using the IBM Lotus Notes integration.

If an email template has the Mute on Entry option enabled, users still hear a sound as attendees join the meeting.

If IBM Lotus Notes is using a different time zone compared to the one on the Webex site, a meeting that's scheduled with the IBM Lotus Notes integration don't appear correctly on the Webex site. On the host's and attendees' IBM Lotus Notes calendars, the time zones for the meeting still appears correctly.

Since Lotus Notes Integration doesn't use an email template, it isn't possible to configure the content of the host's and attendees' email invitations for Webex meetings that are scheduled using the IBM Lotus Notes integration.

Webex events that are scheduled with the IBM Lotus Notes integration has the following limitations:

  • Hosts can't assign a program.

  • Hosts can't assign multiple time zones to an event.

  • Hosts can't add event options like uploading a host or presenter's image, uploading event material, or UCF auto play options.

  • Hosts can't add presenters and panelists.

  • Hosts can't edit email template options for an event.

  • The option to join a meeting before the host isn’t available for recurring events.

Webex training sessions that are scheduled with the IBM Lotus Notes integration has the following limitations:

  • Hosts can't specify Listed for authorized users only.

  • Hosts can't reserve Hands-on Lab computers.

  • Hosts can't specify a registration close date or maximum number of registrations.

  • Hosts can't invite attendees as presenters into the training session.

  • Hosts can't assign attendee privileges.

  • Hosts can't edit the type of email messages to want to send when different training sessions happen.

  • Hosts can't tests and course material.

  • The option to join a meeting before the host isn't available for recurring training sessions.

If a user schedules a meeting using IBM Lotus Notes and then changes the meeting on their Webex site, the changes don't appear in IBM Lotus Notes.

If a user selects multiple meetings in IBM Lotus Notes and then deletes or moves them at the same time, those changes don't appear on their Webex site.

If a user schedules a new meeting in IBM Lotus Notes by copying an existing meeting, a new meeting isn't created on their Webex site. Instead, the same Webex meeting link is shown on the original and is copied with the meeting.

The attendee access code isn't displayed for conferences scheduled with the IBM Lotus Notes integration.

If a host edits an already-scheduled meeting and adds an attendee, the attendee information isn't posted to the Webex site site. As a result, for such attendees, this meeting doesn't appear in the My Meetings list.

Installation privilege errors

If a user manually installs the desktop app using an MSI package, the user must have Windows administration privileges to complete the installation.

If an IT user mass deploys the desktop app using MSI packages, the IT user must have Windows administration privileges to complete the installation.

Windows administration privileges are mandatory for automatically upgrading the desktop app.

Microsoft Outlook integration

The desktop app doesn't support having more than one version of Microsoft Outlook installed on the same device.

Attendee registration can't be enabled for recurring Webex meetings scheduled using the Microsoft Outlook integration.

If an email template has the Mute on Entry option enabled, users still hear a sound as attendees join the meeting.

If Microsoft Outlook is using a different time zone compared to the one on the Webex site, a meeting that's scheduled with the Microsoft Outlook integration don't appear correctly on the Webex site. On the host's and attendees' Microsoft Outlook calendars, the time zones for the meeting still appears correctly.

If a host schedules a meeting using Microsoft Outlook and then changes the meeting information on the Webex site, the changes don't appear in Microsoft Outlook.

If a user selects multiple meetings in Microsoft Outlook and deletes or moves them at the same time, the changes don't appear on the Webex site.

If a host schedules a new meeting in Microsoft Outlook by copying an existing meeting, a new meeting isn't created on the Webex site. Instead, the same link is shown on both the original and copied meeting.

The attendee access code isn't displayed for audio conferences scheduled using the Microsoft Outlook integration.

Importing a company address book into the Webex contacts isn't supported with the 64-bit version of Microsoft Outlook 2010.

You can't edit a meeting that's in progress.

The settings in the Scheduled Meetings tab aren't used- the default settings from the Webex site meeting template are used instead. Users can still leverage the settings that are set while scheduling the meeting in Microsoft Outlook.

Webex events that are scheduled with the Microsoft Outlook integration has the following limitations:

  • Hosts can't assign a program.

  • Hosts can't assign multiple time zones to an event.

  • Hosts can't add event options like uploading a host or presenter's image, uploading event material, or UCF auto play options.

  • Hosts can't add presenters and panelists.

  • Hosts can't edit email template options for an event.

  • The option to join a meeting before the host isn’t available for recurring events.

Webex training sessions that are scheduled with the Microsoft Outlook integration has the following limitations:

  • Hosts can't specify Listed for authorized users only.

  • Hosts can't reserve Hands-on Lab computers.

  • Hosts can't specify a registration close date or maximum number of registrations.

  • Hosts can't invite attendees as presenters into the training session.

  • Hosts can't assign attendee privileges.

  • Hosts can't edit the type of email messages to want to send when different training sessions happen.

  • Hosts can't tests and course material.

  • The option to join a meeting before the host isn't available for recurring training sessions.

Sometimes scheduled meeting information isn't included in the body of the email. This may be due to Microsoft Word settings that prevent web pages from being displayed in Microsoft Outlook for Windows. As a workaround, users on Microsoft Word can go to File > Options > Trust Center > Trust Center Setting > File Block Settings. Then, in the Open column, disable Web Pages.

Links generated by the desktop app and recording services

As part of our updates to improve security, Cisco is making changes to improve the management of cryptographic keys used to generate URLs used across Webex services. As a result, existing links have been updated. Some users may need to request new links.

Mass uninstallation

Mass deploying the desktop app requires the mass uninstallation of the previously installed version. For users who have multiple versions of the desktop app installed, please see the IT Administrator Guide for Mass Deployment of Webex Productivity Tools.

Microsoft Lync 2013

Microsoft Lync 2013 doesn't allow the desktop app to change a user's status.

Embedding the Webex menu item into the right-click menu also isn't supported.

Microsoft Outlook support

Although the Webex Meetings desktop app supports Microsoft Outlook 2016 as of version WBS29.13.70, the desktop app supports only one email invitation template for meetings. The email template that's supported is the attendee version that doesn't contain the host key and access code. Similar to the Mac experience, hosts can view their host key or access code by signing in to their Webex site when joining their meeting.

The desktop app for Microsoft Outlook 2013 and earlier supports two email invitation templates. One template is for attendees, and the other which includes the host key and access codes for hosts. The Mac version of the desktop app has always supported only one email template for all supported versions of Microsoft Outlook.


Users with Webex Productivity Tools with Microsoft Outlook 2016 should install the latest version of the desktop application. Changes in Microsoft Outlook 2016 cause the older version of Productivity Tools to send the host email invitation template to attendees.

Hosts can use Microsoft Outlook to edit meetings created with supported versions of Microsoft Outlook in Webex Productivity Tools. A new email template is generated based on the unified email template for hosts and attendees.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. However, the email invitation shows Webex information for the original meeting and edited meetings.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. The user editing the meeting receives a message that Webex Meetings can't locate the meeting because it's being edited. Selecting OK or Cancel updates the meeting with incorrect information.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2007. The user editing the meeting receives a message that they don't have the appropriate permissions to edit and save the meeting.

Hosts can create recurring Webex meetings in Microsoft Outlook 2016 for Mac, change one occurrence, and then cancel the Webex portion of the meeting. However, the appointment can't be canceled in Microsoft Outlook 2016 for Windows if the calendars are in different time zones. Even if the email body is updated, the appointment can't be canceled.

Recurring meetings

If a user cancels a Webex recurring meeting in Microsoft Outlook that has an exception, and the user is using the Microsoft Exchange server version 2013 or later, the Webex information isn't completely removed from the cancelation email notification.

In Microsoft Outlook 2013 (15.0.4823.1000), updating a meeting series overwrites the email message of exception meetings.

Meeting times aren't displayed correctly in email invitations for a meeting series. This is because the %MeetingDate% parameter isn't supported. We recommend that you don't add this parameter to display the meeting date when customizing email templates.

Silent installation or mass deployment of the desktop app

If an administrator performs a silent installation or mass deployment of the desktop app, users can't edit any of the settings on the Tools panel. Performing a silent installation may cause some settings on the desktop app page of Webex Site Administration to be ignored.

For administrators who mass installed the desktop app and are trying to upgrade to a new version, we recommend that you perform a silent uninstallation first.

In some silent upgrade cases, the version of the desktop app on the control panel is reflected incorrectly. This problem doesn't impact features and should be fixed in a future update.

For more information about deploying the desktop app, see the IT Administrator Guide for Mass Deployment of Webex Productivity Tools.

Video call-in port setting for video device-enabled meetings

If a site administrator reduces the default video call-in number from ten to five, all scheduled video device-enabled meetings can still be updated.

Video device-enabled (Webex-enabled TelePresence) integration issues

For video device-enabled meetings, email templates are only supported in English only on Windows and Mac devices.

  • Scheduling video device-enabled meetings

    If an administrator turned on the TelePresence integration for a Webex site, users can schedule video device-enabled (Webex-enabled TelePresence) meetings with Microsoft Outlook for Windows. This option is only available for sites with TelePresence integration turned on. Once this option has been turned on, users may have to upgrade their desktop apps and restart Microsoft Outlook. The Allow people to join using Webex option in the Meeting Options dialog for video device-enabled meetings doesn't stay enabled if it was for a previous meeting. To allow users to join using Webex, this option must be enabled every meeting.

    Hosts who have video device-enabled meetings enabled but don't have the Webex setting in their Cisco TelePresence Management Suite (Cisco TMS) can't schedule TelePresence-only meetings with the desktop app.

  • Adding resources

    When users schedule a Webex meeting with Microsoft Outlook, if they add TelePresence rooms or extra video call-in participants, a Webex-enabled TelePresence meeting is automatically scheduled. If they don't include these resources, the meeting is a Webex-only meeting. Status indicators show that a TelePresence meeting was booked if these resources were added.

  • Email invitation templates for CMR Hybrid meetings

    CMR Hybrid meetings still only support one email invitation template, which is the attendee version that doesn't contain the host key and access codes. To view the host key and host access code, video device-enabled meeting hosts must sign in to their Webex site to see the Meeting Details Page. They can also sign in to their site on through the desktop app to view the information in their Advanced Webex Settings dialog.

    The desktop app for video device-enabled meetings doesn't support sending HTML email invitations. The email invitations are only available in plain text format.

    The desktop app email templates for video device-enabled meetings don't contain the %ConfCallParticipant% variable, so audio-only callers can join the audio conference from a mobile device. Instead, mobile device users can select the Join Webex meeting link or URL in their invitation, and join the meeting using the Webex Meetings mobile app. Users can also pick up or manually dial the call-in number and meeting ID number or access code in the invitation from their mobile device.

  • Time zone and Daylight Savings Time

    The time zone for a Webex site must match the time zone for the Cisco TMS; otherwise the meeting time isn't synchronized. When Daylight Savings Time changes are made between a Webex site and the Cisco TMS, it's possible that meetings might be an hour off schedule. If this happens, rescheduling is required. If this problem occurs with a meeting series where some instances occur before Daylight Savings Times begins and some occur after, we recommended that hosts create two meeting series: one meeting series that ends before the Daylight Savings Time begins and a second meeting series that starts after Daylight Savings Time begins.

  • Cisco Unified MeetingPlace Audio

    The desktop app that supports the Webex integration with Cisco TelePresence doesn't support Cisco Unified MeetingPlace Audio. Users with Cisco Unified MeetingPlace and the desktop app installed who want to schedule a combined Webex and TelePresence meeting with Webex or TSP audio, must use the Smart Scheduler in the Cisco TMS. A user can't have two versions of the desktop app installed at the same time.

  • Telephony service provider (TSP) audio

    For some TSP audio accounts, if a host with a TSP account schedules two adjacent video device-enabled or Webex video conferencing meetings, with the second one scheduled to start immediately after the first one ends, and if the TelePresence scheduling system automatically extends the first meeting past the scheduled end, the second meeting will end automatically because the host because the same TSP audio account can’t be used for both meetings at the same time. To work around this problem, hosts can set up two different TSP audio accounts with different host access codes, and use one account for the first meeting and the other account for the second meeting. Another option is the administrator to turn off the option for the TelePresence systems to automatically extend the meeting.

  • Support for Microsoft Office 365, Microsoft Outlook 2010, and Windows 8 and 8.1

    Webex sites that have the video device-enabled meetings enabled may require the latest versions of the Cisco TMS and Cisco TMSXE to support Microsoft Office 365, Microsoft Outlook 2010, or Windows 8 and 8.1. For more information, go to Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide > Cisco Webex Features and Important Notes > Prerequisites on the Cisco TelePresence Management Suite (TMS) Configuration Guides page.

  • Instant Meetings and Personal Room meetings

    Users can't start instant video device-enabled meetings; only schedule them. When users start instant meetings, they are Webex-only meetings and don't include TelePresence integration.

    Instant meetings that started with the Meet Now command are held in Personal Rooms by default. This option can be changed in a user's Preferences. In order to have a Personal Room meeting that users can join from a video conferencing system or app, the Webex site and host account must be enabled for it.

    A workaround for an instant meeting that uses both Webex and TelePresence is to start a meeting from a TelePresence system and then the named host has selects Instant Webex Meeting on the meeting detail page to generate a URL that allows external participants to join the TelePresence meeting from a desktop or mobile app.

  • Scheduling Webex-only or TelePresence-only meetings

    Webex sites that have video device-enabled meetings enabled require Cisco TMSXE in order for users to schedule Webex-only or TelePresence-only meetings with the desktop app.

  • Maximum of two simultaneous meetings per host

    Webex sites that have video device-enabled meetings enabled can't have a host have more than two meetings started at the same time.

  • Personal and audio conferences

    Although a video device-enabled meeting user can schedule a Personal Conference meeting for sites that have Webex Audio or an audio conference for sites that have TSP audio, it's a Webex-only meeting type and doesn't include video device-enabled meetings.

  • No branding or customizing of video device-enabled meeting features

    Site administrators can't change the branding for the video device-enabled meeting Options panel, hide info, and can't limit the number of video call-in participants that users can enter.

Webex One-Click, instant messenger, and Microsoft Office integrations

If users use personalized join links to automatically populate attendee names and email addresses on the Join Meeting page, some email gateways may truncate the links. Attendees can still click the links, but the links don't automatically allow them to join the meeting. Instead, they must enter their name and email address before joining the meeting. There’s no current known workarounds.

If the instant messenger integration was installed using a silent installer, users must restart their instant messenger to see the desktop app integration features.

Webex site URL change

If a user signs in to the desktop app with a new Webex site URL after the site was renamed, they can't edit the meetings that were scheduled with the previous URL.

Mac

The issues noted here affect all Webex services unless indicated otherwise.

Installation privilege errors

Users manually installing the desktop app using a DMG package must have iOS administration privileges.

iOS administration privileges are mandatory to automatically upgrade the desktop app.

Mass deployment of the desktop app isn't supported on the Mac.

Microsoft Outlook support

The desktop app for Mac doesn't support Microsoft Insider preview versions.

Hosts can create recurring Webex meetings in Microsoft Outlook 2016 for Mac, change one occurrence, and then cancel the Webex portion of the meeting. However, the appointment can't be canceled in Microsoft Outlook 2016 for Windows if the calendars are in different time zones. Even if the email body is updated, the appointment can't be canceled.

The desktop app support having more than one version of Microsoft Outlook installed on the same computer.

Meetings from Webex Meetings server aren't supported.

Some known issues may occur with the desktop app using Microsoft Exchange Server 2007 and Microsoft Outlook for Mac.

If a user is updating the Webex meeting on the Outlook calendar view instead of the editing window of the occurrence, some issues occur because some Microsoft Outlook behaviors aren't under the desktop app's control in the calendar view.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. However, the email invitation shows Webex information for the original meeting and edited meetings.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. The user editing the meeting receives a message that Webex Meetings can't locate the meeting because it's being edited. Selecting OK or Cancel updates the meeting with incorrect information.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2007. The user editing the meeting receives a message that they don't have the appropriate permissions to edit and save the meeting.

Meeting times aren't displayed correctly in email invitations for a meeting series. This is because the %MeetingDate% parameter isn't supported. We recommend that hosts don't add this parameter to display the meeting date when customizing email templates.

In Microsoft Outlook 2016, an exception meeting opens when a user right-clicks an exception and selects Open > Open Series.

Cisco TelePresence Management Suite (TMS) sign in window

If the TMS sign in window doesn't appear after upgrading to the latest version of the desktop app, restart the device.

Default meeting templates

If the First attendee to join will be presenter option is enabled in Webex Site Administration, this option is enabled by default in a Webex site's meeting scheduler. The setting is also be enabled in the default meeting template that's used by the desktop app for scheduling Webex meetings. Custom meeting templates that have been created by users aren't be impacted. If a host schedules meetings with custom templates and wants the first attendee to become the presenter, the host must manually enable the setting.

IBM Lotus Notes integration

IBM Lotus Notes isn't supported in the desktop app.

Sign in and sign out processes

Sometimes, the desktop app might redirect a user to their Webex site to sign in again and change their password.

The desktop app supports enterprise single sign-on users; however, because there’s no single sign-out service from the enterprise site, users can only switch their account when the single sign-on token has expired.

Before single sign-on users first sign in to the desktop app, they must go to the Webex site to accept the site certification manually with Safari.

Video device-enabled meeting issues

For video device-enabled meetings, email templates are supported in English only.

The same issues that exist for the Webex-enabled TelePresence integration (CMR Hybrid) for the Windows version of the Desktop Application also apply to the Mac version.

If a host using the desktop app schedules a video device-enabled meeting and schedules a TelePresence room, and then the host drags the meeting to a new start time on the calendar or add a new Telepresence room, there may be a problem if the TelePresence room is already booked. As a result, the Cisco TelePresence Management Suite server can't update the meeting because of the conflict. In addition, the Webex meeting can’t be moved back to the original start time.

Webex Site Administration options from the desktop app

In the Site Administration, on the desktop app, the options under Installation Options and Integrations apply only to the Windows version of the desktop app, not the Mac version. In addition, the only integration that's available for the Mac version of the desktop app is the integration to Microsoft Outlook.