This is a new installation of Exchange 2007 SP1 with all updates. We are in the process of transitioning from Exchange 2003 to Exch2007. To begin with we had all roles installed on the new Exchange 2007 server but then learned that there were issues with OWA and Exch2007 regarding public folders. I was told that I needed to move the CAS role to a different server. The install goes fine but once it finishes I get the error below. Can someone please shed some light on what causes this error and how to correct it. Thanks, Get-OWAVirtualDirectoryFailedError:Unable to create Internet Information Services (IIS) directory entry. Error message is: Class not registered. HResult = -2147221164. Class not registered. Directory Path: IIS://mailboxroleserver.domain.local/W3SVC/1/ROOT/Exchange Detail:server name: mailboxserver.domain.locallocal machine name: CLIENTACCESSROLESERVERNAMElocal machine fqdn: clientaccessroleserver.domain.local Class not registered

Is IIS already installed on the server you are trying to add the CAS role to?

Yes. I think I just figured out what the problem was. I had IIS installed on the server that I was installing CAS to, but apparently IIS needs to be installed on the the other server also. That's the server with the other roles. When I remove the CAS role from that server I also uninstalled IIS thinking that it wouldn't be needed. I guess that what I get for thinking I still don't understand why IIS is necessary on both boxes, but that does seem to have fixed the issue. BTW, once I installed it I got another error stating the following. I simply followed the instructions in the error by running the commands that it recommends and now all seems to be well. Until the next issue that I'm bound to run into anyway. --------------------------------------------------------Microsoft Exchange Warning--------------------------------------------------------The following warning(s) were reported while loading topology information: Get-OWAVirtualDirectoryCompleted Warning:Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directories. This can happen if Outlook Web Access virtual directories were deleted in Internet Services Manager. Verify that you have access to the metabase on the servers listed below. To correct this inconsistency, run the following command: Remove-OwaVirtualDirectory -Identity "Exchange (Default Web Site)". Running this command will remove references to these virtual directories from the Active Directory directory service."Exchange (Default Web Site)" Warning:Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directories. This can happen if Outlook Web Access virtual directories were deleted in Internet Services Manager. Verify that you have access to the metabase on the servers listed below. To correct this inconsistency, run the following command: Remove-OwaVirtualDirectory -Identity "Public (Default Web Site)". Running this command will remove references to these virtual directories from the Active Directory directory service."Public (Default Web Site)" Warning:Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directories. This can happen if Outlook Web Access virtual directories were deleted in Internet Services Manager. Verify that you have access to the metabase on the servers listed below. To correct this inconsistency, run the following command: Remove-OwaVirtualDirectory -Identity "Exadmin (Default Web Site)". Running this command will remove references to these virtual directories from the Active Directory directory service."Exadmin (Default Web Site)" --------------------------------------------------------OK--------------------------------------------------------

Good to hear you got it working on the new CAS server. The uninstall on the old CAS server may have left the OwaVirtualDirectory configuration defined (popinting to the old server), which (if memory serves me correct) is stored in AD as well as defined on the server. This may be why the environment was complaining about an inconsistency in the AD configuration for the virtual directories. The necessity of IIS on the server is dependant upon the roles you have installed. Depending upon what is left on the old server, you may be able to safely remove IIS at this point. However, remember the old IT adage: If it's not broke, don't fix it. Best Regards, Jeremy