Article ID: 980954 - View products that this article applies to.
When a user creates an ad hoc or Meet Now Live Meeting by using the Microsoft Conferencing Add-in for Microsoft Office Outlook, the organizer can share slides. However, attendees cannot share slides. This problem does not occur if the user initializes an ad hoc Live Meeting by using Microsoft Office Communicator 2007.
Note Ad hoc meetings are meetings for instant collaboration and are sometimes called Meet Now meetings.
When a user initializes an ad hoc Live Meeting by using Microsoft Conferencing Add-in for Microsoft Office Outlook, the default type of behavior for the meeting is set to Presentation conferencing type. A presentation meeting does not allow attendees to share slides by default. When a user initializes an ad hoc Live Meeting by using Office Communicator 2007, the default type of behavior for the meeting is set to Collaboration conferencing type. A collaboration meeting allows attendees to share slides by default.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756To resolve this problem, install the following update:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
980924After you install this update, you must create a registry key. To do this, follow these steps:
(https://support.microsoft.com/kb/980924/ )Description of the update for the Live Meeting Conferencing Add-in for Outlook: April 2010
To work around this problem, you can change the permissions of attendees by selecting (CTRL+N) after the meeting has started.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 980954 - Last Review: August 23, 2011 - Revision: 3.0