• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 962
  • Last Modified:

Failed to open Exchange 2010 mangement console

We failed to open Exchange 2010 mangement console after install 2008 R2 SP1.

Error Message:

Initialization failed
The following error occurred when retrieving user information for 'domain\Administrator':
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.

Any idea how to fix it or any log could help to narrow the cause?
Environment:
2008 R2 DC, Exchange 2010 in 2008 R2 member server  in Hyper-V
0
dickchan
Asked:
dickchan
3 Solutions
 
Alan CoxSr. Systems Engineer | Lead Microsoft CIE Qualified FacilitatorCommented:
0
 
williamvanerpCommented:
Did you check if the WinRM is still installed?
0
 
Alan CoxSr. Systems Engineer | Lead Microsoft CIE Qualified FacilitatorCommented:
yup. good point. I've had to remove and re-install before.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
waleedaCommented:
Better re-install the Exchange Management console, to save the time
0
 
Suliman Abu KharroubIT Consultant Commented:
please try to config the winrm :

run-->cmd:
winrm qc
0
 
dickchanAuthor Commented:
WinRM is installed.

 When i run WinRM qc, is shows:
[PS] C:\Windows\system32>winrm qc
WinRM already is set up to receive requests on this machine.
WinRM already is set up for remote management on this machine.

When use Power Shell, it prompts:
 C:\Program Files\Microsoft\Exchange Server\V14\bin\CommonConnectFunctions.ps1:116 ¿¿:48
+             $global:importResults=Import-PSSession <<<<  $global:remoteSession -WarningAction SilentlyContinue -Disab
leNameChecking
    + CategoryInfo          : InvalidResult: (:) [Import-PSSession], RuntimeException
    + FullyQualifiedErrorId : ErrorFromRemoteCommand,Microsoft.PowerShell.Commands.ImportPSSessionCommand
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now