This article was previously published under Q276491
This article has been archived. It is offered "as is" and will no longer be updated.
When you install Exchange 2000 Conferencing Server Conference Management Service (CMS) and the T.120 MCU component in one site, and then install the T.120 MCU component on a server in another site that does not contain an active CMS, the MCU server object that was installed in the second site is not displayed in the Results pane when you click the Data Conferencing Provider node in the Conferencing Manager snap-in.
This issue can occur if the server installation in the second site (the "MCU only" server installation) does not register itself with the CMS in the first site.
To resolve this issue, run the following command to install the MCU in the second site, where Source_path is the location of the Microsoft Exchange 2000 Conferencing Server.msi file, and Site_name is the name of the conference site:
NOTE: The msiexec command is case sensitive; when you run msiexec, the site in which the remote MCU is installed is set. Verify that only the MCU is being installed and that all other options have been cleared.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.
If you are performing an unattended installation, use the following syntax, where Source_path is the location of the Exchange 2000 Conferencing Server.msi file, and Site_name is the name of the conference site, and cdkey is your Exchange 2000 Conferencing Server CD-ROM key without spaces or hyphens: