Our exchange 2013 server is an all in one box running in a VM on Hyper-V. This is the only exchange server we have.
Everything was working fine, then yesterday we tried to add a virtual directory to the server under the default website. This was added as first as local folder and then we changed it to a network drive with it setup as an application. We also setup an application pool just for this folder.
About that time, we noticed that exchange clients were having an issue connecting. OWA stopped working, ECP stopped working, Outlook desktop clients stopped connecting.
We un-did all our changes, deleted the application pool we created, deleted the virtual directory, but still nothing is working.
From the Exchange server, we can get the login screen for OWA, but it just hangs on a blank screen after entering the username & password. We're not seeing any errors in the windows system logs.
We've also noticed the Back End Website is running under the default application pool. Not sure if this is correct or not.
Is there a powershell command which will just rebuild the IIS websites? Any help is appreciated.
Thanks