Hi all, We have a windows 2003 server (single exchange server) and we are moving all to 2010. So we had to prep Ad and all the requirements, etc..... all good. The idea was to build 2010 then migrate the mailboxes over to 2010 box and decommission the 2k3 server. Current Exchange Server: 2k3 windows OS and Exchange 2003 - both standard 32 bit edition (physical server) New Exchange Server: 2k8 Enterprise R2 OS and Exchange 2010 - Both Enterprise 64 bit edition (physical server) I've installed Exchange 2010 after meeting all requirements and all seemed to install successfully. Everything seemed to install correctly and I can see all services running and it appears in the exchange organisation via System Manager but I obviously can't manage the 2010 server using that 2k3 snapin. Anyway, with all seemly looking good I tried to load the 2010 EMC but have this strange error that appear once the EMC is loaded and I try to view the contents of the Exchange On Premises object (top left under Microsoft Exchange). I've tried many options to get things running like disabling anonymous access in IIS, adding fqdn into the IIS bindings and nothing. I just can't seem to bring up the console. I'm really stuck at the moment and not sure where to go from here to get the EMC snapin working and connected to the new 2010 server so I can manage and configure it. See error msg below: The following error occurred when searching for on-premises exchange server: [mbxserver.blah.com] Connectng to remote server failed with the following error message: The WinRm client sent a request to an HTTP server and go an response say the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocal. For more information, see the about_Remote_Troubleshotting Help Topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'. Can anyone help as I'm really stuck on this and not an Exchange expert. Thanks, Ryan.

Hi All, Just to add some more information, I've also completed a few tests for your information. Please see below: PS C:\Users\Administrator> winrm get winrm/config Config MaxEnvelopeSizekb = 150 MaxTimeoutms = 60000 MaxBatchItems = 32000 MaxProviderRequests = 4294967295 Client NetworkDelayms = 5000 URLPrefix = wsman AllowUnencrypted = false Auth Basic = true Digest = true Kerberos = true Negotiate = true Certificate = true CredSSP = false DefaultPorts HTTP = 5985 HTTPS = 5986 TrustedHosts Service RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD) MaxConcurrentOperations = 4294967295 MaxConcurrentOperationsPerUser = 15 EnumerationTimeoutms = 60000 MaxConnections = 25 MaxPacketRetrievalTimeSeconds = 120 AllowUnencrypted = false Auth Basic = false Kerberos = true Negotiate = true Certificate = false CredSSP = false CbtHardeningLevel = Relaxed DefaultPorts HTTP = 5985 HTTPS = 5986 IPv4Filter = * IPv6Filter = * EnableCompatibilityHttpListener = false EnableCompatibilityHttpsListener = false CertificateThumbprint Winrs AllowRemoteShellAccess = true IdleTimeout = 180000 MaxConcurrentUsers = 5 MaxShellRunTime = 2147483647 MaxProcessesPerShell = 15 MaxMemoryPerShellMB = 150 MaxShellsPerUser = 5 PS C:\Users\Administrator> winrm quickconfig WinRM already is set up to receive requests on this machine. WinRM already is set up for remote management on this machine. PS C:\Users\Administrator> PS C:\Users\Administrator> get-Pssnapin Name : Microsoft.PowerShell.Diagnostics PSVersion : 2.0 Description : This Windows PowerShell snap-in contains Windows Eventing and Performance Counter cmdlets. Name : Microsoft.WSMan.Management PSVersion : 2.0 Description : This Windows PowerShell snap-in contains cmdlets (such as Get-WSManInstance and Set-WSManInstance) that a re used by the Windows PowerShell host to manage WSMan operations. Name : Microsoft.PowerShell.Core PSVersion : 2.0 Description : This Windows PowerShell snap-in contains cmdlets used to manage components of Windows PowerShell. Name : Microsoft.PowerShell.Utility PSVersion : 2.0 Description : This Windows PowerShell snap-in contains utility Cmdlets used to manipulate data. Name : Microsoft.PowerShell.Host PSVersion : 2.0 Description : This Windows PowerShell snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the Windows PowerShell console host. Name : Microsoft.PowerShell.Management PSVersion : 2.0 Description : This Windows PowerShell snap-in contains management cmdlets used to manage Windows components. Name : Microsoft.PowerShell.Security PSVersion : 2.0 Description : This Windows PowerShell snap-in contains cmdlets to manage Windows PowerShell security. Name : Microsoft.Exchange.Management.PowerShell.E2010 PSVersion : 1.0 Description : Admin Tasks for the Exchange Server Name : Microsoft.Exchange.Management.PowerShell.Setup PSVersion : 1.0 Description : Setup Tasks for the Exchange Server Name : Microsoft.Exchange.Management.Powershell.Support PSVersion : 1.0 Description : Support Tasks for the Exchange Server

Yes, we cannot manage Exchange 2010 from Exchange management tools for Exchange 2003 and Exchange 2007.Please check my post in the similar thread:http://social.technet.microsoft.com/Forums/en/exchange2010/thread/1513c920-ead5-424e-9fc5-c460c7b71f3fhttp://social.technet.microsoft.com/Forums/en-GB/exchange2010/thread/0d560a46-3bf6-4703-8ebe-064947899546 http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/ff50ab37-b4da-4c19-a830-e4f3cc38080fBesides, we have a article publish on Exchange team blog to address this issue. Possible Causes: 1. The http binding has been removed from the Default Web Site. A common scenario for this is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by requiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Remote PowerShell requires port 80 to be available on the Default Web Site. If you want to set up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx and follow the directions under the section "For a Configuration in Which SSL is Required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0". 2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue, you need to clear out the Hostname field under the port 80 bindings on the Default Web Site. Troubleshooting Exchange 2010 Management Tools startup issues http://msexchangeteam.com/archive/2010/02/04/453946.aspxRegards,Xiu