Comments on: Exchange 2010. Unable to access console or shell.

By: Niklas Jumlin

Niklas Jumlin — Wed, 04 Jan 2012 08:28:08 +0000

I’m thrilled! =) I’m hoping more can find this small blog and benefit out of this post.

By: Mattioumatt

Mattioumatt — Wed, 21 Dec 2011 14:48:31 +0000

Sorry for my English…

I had exactly the same problem (The WinRM client received an HTTP server error status (500)).
This was due to dupplicated SID’s (2 cloned VM’s, one for DC, the other for Exchange).

What worked for me, and since no problem :
- Sysprep on my Exchange server (under C:\Windows\System32\Sysprep\Sysprep.exe),
- Join domain
- Reinstall Exch,
And everything’s fine
…

By: Angelo De Bonis

Angelo De Bonis — Mon, 07 Nov 2011 12:06:07 +0000

Thank You,Thank You,Thank You,Thank You,

You have no idea how long I have been working on this.

Yet you made so simple. You have been promoted to Guru status.

Not to mention you saved my ass.

Thnaks again

Angelo

By: Peter A

Peter A — Fri, 28 Oct 2011 04:56:39 +0000

Thanks for your efforts. The web has many sites with solutions like this one:
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
No site ever mention what you do on step 2 above, authentication methods. By enabling Windows Authentication only I was able to start the Exchange 2010 console and shell.
Thanks!
Peter A

By: Niklas Jumlin

Niklas Jumlin — Thu, 01 Sep 2011 07:21:27 +0000

I’m really glad I could help you solve your nightmares :)

By: Gotenks

Gotenks — Wed, 31 Aug 2011 21:58:14 +0000

Solution:
Server Manager > Roles > Web Server (IIS) > Scan this role
Comes up with error “Application pools should be set to run as application pool identitiies”.

To fix that, I went to Administrative Tools > IIS Manager > (hostname) > Application Pools > Right-click each application pool except Classic .NET AppPool > Advanced Settings > Identity > “Change to:” Application Pool Identity

Now I did that… and then calls started coming in no one was able to get to their OWA. I couldn’t even get to the EMC or EMS without errors similar to as mentioned above.

Being as the permissions as shown in Step 2 above were correct. I remembered having also made this change and reverted it.

So again: To fix that, I went to Administrative Tools > IIS Manager > (hostname) > Application Pools > Right-click each application pool except Classic .NET AppPool > Advanced Settings > Identity > “Change to:” LOCAL SYSTEM

Now, at least everything works again. I didn’t need to reboot for this to take effect, but if it makes ya feel better select ‘recycle’ on each Application Pool item.

Exchange 2010 functionality is more important to me than a best practices warning here.

By: Steven

Steven — Tue, 12 Jul 2011 16:13:20 +0000

THANK YOU! THANK YOU! THANK YOU!

This worked great! I spent 3 days (including my birthday) trying to resolve this for my client.

God Bless,

Steven

By: TPeter

TPeter — Tue, 17 May 2011 06:12:10 +0000

Huge Thanks !

Was scrolling the Net for almost 2 weeks, then your last suggested powershell tips solved my problem.

Thanks again,

Peter

By: Alexander

Alexander — Fri, 04 Mar 2011 08:07:18 +0000

we can really run some test.. if you have a time for it…
we have right where it was started. -auto doesn’t work. FQDN works!
if in gpedit.msc we disallow Negotiate authentication for client we have an error

PS C:\Users\aerotop> winrm get winrm/config/client/auth
WSManFault
Message = The WinRM client cannot process the request. Negotiate authentication is currently disabled in the client
configuration. Change the client configuration and try the request again. If this is a request for the local configurati
on, use one of the enabled authentication mechanisms still enabled. To use Kerberos, specify the local computer name as
the remote destination. To use Basic, specify the local computer name as the remote destination, specify Basic authenti
cation and provide user name and password.

Error number: -2144108319 0x803380E1
The WinRM client cannot process the request. Negotiate authentication is currently disabled in the client configuration.
Change the client configuration and try the request again. If this is a request for the local configuration, use one of
the enabled authentication mechanisms still enabled. To use Kerberos, specify the local computer name as the remote des
tination. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and pro
vide user name and password.

Does it mean that it tries to use NOT kerberos by default ? is it alright ? how can we change it ?

By: Niklas Jumlin

Niklas Jumlin — Fri, 04 Mar 2011 07:20:12 +0000

I really have no clue, I can’t help you much more.
But I really believe it has do to with Kerberos authentication.