Exchange Server 2010 'Recreating legacy Exchange Virtual Directories'

Exchange 2010 install of the CAS role includes the installation of legacy Exchange Virtual Directories. Exchange, Public and Exchweb Virtual Directories are placed and configured directly in the IIS metabase, therefore these VDs are only local to Server and no longer objects located in Active Directory. “Additionally, Exchange 2010 New-OWAVirtualDirectory cmdlet no longer recognizes the […]

Exchange 2010 install of the CAS role includes the installation of legacy Exchange Virtual Directories. Exchange, Public and Exchweb Virtual Directories are placed and configured directly in the IIS metabase, therefore these VDs are only local to Server and no longer objects located in Active Directory. “Additionally, Exchange 2010 New-OWAVirtualDirectory cmdlet no longer recognizes the -Name parameter and is hard coded to use "OWA" for the name. This behavior is by design. So what happens if we need to manage or recreate only the legacy Exchange VDs on an Exchange 2010 Server? Since the legacy Exchange VDs are no longer listed and manageable in AD, we need to use the appcmd utility (as we do to manage other VDs in IIS 7 and above) or add the VDs in IIS manually and modify the applicationHost.config file directly.”

Full Article: Exchange blog