Exchange 2010 / IIS 7.5 - Config Issues

Hi Experts,

I have been working on this fault for about 24hrs now and I am kind-off at a dead-end / lack of experience (my boss is away on holidays :-S).

Short-Story;
I was making some changes in IIS on our Exchange Server (MS 2008R2, Exchange 2010) yesterday, trying to get OWA redirect to work (http to https) and it has destroyed my Mac Users access to Outlook 2011 email (EWS) and access to EMC - error "WinRM".

So I have done enough damage and I am having no love fixing the issues I have created so I thought I will do a restore, I went into a backup (from the previous day) and copied c:\Windows\system32\inetsrv\config and then I copied the files over to the broken files, did a iisreset and a full server reset.

But OWA and also EWS Mac Users are still having challenges.

our EWS site says; "The page cannot be displayed because an internal server error has occurred".

Also on IIS Admin, there is legacy items (from when I made changes yesterday) - so my restore doesn't sound like it did anything? Did I copy the wrong files?

So really, all I want to do is go back in time before I changed anything on this server :-D

Look forward to your assistance,

Thanks, Alex.
alexballAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

brendanmeyerCommented:
do you have shadow copies of the files?
0
alexballAuthor Commented:
Hi brendanmeyer,

Thanks for your response, nope Shadow Copies is disabled. We use Altaro Hyper-V backup so I have snapshots of the VM and can restore at a file level if required.

I can't restore the whole Exchange server as we have a day of emails we would loose.

Look forward to your feedback,

Thanks, Alex.
0
SeanSystem EngineerCommented:
if you were doing http redirect then you may have a different web.config for each of your Virtual Directories. What i would check first is make sure all your VDs have the correct http redirect enabled or disabled. Make sure they are all marked with the "Only redirect requests to content in this directory" and a Found(302) status code.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

alexballAuthor Commented:
Thanks Zindel1,

That's half the problem / I didn't take down the settings or make a backup prior to making changes (I know right - I.T. 101), so I am not sure of what was in place previously.

I have switched off all the redirects on each VD now and changed the settings to what I would assume was the previous setup (so settings in redirect are off), but EMC and EWS is still dead.

From reading at iis.net (http://blogs.iis.net/bills/archive/2008/03/24/how-to-backup-restore-iis7-configuration.aspx) Bill talks about just the one file location;

%windir%\system32\inetsrv\config

Which should contain all the settings for IIS for each VD? I hence why I have restored these files and nothing has changed, is this the correct file location?

Thanks again, look forward to your feedback,

Alex.
0
alexballAuthor Commented:
Update;

I found an update sitting on the server and ran a 'appcmd.exe restore backup "IISBackupxxxx".

Then did a iisreset

Then rebooted the server,

Now I have lost all my VD's except;
aspnet_client
PowerShell
Rpc
RpcWithCert

Missing owa, EWS etc. this is getting worse, I might stop touching :-S

I then tried to revert this by running the 'appcmd.exe restore backup "CFGHISTORY_0000000089" which was the most recently snap-shot / backup, rebooted again and no issues.

Any assistance would be great,

Thanks, Alex.
0
brendanmeyerCommented:
0
alexballAuthor Commented:
That's great brendanmeyer,

Researching that now, that may be a real option - I am currently running a backup so it doesn't go any further backwards.

Also due to the impacts of the PowerShell VD, EMC / ECC is down - I have to resolve that issue prior to trying to work that angle, any advice getting EMC back up and runnig?

Thanks, Alex.
0
brendanmeyerCommented:
whats the error you get from the powershell emc/ems when you run it?
0
alexballAuthor Commented:
So the error is;

VERBOSE: Connecting to exchange.server.local
[exchange.server.local] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to exchange.server.local
[exchange.server.local] Connecting to remote server failed with the following error message : The WinRM client cannot
 process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site Office 2. Connecting to an Exchange server in another Active Directory site.
WARNING: No Exchange servers are available in the Active Directory site Office 3. Connecting to an Exchange server in another Active Directory site.
WARNING: No Exchange servers are available in the Active Directory site Office 3. Connecting to an Exchange server in another Active Directory site.
WARNING: No Exchange servers are available in the Active Directory site Office 2. Connecting to an Exchange server in another Active Directory site.
VERBOSE: Connecting to exchange.server.local
[exchange.server.local] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
0
SeanSystem EngineerCommented:
At this point i would just delete all vitual directories and recreate them from exchange.

http://technet.microsoft.com/en-us/library/ff629372%28v=exchg.141%29.aspx
0
alexballAuthor Commented:
Hey EE's,

Just an update on this one, got it working again. In the end it was a multi-level fix.

One evening I ran up a Snapshot of a Backup of that VM, Copied all the inetpub / inetsrv folders, the Exchange Folders (Client Access) and using appcmd.exe ran a backup and copied that folder too.

I then replaced all those folders (confirming each replaced files time-stamp was prior to the problem anyway - most were) on the Server and ran a appcmd.exe restore - restoring all the IIS Configs.

Then ran an update on the Server (not sure if that did anything).

That got Activesync and Outlook-anywhere back up an running, but OWA was throwing errors still, EWS was down (HTTP 500 error) and EMC/EMS was still down.

To resolve the rest of the challenges - somehow WinRM II Feature had disabled it self, re-enabling this brought EWS, OWA and EMC/EMS straight backup!

So anyone reading my horror story, resolving it:

1st - Make sure WinRM II Feature is enabled on the Exchange Server - without this EMC/EMS/EWS will not run and OWA throws errors.

2nd - Make sure you have backups of the Server (Client Access, intepub, inetsrv etc.),

Thanks everyone for all your help, you pointed me in the right directions,

Alex.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
alexballAuthor Commented:
Multi-faceted error requiring a multi-faceted fix.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.