Solved

Remote Exchange Management Console Initialization failed

Posted on 2016-09-15
18
41 Views
Last Modified: 2016-10-03
I have installed the Exchange Management 2010 Console locally on my PC. (v14.03.0123.003)

When loading the console and expanding "Microsoft Exchange On-Premises" I get an Initialization failed error.

 Initialization failed
Additionally if I try to add an Exchange Forest manually (Right click Microsoft Exchange, Add Exchange Forest), fill in the correct details for the server and click ok, I then enter my administrative credentials and ok, I get the error "Kerberos" authentication failed.

Kerberos authentication failed
I have un-installed and re-installed, same issue. I have also run SFC /SCANNOW which fixed some issues, but not anything with my console access.

My machine was recently re-imaged, so this issue is relatively new.

I can logon directly to the exchange server with the same credentials and load the management console without error.

This is driving me nuts, so any advice and help to resolve is massively appreciated!
0
Comment
Question by:Terry Rogers
  • 10
  • 3
  • 3
  • +1
18 Comments
 
LVL 42

Expert Comment

by:Amit
ID: 41799878
You need to install same level of service pack and RU for management tools also, which you had on your Exchange server. It seems to be version mismatch issue. Run below command on your Exchange server:

GCM exsetup |%{$_.Fileversioninfo}

This will tell you what version you need to install on your management server.
0
 
LVL 16

Expert Comment

by:Dirk Mare
ID: 41799879
Our trend micro antivirus causes similar issues..

Check AV and firewall settings..

DirkMare
0
 
LVL 42

Expert Comment

by:Amit
ID: 41799880
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 1

Author Comment

by:Terry Rogers
ID: 41799942
The version I am seeing on the Exchange Server is 14.03.0235.001, so doesn't match exactly to what I have installed, however both the server and my local machine have been installed with SP3, so not sure where the slight variant comes from.

I've also checked out the link as described and tried following through the instructions without success.

My Firewall was disabled in services.msc, so I have re-enabled to check its configuration, but doubt this is firewall related if the firewall was disabled?

We use McAfee VirusScan Enterprise in our organisation. We have never had to make any changes to this before, and I have a number of other colleagues with this working as expected. I checked the logs to see if there was anything obvious any nothing showed up.
0
 
LVL 16

Expert Comment

by:Dirk Mare
ID: 41799951
It could be that your computer name is different after the reimage and because of this its not in the same group/container as it used to be please unload/exit mcafee just to test.

DirkMare
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41799973
I have disabled McAfee with no further success, in addition prior to the re-image, the machine was deleted from Active Directory, SCCM and McAfee.
0
 
LVL 19

Expert Comment

by:Peter Hutchison
ID: 41800671
Delete the mmc settings cached EMC file from your profile:

C:\Users\username\Appdata\Roaming\Microsoft\MMC\
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41801129
I deleted this as part of the comment from Amit, however I am still getting the same errors.

Are there any logs we can look at, both my machine side and server side?
0
 
LVL 19

Expert Comment

by:Peter Hutchison
ID: 41801133
Other things to check:
1. Is your user still a member of one or more of the Exchange Security Groups e.g. Organization Management.
2. Is your user a member of Domain Admins or Enterprise Admins as well?
3. Is your user a local administrator of your machine?
4. Do you have the correct .NET Frameworks components installed (3.5 for Exchange 2010).
5. Do you have the RSAT tools installed?
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41801219
Hi Peter,

I am still able to logon to the Exchange Server directly and open the Console with the same credentials I am using for the remote console, my account is also apart of Domain and Enterprise Admins and a local administrator of my local PC.

I thought .NET 3.5 might not be installed, but it appears it is, I have removed and re-installed this with no success.

I have RSAT installed and I am using AD Users and Computers, DNS and various other snap-ins with no issues.

Regards

Terry Rogers
0
 
LVL 42

Expert Comment

by:Amit
ID: 41801522
Are you part of Exchange Org Group?
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41802192
What do you mean Exchange Org Group?
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41808260
This seems to be a machine specific issue, and not a permissions issue as I can access management remotely using the console on others machines.
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41819649
Does anyone else have any other ideas on how I can troubleshoot this?
0
 
LVL 16

Expert Comment

by:Dirk Mare
ID: 41819658
Have checked that you machine is up to date with all of windows updates?
Also check online instead of using SUS

DirkMare
0
 
LVL 1

Author Comment

by:Terry Rogers
ID: 41820093
Ok, getting somewhere (I think!). I cleared my kerberos cache using klist purge and I now get a different issue.

I actually have a version mis-match.

Version Mismatch
I've looked at the versions as listed on this MS article ...

https://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-build-numbers.aspx

And downloaded the relevant upgrade patch, however I get the following error:

Upgrade Error
I presume this is because I only have the management console and not the server components / roles installed.

If this is the case, how do I get my console version to match?

The version I have is installed from the current SP3 download.
0
 
LVL 1

Accepted Solution

by:
Terry Rogers earned 0 total points
ID: 41821298
Ok, so I have resolved this now.

It seems I had a cached credential of some kind which after purging resulted in me no longer seeing the access denied error.

After that I was able to install the relevant service packs and roll ups to match versions and wallah, I can now connect.

Thank you all for you efforts in helping resolve this one!
1
 
LVL 1

Author Closing Comment

by:Terry Rogers
ID: 41826024
I was able to trouble shoot and find steps online that aided in my self resolve of this issue.

Please see last comment for further details.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you try to extract and to view the contents of a Microsoft Update Standalone Package (MSU) for Windows Vista, you cannot extract the files from the MSU. Here we are going to explain how to extract those hotfix details without using any third pa…
The following article is intended as a guide to using PowerShell as a more versatile and reliable form of application detection in SCCM.
This Micro Tutorial will give you basic overview of the control panel section on Windows 7. It will depth in Network and Internet, Hardware and Sound, etc. This will be demonstrated using Windows 7 operating system.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question