single server - Windows Server 2012 R2 and Exchange 2013 Standard

Exchange mail flow is working but couldn't access OWA
checked IIS and the Default Website is stopped, tried to restart but no luck
clicked to View Virtual Directories and don't see any?
Exchange Back End is running and the virtual directories are there
Was going to recreate the Default Website virtual directories using power shell but it fails to connect
winrm qucikconfig shows it's already setup and running

How to correctly recreate the virtual directories for the Default Website without access to ps?

Thanks

update:
Since I can't connect to Exchange Shell Management, I added the snapin to Windows powershell.
I then ran the following commands, substituting my server name for ServerName:
Remove-OwaVirtualDirectory ServerName\owa (Default Web Site)
Remove-OwaVirtualDirectory ServerName\owa (exchange back end)

This seemed to work, asking me for confirmation, so I then attempted to run the following commands, substituting my server/domain:
New-OwaVirtualDirectory  -InternalUrl https://ServerName/owa -ExternalUrl https://mail. domain.com/owa
New-OwaVirtualDirectory  -InternalUrl https://ServerName/owa -ExternalUrl https://mail.domain.com/owa -WebSiteName Exchange Back End

But this failed for each, returning a message that the website doesn't exist?
Of course they don't, so this makes no sense?

• Edited by trythis Monday, June 08, 2015 1:35 AM

444

No, stopping the Exchange Back End site has no affect on being able to start the Default site.

also, I can't access the Exchange management shell so I added the Exchange snapin to powershell and ran:
Get-AutodiscoverVirtualDirectory

which gave me this (i've edited the server.domain):

WARNING: IIS://myserver.mydomain.local/W3SVC/1/ROOT/Autodiscover wasn't found. Please make sure you've typed it correctly.

• Edited by trythis Monday, June 08, 2015 4:43 PM

I'd never have thought of that, since I've never used DirectAccess.  But I can see how there would be a massive conflict :-)

It would be good if you could configure it to use a different port.

Yes, since Exchange was installed after DA and both it and the vpn worked successfully until  the mysterious IISReset obviously DA can use another port.

I'd call this a major bug, for which I paid dearly, but MS will just call it a non-recommended installation (easy excuse). In other words, their own products don't play well together. So much for integrated solutions.

Not just Exchange, either. I'd imagine that this would break anything with IIS on, where you wanted to use SSL for the usual purpose.