When using the Exchange Management Console from a Hub-Transport server on Exchange 2007, you will get the following errors when you try to manage a remote Client Access Server.
--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
The following error(s) were reported while loading topology information:
Get-ActiveSyncVirtualDirectory
Failed
Error:
An error occurred while trying to access IIS (Internet Information Service)
metabase. Make sure the Internet Information Service Manager component is installed
and configured properly.
Unknown error (0x80005000)
Get-OabVirtualDirectory
Failed
Error:
An error occurred while trying to access IIS (Internet Information Service)
metabase. Make sure the Internet Information Service Manager component is installed
and configured properly.
Unknown error (0x80005000)
Get-OWAVirtualDirectory
Failed
Error:
An error occurred while trying to access IIS (Internet Information Service)
metabase. Make sure the Internet Information Service Manager component is installed
and configured properly.
Unknown error (0x80005000)
====
This is because you don’t have the IIS management binaries installed on the HUB server. These binaries are not needed for the management console to work on the HUB server itself, but they are required for doing remote administration on a CAS server.
Open the Command prompt on the server and run the following commands to be run on Hub-Transport server
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
Ref:
How to install the Windows Server 2008 operating system prerequisites for Client Access servers
(http://technet.microsoft.com/en-us/library/bb691354(EXCHG.80).aspx)
Reboot the Hub Transport server and open the Exchange Management Console. You should now be able to access the Client Access Server without any issues
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See
Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.