asked on

Problem with Exchange 2010 and WinRM

Hi!

I have a problem with Exchange 2010 on Windows server 2008 R2 (domain member).

Oponing the console or shell throws the following error:

[server185] Connecting to remote server failed with the following error message : The WinRM client cannot
process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer (server185:80) returned an 'access denied' error. Change the configuration to allow Kerberos authentication me
chanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify th
e local computer name as the remote destination. Also verify that the client computer and the destination computer are
joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authenticati
on and provide user name and password. Possible authentication mechanisms reported by server: Negotiate For more in
formation, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed

I have tried lot of solutions I have found on Google, but non of them worked.
Any ideas?

Busbar

which version of Exchange 2010 you are using are you using RTM version, also do you use the latest winrm versions?

ironx

ASKER

Hi!

No, it's the full Enterprise version downloaded from MSDN.
Everything is the latest and up-to-date.

Busbar

do you use outlook live?

Saakar

Open IIS manager and let me know the Authentication Settings in Powershell Virtual Directory.. try Only with Windows Integrated Authentication on Powershell VDIR

ironx

ASKER

I have now a different problem with the server, so I have to reinstall Windows... but not right now.
I'll be back in a few weeks.

Thanks anyway.

ironx

ASKER

I have re-installed the server...

Windows Server 2008 Enterprise (all updates)
All pre-requirements of Exchange 2010...

Tried running setup /PrepareAD and /preparelegacyexchangepermissions /prepareschema / preparedomain one-by-one. Both ways the same error:

------------------------------------------------------------

G:\>setup /preparedomain

Welcome to Microsoft Exchange Server 2010 Unattended Setup

By continuing the installation process, you agree to the license terms of
Microsoft Exchange Server 2010. If you don't accept these license terms,
please cancel the installation. To review these license terms, please go to
http://go.microsoft.com/fwlink/?LinkId=150127&clcid=0x409/

Press any key to cancel setup................
No key presses were detected. Setup will continue.
Preparing Exchange Setup

Copying Setup Files ......................... COMPLETED

No server roles will be installed

Performing Microsoft Exchange Server Prerequisite Check

Organization Checks ......................... COMPLETED

Configuring Microsoft Exchange Server

Prepare Domain Progress ......................... FAILED
The following error was generated when "$error.Clear(); if ($RolePrepareAll
Domains) { initialize-DomainPermissions -AllDomains:$true -CreateTenantRoot:$Rol
eIsDatacenter; } elseif ($RoleDomain -ne $null) { initialize-DomainPermissions -
Domain $RoleDomain -CreateTenantRoot:$RoleIsDatacenter; } else { initialize-Doma
inPermissions -CreateTenantRoot:$RoleIsDatacenter; }" was run: "Length of the ac
cess control list exceed the allowed maximum.".

The Exchange Server setup operation did not complete. Visit http://support.micro
soft.com and enter the Error ID to find more information.

Exchange Server setup encountered an error.

---------------------------------------------------------------------

Tried cleaning out AD, with ADSIedit (extended-rights and services) but no luck.

Any ideas?

ironx

ASKER

I'm wondering if there's a way of cleaning out Exchange totally from AD?

Saakar

Open ADSIEDIT and under configuration container > Services>Microsoft Exchange> ORG Name> Servers

Delete the server name and reinstall

ASKER CERTIFIED SOLUTION

ironx

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial