• Article

Changing the UNC Paths Where Meeting Content or Metadata Is Stored

Topic Last Modified: 2009-05-22

The Web Conferencing Server in Office Communications Server 2007 R2 saves any content created in a conference to a folder. Along with the content, the Web Conferencing Server also saves metadata information to a folder. The metadata information describes the meeting content such as upload time and the user who uploaded the content. Both the meeting content and the metadata are encrypted.

You specify the location for the meeting content folder and the meeting metadata folder during setup. You cannot change them by using the Office Communications Server 2007 R2 Administrative Tools. However, you can manually change their locations after you deploy Office Communications Server by performing the following steps:

  1. Stop the Office Communications Server Web Conferencing service.
  2. Create and configure the file folders and file shares for meeting content and metadata.
  3. Change WMI settings for meeting content and meeting content metadata folders.
  4. Change the Internet Information Services (IIS) virtual directory to the presentation folder.
  5. Restart the Office Communications Server Web Conferencing service.

Note

You must stop the Office Communications Server Web Conferencing service before performing the following steps.

Step 1: Stop the Office Communications Server Web Conferencing Service

Stop the Office Communications Server Web Conferencing service on your Standard Edition server or on each server in your Enterprise pool that is running the service. For details, see Starting and Stopping Services.

Step 2: Create and Configure File Folders and Shared Folders for Meeting Content and Metadata

If the folder does not exist, create a new folder for storing meeting content. For a Standard Edition deployment, verify that Setup created a file folder at <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Data MCU Web\Web. For an Enterprise Edition deployment, create and configure a shared folder for storing meeting content on a dedicated file server and record the folder’s Universal Naming Convention (UNC) path (for example, \\Contoso\CommunicationsServer\Content). Configuration includes setting the correct access control (that is, permissions) on the folders or file shares. For details, see Storage Requirements in the Planning and Architecture documentation.

To configure the file folder or shared folder for meeting content or metadata

  1. Set correct permissions for the meeting content folder as follows:

    • For a Standard Edition server, right-click the file folder, click Properties, click the Security tab, and then verify that permissions are configured as follows:
      RTC Component Local Group: Read/Write
      Users (Local Group): Read-Only
    • For an Enterprise pool, right-click the shared folder, click Properties, click the Security tab, and then ensure that permissions are configured as follows:
      RTCUniversalGuestAccessGroup: Read, Read and Execute, List Folder Contents
      RTCComponentUniversalServices: Read, Read and Execute, Modify, List Folder Contents, Write

  2. If the folder does not exist, create a new folder for storing meeting content metadata as follows:

    • For a Standard Edition deployment, verify that Setup created a folder for storing meeting content metadata at <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Data MCU Web\Non-Web.
    • For an Enterprise Edition deployment, create and configure a shared folder for storing meeting content on a dedicated file server and record the folder’s UNC path (for example: \\Contoso\CommunicationsServer\Metadata).

  3. Set correct permissions for the meeting content metadata folder:

    • For a Standard Edition server, right-click the file folder, click Properties, click the Security tab, and then ensure that permissions are configured as follows:
      RTC Component Local Group: Read/Write
    • For an Enterprise pool, right-click the file folder, click Properties, click the Security tab, and then ensure that permissions are configured as follows:
      RTCComponentUniversalServices: Read, Read and Execute, Modify, List Folder Contents, Write

Step 3: Change WMI Settings for Meeting Content and Meeting Content and Metadata Folders

You can change WMI settings to point to a new UNC path.

To change WMI settings for meeting content and meeting content metadata folders

  1. Log on to a server with Office Communications Server 2007 R2 Administrative Tools installed, as a member of the RTCComponentUniversalServices group or an account with equivalent user rights.

  2. At the command prompt, type wbemtest.exe.

  3. In the Windows Management Instrumentation Tester dialog box, click Connect.

  4. In the Connect dialog box, in Namespace, type root\cimv2, and then click Connect.

  5. In the Windows Management Instrumentation Tester dialog box, click Query.

  6. In the Query dialog box, type the query, for example:

    Select * from MSFT_SIPDataMCUCapabilitySetting where Backend = (local)\\rtc

    Note

    The example shown in this procedure is for Standard Edition server. For an Enterprise pool, replace "(Local)\RTC" with "BackendServerName\DatabaseInstanceName." If you do not know the name of the SQL back-end server and database instance for the pool, you can see it in the details pane of Office Communications Server 2007 R2. In Office Communications Server 2007 R2, in the console tree, click the name of the pool. In the details pane, click the Database tab. The value of Database Instance Name indicates the name of the database instance.

  7. In the Query dialog box, click Apply.

  8. In the Query Result dialog box, double-click MSFT_SIPDataMCUCapabilitySetting.

  9. In the Object editor dialog box, do the following:

    • To change the location of meeting content, double-click the MeetingPresentationContentLocation property. In the Property Editor dialog box, change the value to a new UNC path, and then click Save Property.
    • To change the location of the meeting content metadata folder, double-click the Meeting MetadataLocation property. In the Property Editor dialog box, change the value to a new UNC path, and then click Save Property.

  10. In the Property Editor dialog box, click Save Property, and then close the WBEMTEST program.

Step 4: Change the IIS Virtual Directory to the Presentation Folder

You can change IIS virtual directory settings to point to a new UNC path.

To change the IIS virtual directory to the presentation folder

  1. Log on to a server with Web Components installed as a member of the Administrators group or a group with equivalent user rights.

  2. Open IIS Manager: Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  3. Expand the computer name, expand Web Sites, expand Default Web Site, expand Etc, expand Place, expand Null, right-click FileTree, and then click Properties.

  4. On the Virtual Directory tab, do one of the following:

    • If the content for this resource is on the local computer, click A directory located on this computer, and then type the path to the meeting content folder that you created in the Local path box.
    • If the content for this resource is not on the local computer, click A share located on another computer, and then type the path to the meeting content folder that you created in the Network directory box.

    Note

    If the directory that you specify is a network share, you must ensure that the account configured for IIS anonymous access has Read access to the network share. You can use a user account that belongs to the RTCUniversalGuestAccessGroup for this purpose. To verify what account is configured for IIS anonymous access, in the FileTree Properties dialog box, on the Directory Security tab, under Authentication and access control, click Edit.

Step 5: Restart the Office Communications Server Web Conferencing Service

Restart the Office Communications Server Web Conferencing service on your Standard Edition server or on each server in your Enterprise pool that is running the service.