Configure Meeting Workspace options in Outlook 2007
Updated: April 9, 2009
Applies To: Office Resource Kit
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
In this article:
Using policies to define server lists and other user options
Configuring Meeting Workspace integration when using a POP Server
Viewing error message logs
A Meeting Workspace is a Web site for centralizing meeting information and materials. Before the meeting, you use a workspace to publish the agenda, attendee list, and documents you plan to discuss. After the meeting, you use the workspace to publish the meeting results and track tasks. You send a Microsoft Outlook meeting request to invite people to the meeting. In the message, you include a hyperlink that points to the workspace where invitees can learn details and see the meeting materials.
Note
This topic is for Outlook administrators.
You can configure a number of options to set up and manage your Meeting Workspace deployment with Microsoft Office Outlook 2007. You can manage how users choose Meeting Workspace servers and other options when they create workspaces to include in Outlook meeting requests. You can configure Meeting Workspaces when you use a POP server as your messaging server. You can also view Meeting Workspace error messages in a log file to troubleshoot issues with Meeting Workspace configurations.
Note
By default, a Microsoft Exchange server must be configured as your messaging server when you use Meeting Workspaces with Outlook.
A Meeting Workspace is a special type of Microsoft Windows SharePoint Services Web site created under a top-level SharePoint site. Help for the Meeting Workspace and general SharePoint Help is available from the workspace.
Note
If Windows SharePoint Services is installed on your network, users within your company can invite other users who share the same Microsoft Windows NT forest to a workspace. For more information about domains and forests, see information on Active Directory in Windows Help.
Using policies to define server lists and other user options
You can configure options when you use policies to enforce Meeting Workspace settings for groups of users in your organization. For example, you can define the list of Meeting Workspace servers that users can choose. You can disable Meeting Workspace access if you do not want users to use this feature.
In a server list, you can specify how to prepopulate the drop-down lists that users see when they work with Meeting Workspaces in Outlook. You access the Meeting Workspace feature by clicking Meeting Workspace on an Outlook meeting request. On the Meeting Workspace task pane, click Change settings. On the next Meeting Workspace task pane, choose a server from the Select a location: drop-down list.
On the same pane, you can create a new workspace by choosing a template language and a template type from drop-down lists. You can also link to an existing workspace by choosing a workspace from the Select a workspace drop-down list.
You use Group Policy to configure the lists and settings you want for Meeting Workspace. When you load the Microsoft Office 12 system ADM files into Group Policy, policies related to Meeting Workspace are located under User Configuration\Administrative Templates\Microsoft Office Outlook 2007\Meeting Workspace. This is also the location where you create a new policy to list Meeting Workspace servers and other items in the Meeting Workspace task pane drop-down lists.
Configuring server list behavior for meeting organizers
You can configure how Meeting Workspace server lists are presented to meeting organizers in Outlook. For example, server lists can show a most recently used (MRU) list, and the list of servers and templates can be repopulated from the default list each time a workspace is created. You can also help to prevent Meeting Workspace access by disabling the Meeting Workspace option for Outlook meeting requests.
When you specify the list of servers, you can ensure that the server list is repopulated with default servers and default templates. You can also help to control whether users can access servers other than those that are specified. You remove the Meeting Workspace button from Outlook meeting requests with the Disable Meeting Workspace button policy. Double-click the policy to open the Properties dialog and select Enabled. Then select the Check to disable Meeting Workspace button.
You configure options for the Meeting Workspace. Select a location drop-down list with the Disable user entries to server list policy. Double-click the policy to open the Properties dialog and select Enabled. In the Check to disable users from adding entries to server list drop-down list, select one of the following:
Publish default, allow others—You specify a list of default servers that appears in the drop-down list. Users can use the Other workspace server pop-out dialog to specify other servers. In addition, other Windows SharePoint Services sites and document workspace sites that users visit appear on the server list. No user MRU list is created with this setting.
Publish default, disallow others—The default server list you specify is locked down for users. Users cannot access the Other workspace server pop-out dialog to specify servers that are not on the provided list. With this setting, no user MRU list is created.
Specifying a list of servers and default templates
You can configure the list of servers and corresponding Meeting Workspace templates that appear in a drop-down list when a user clicks Meeting Workspace in a meeting request. A single registry key or policy stores all the Meeting Workspace server list entries.
Note
You can use the Office Customization Tool (OCT) to deploy the registry key that specifies the list of Meeting Workspace servers to your users. For more information about using the OCT, see Configure user settings for the 2007 Office system. For details on deploying registry keys by using the OCT, see Office Customization Tool in the 2007 Office system.
The server list policy has a specific format that must be followed. Server names are separated from each other by vertical pipes (|) without carriage returns (CRs) or line feeds (LFs). There are six fields per record, as described below. There are from one to five records in the policy. This is an MRU list. The first server record (for example, Server1) is the most recently used server and the 5th server record (for example, Server5) is the oldest server reference.
The OrganizerName field is ignored when you use a policy to specify the server list. The other fields should always have valid content.
Note
You can examine the following registry key to see the current server list settings on any computer that has been used to create Meeting Workspaces:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Meetings\Profile\MRUInternal
You specify the server list for the Meeting Workspace with the Default servers and data for Meeting Workspaces policy. Because the policy string is complex, you should first type the entries into a text editor (such as Notepad), and then paste the entire string into the policy. When you create the server list string following the syntax described below, double-click the policy to open the Properties dialog and select Enabled. In the Default field, paste the server list string you have created.
The syntax for the server list string is outlined below:
http://Server1 |Friendly name for server 1|TemplateLCID|TemplateID|TemplateName|OrganizerName|http://Server2 |Friendly name for server 2|TemplateLCID|TemplateID|TemplateName|OrganizerName|http://Server3 |Friendly name for server|
The list continues with the same structure, with an entry for each server you want to include.
There are six fields in each record:
Field 1: Server URL
Field 2: Server friendly name
Field 3: TemplateLCID
Field 4: TemplateID
Field 5: TemplateName
Field 6: OrganizerName
Each field is separated from the next field with a vertical pipe (|). Each complete record is separated from the next record with a vertical pipe (|) after the last field (OrganizerName). There is a total of six vertical pipes in each record included in the setting.
For the field TemplateLCID, specify a decimal value that identifies the language for the template, such as 1033 (representing English).
For the other template fields, you can choose a template name and the corresponding TemplateID from the following table of default templates.
| TemplateName | TemplateID |
|---|---|
Basic Meeting Workspace |
Mps#0 |
Blank Meeting Workspace |
Mps#1 |
Decision Meeting Workspace |
Mps#2 |
Social Meeting Workspace |
Mps#3 |
Multipage Meeting Workspace |
Mps#4 |
Note
You cannot use a custom template for Outlook Meeting Workspaces with Windows SharePoint Services.
The following is an example of a server list entry (OrganizerName is blank):
http://server1/sites/design_team|The Juniper Project|1033|MPS#4|Multipage Meeting
Configuring Meeting Workspace integration when using a POP Server
You can configure Meeting Workspace integration for Outlook when you use a POP server as your messaging server. The POP server configuration enables Outlook to transport and persist Meeting Workspace properties for meeting organizers and meeting attendees who use a POP server.
Note
The use of Outlook delegates with Meeting Workspace is not supported in POP server configurations.
This section provides a pointer to reference information that can help you configure your POP server to use TNEF. This section also includes steps that meeting organizers must take to help ensure that meeting requests are sent by using rich transport.
The following is required to use Meeting Workspaces with a POP server:
The POP server must be configured to support Transport-Neutral Encapsulation Format (TNEF).
Outlook meeting requests must be sent by using rich transport.
The following scenario describes the user experience when Meeting Workspaces are included in meeting requests and Outlook is used with a POP server.
The meeting organizer initiates a meeting request in Outlook and creates or links to a Meeting Workspace in the request.
The attendee receives the meeting request and sees a Meeting Workspace table in the message body. The correct format of the table should include a link to the Meeting Workspace.
The Meeting Workspace properties are persisted to the attendee's calendar.
The attendee's response is sent to the Meeting Workspace server.
More about TNEF support
TNEF is a format for converting a set of MAPI properties—a MAPI message—into a serial data stream. The TNEF functions are primarily used by transport providers that need to encode MAPI message properties for transmission through a messaging system that does not directly support those properties. For example, an SMTP-based transport uses TNEF to encode properties, such as PR_SENT_REPRESENTING, which do not have direct representations in the structure of an SMTP message.
For more information about using TNEF, see the Transport-Neutral Encapsulation Format (TNEF) appendix in the Messaging API SDK on TechNet.
TNEF must be enabled for Meeting Workspaces to work properly in Outlook meeting requests when a POP server is used as the messaging server. The Meeting Workspace properties are stored in a MAPI property associated with the meeting request form. TNEF is required to transport the properties from the meeting organizer to the meeting attendee. When the meeting attendee receives the Meeting Workspace properties (after the properties are transported by using TNEF), Outlook stores the properties in the attendee's client meeting request.
Ensuring that rich transport is used
Meeting organizers who want to use Meeting Workspace with POP messaging servers must ensure that rich transport—rather than plain text transport—is used to send the meeting request to recipients. Rich transport means ensuring that Rich Text Format attributes and iCalendar information are included together in the transport. This ensures that the Meeting Workspace properties attached to the meeting request persist in the e-mail transport from organizer to attendee. The meeting organizer must take the following steps to help ensure that rich transport is used for the meeting request:
Use Rich Text Format (RTF) when the meeting request is sent.
Do not attach an iCalendar (iCal) to the meeting request. (The iCalendar format is a common format for Internet calendars.)
These are only requirements if POP is the messaging server. If the organizer is using an Exchange server, these options are not needed.
Set Rich Text Format
Rich Text Format for meeting requests in Outlook can be set per meeting request or as the default for all Outlook messages, including meeting requests.
To set Rich Text Format for one meeting request
In the meeting request, in the To box, double-click the user name.
In the E-mail properties dialog, under Internet format, click Send using Outlook Rich Text format.
You can also configure Outlook to use RTF for all Internet messages, including meeting requests.
To set Rich Text Format as the default for all Internet messages
In Outlook, on the Tools menu, click Tools and click the Mail format tab.
Click Internet Format.
In the drop-down list in the Outlook Rich Text options section, select Send using Outlook Rich Text format.
Do not send an iCalendar attachment
To specify that an iCalendar attachment is not sent with a meeting request, clear Send as iCalendar on the Tools menu in the individual meeting request. This forces the iCalendar properties to be transported in the MIME message header. This option is not available if Outlook is used with Exchange server.
Viewing error message logs
Some Meeting Workspace errors are suppressed by default to help avoid user confusion. However, Meeting Workspace errors are written to the Windows Event Log, which can help you find problems when you are troubleshooting.
Meeting Workspace users are alerted with an error message if there is a problem when they create a workspace or if a problem with the workspace arises later (for example, if a meeting workspace server fails). If problems occur separately from the process of initiating a meeting and creating a workspace, users might not understand what went wrong and what, if anything, they can do about the problem. Because these errors occur asynchronously, in some cases it might not be obvious that the error was triggered by a meeting update action.
When there are steps users can take to fix the problem, error messages about the problem are always shown to users. Error messages that might confuse users are suppressed by default.
If you need to debug Meeting Workspace issues, it might be helpful to examine the error content in the Windows event log. You can view the log files by using the Windows Event Viewer. To open Event Viewer, in Control Panel, double-click Administrative Tools and double-click Event Viewer. You can see logging information related to Outlook by clicking Application Log in the left pane.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Office Resource Kit information.