XCLN: Unable to View or Configure Multipoint Control Unit in a Site Without a Conference Management Service (276477)
The information in this article applies to:
- Microsoft Exchange 2000 Conferencing Server
This article was previously published under Q276477 SYMPTOMS
Administrators may not be able to view or configure a Multipoint Control Unit (MCU) that is installed in a Windows 2000 site in which the Conference Management Service (CMS) is not installed.
CAUSE
During installation, an MCU registers itself with the Conference Management Service for that server's Microsoft Windows 2000 site. This problem can occur if a CMS is not installed in the site; during installation, the MCU is installed in an orphaned state. Therefore, any Windows 2000 or Exchange 2000 sites that contain a CMS cannot view or configure the MCU.
WORKAROUND
To work around this problem and provide the conferencing administrator the ability to view and configure an MCU installed in a site in which there is no Conference Management Service, use one of the following methods.
Method 1: Graphical User Interface
To use the graphical user interface (GUI):
- Remove the MCU from the MCU-only server.
- Change the Subnet container for the MCU-only server in the Active Directory Sites and Services Microsoft Management Console (MMC) snap-in from the current site to the site that contains the CMS:
- Start the Active Directory Sites and Services MMC snap-in; click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
- Click to expand the Sites container, and then locate the Subnets container.
- Click the subnet that the MCU-only server resides in, right-click the subnet, and then click Properties.
- Under Site, click the list, change to the site that contains the CMS, and then click OK.
- On the MCU-only server, run the nltest /dsgetsite command at the command line to ensure that the server returns the CMS site.
- Re-install the MCU only on the server.
- Change the Subnet container for the MCU-only server from the CMS site back to the previously configured site name.
After you complete these steps, the T.120 MCU/H.323 Bridge is displayed in the results pane when you select the Data Conference Provider object. NOTE: The preceding steps might cause replication traffic because these steps change the server's site designation from its original site to another site.
Method 2: Command Line
To use a command-line command:
- Click Start, click Run, and then type cmd.
- Run the following command:
msiexec /i "Source_Path\MICROSOFT EXCHANGE 2000 CONFERENCING SERVER.MSI" EXTENDEDSITE=The_Conference_Site_Name
Note the following:
- This command is case-sensitive.
- This command sets the site that the remote MCU is installed in.
- The user interface (UI) is still displayed; you need to ensure that the Custom option is selected and only the MCU is being installed. Make sure that all of the other options are clear (not selected).
If you want to perform an unattended installation, the following command displays only a process dialog box:
msiexec /i "Source_Path\MICROSOFT EXCHANGE 2000 CONFERENCING SERVER.MSI" EXTENDEDSITE=The_Conference_Site_Name PIDKEY=CDKEY_NO_SPACES_OR_DASHES ADDLOCAL=ecs_mcu_feature /qb NOTE: If you want to walk through the dialog box options manually, remove the /qb switch. You need to select custom during the installation process.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Conferencing Server.
Microsoft is researching this problem and will post more information in this article when the information becomes available.
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kbbug kbpending KB276477 |
---|
|