My Exchange 2010 is ... poorly!

[cpjitservices]

Yes, autodiscover has always worked, we use it for external clients mainly, or we did until it broke.

[cpjitservices]

Clients using Outlook are still sending/receiving mail fine, It's OWA AND EMC that doesn't work and also Exchange Powershell.

[cpjitservices]

I have found 3 entries on my bindings on Default web site in IIS, ones that I haven't put in there.

 

Listed below:

 

net.msmq localhost

net.pipe *

net.tcp 808:*

 

Should they be in there ? considering I only need HTTPS and HTTP on that server.

Edited December 17, 2013 by cpjitservices

[twin--turbo]

have you checked the IIS logs in c:\inetpub\.....

 

Rob

[cpjitservices]

Yep, Nothing in there that looks out of the norm.

 

 

have you checked the IIS logs in c:\inetpub\.....

 

Rob

[cpjitservices]

I have got IIS working again and OWA is back up... I deleted all of those net.* bindings and we are back in business... However Exchange MC is still broken.

 

Ill try a reboot during lunch time.

[Domino]

Have a read of this thread: Repair Exchange 2010 IIS virtual directories

 

there's a few things there that may be relevant to you.

[apeman]

The exchange management console uses iis even though its an mmc so i would say thats still where your problem lies, be careful running the repair commands they can actually make things worse.

[HPlum78]

Have you run the EMT on this? First place to go when you have issues with WINRM while running the exchange management console. See here Blogs - Exchange Team Blog - Site Home - TechNet Blogs

[cpjitservices]

I'll try that although I cant use Powershell.

 

 

Beauty! Seems to of worked and I now have access to EMC.

 

Thanks.

Edited December 18, 2013 by cpjitservices