EMC still trying to connect to old server
Hi all,
I am in the process installing Exchange 2010 and transitioning from Exchange 2003.
I initially installed a CAS array consisting of 2 servers using old server names thinking this is what I needed in the DMZ. Then I removed this role after a bit of research, and set them up as Edge servers. Then I uninstalled that role after I decided that
we already have Barracudas to do this job already.
So I built these 2 servers again as a CAS array (with different hostnames and IPs) in the internal network and everything is fine. Except that when I open the EMC the 'Microsoft Exchange On-Premises' does not connect.
I am able to connect using the EMC by adding a new forest and entering the hostname of the CAS server as part of the new organisation, I can see the new CAS array just fine and administer it normally. However I would like to remove the old Microsoft Exchange
On-Premises connection as it does not exist any more, and it also brings up an error when I click on it:
The attempt to connect to http://hostname.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request.
The following error occured while using Kerberos authentication: The network path was not found.
This is not a user permissions error. The EMC is simply not able to connect to servers I have shut down before. Is there a way to remove this manually?
Thanks in advance
Andoni
December 22nd, 2010 3:35pm
Do you have any stale DNS records left behind by those servers?[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2010 3:50pm
Nope. The only DNS record I have is for the CAS array name, but that has been deleted.
The EMC is trying to connect using the direct hostname. I am using the EMC directly on each CAS server.
December 22nd, 2010 4:20pm
Hi,
Please follow these steps to specify a remote Exchange 2010 server for EMC:
1.OPen EMS,Enter your network credentials and store them in a variable by running the following command.
$UserCredential = Get-Credential
In the dialog box that opens, type the user name and password of the administrator account that has access to administer the Exchange 2010 server you want to connect to, and then click OK.
2. Open the connection to Exchange 2010 by running the following command.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
http://<FQDN of new Exchange 2010 server>/PowerShell/ -Authentication
Kerberos -Credential $UserCredential
3 .Import the server-side PowerShell session into your client-side session by running the following command.
Import-PSSession $Session
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks
Gen Lin-MSFT
Free Windows Admin Tool Kit Click here and download it now
December 24th, 2010 8:54am
Gen Lin,
i have the same issue but this doesn't work for me.
Hani
December 28th, 2010 8:32pm
Hi Gen,
I am simply trying to remove the dormant connection entry called "Microsoft Exchange On-Premises" from the EMC.
I have a second working connection in the EMC, I just need to tidy up the client. Is there a way to delete the EMC configuration and start again with no connections inside it?
Thanks
Andoni
Free Windows Admin Tool Kit Click here and download it now
January 4th, 2011 2:12pm
You should be able to do this with ADSI Edit but Gen should confirm this first.MVP Exchange Server
January 4th, 2011 9:46pm
I had a similar issue and I resolved mine; there's a key in the registry that is caching the address of the local server as an Exchange Server. When the Console starts it looks to itself first to see if it is a part of the Exchange infrastructure -
your server thinks it still is one.
Here's my thread:
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/cef4a010-0a64-40a7-8601-1539ffdb2568
Long story short, crush the binary key: HKCU\Software\Microsoft\ExchangeServer\v14\AdminTools\NodeStructureSettings.
...only six months late to the party here. ;)
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2011 12:41am
hi Paul,
thanks so much!
part of the problems I had were because the download media was corrupt, and was causing issues with the exchange install. I rebuilt all of my servers using another download link and all works fine now.
thanks though, your help will be valuable to others whose installations are fine but the EMC still has a problem.
Andoni
June 6th, 2011 9:13am