Hi all, I backup my Exchange servers with Backup Exec. I get a bunch of errors nightly in the "MSExchange Management" log due to the backups, but they were working properly, so I wasn't too concerned and figured I'd get it resolved when time allowed. Well, that time is now. I submitted a case on the Symantec forums about it and found out I should have the Exchange Management Tools installed on the backup server, which I didn't have. I installed them yesterday and installed the Rollup 3v3, but whenever I try to open the Exchange Management Console I get the following error: The following error occurred while attempting to connect to the Exchange server 'utl004.domain.local': The attempt to connect to http://utl004.domain.local/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooring Help topic. Additional information: -The server running the Backup Exec media server software is named "utl004". -The Exchange server that is running my CAS is named "exc003". -If I click "Add Exchange Forest..." I can connect properly to exc003, albeit as a separate forest (not "Microsoft Exchange On-Premises"). -If I open the Exchange Management Shell it connects automatically to exc003 without issue. -When I open the EMC (and EMS) from my workstation it connects to exc003 without issue. Also, a few months ago, I set up this server as a FaxMaker server. FaxMaker requires an SMTP engine on the server where it is installed. I was looking for the SMTP Server under IIS and couldn't find it, so I thought it was removed from 2008 R2, so I installed a Hub on utl004 (until a day later when I talked with GFI support who showed me the SMTP Server is a "Feature" and not a "Role" in Server Manager...d'oh!). I'm thinking it may have something to do with the fact that this server was a Hub at one point in time, but it NEVER had a CAS role. As for other software on this server, in addition to FaxMaker and Backup Exec, it is running WSUS and an SNMP collector ("FMAudit", for our managed printing service) and it has Office 2010 installed (to convert files for FaxMaker). Does any ideas on this one? I'd like to think that there is some sort of configuration somewhere that is pointing Microsoft Exchange On-Premises to itself, and that it may be easily changed. Oh, and I looked through ADSIEdit and didn't see any mention of utl004 being an Exchange server/having Exchange roles. Thanks in advance!

Hi, have you configured winrm? I think that starting the Exchange Shell don´t work with the same error as the EMC. regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

Hi, have you configured winrm? I think that starting the Exchange Shell don´t work with the same error as the EMC. regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com Hi there, Have I configured WinRM on which server? The one I am trying to connect from (utl004), or the Exchange server (exc003)? If utl004, then yes, if the Exchange server, would it matter if I can connect to it from other systems? Remember, I can connect to it from my workstation, so I think it is configured properly on the Exchange server. If it were a WinRM issue on the Exchange server I figure I wouldn't be able to connect to it from my workstation. Thanks.

You have to configure it on the Backup Serrver ('utl004.domain.local') But here is a list of typical errors concerning winrm: 1) check the user account you are logged on with. It should be the deomain admin Account 2) Perhaps user Account Control blocks the start of the shell 3) check the HTTP proxy Settings with the netsh command: netsh winhttp show proxy 4) check the time on both servers (Exchange and Bakupserver) It should be the same 5) check the exchange certificate and if the client (Backup Server) trusts that certificate of the Exchange server. 6) check the Firewll TCP 443 (HTTPS) should be allowed. 7) check if remoting is enabled: enable-psremoting regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

Thanks for the reply. Yes, I did run winrm qc on the backup server. As to your list, here are my replies: 1. I am using the domain administrator account. 2. UAC is disabled. 3. "Direct access (no proxy server)." is the result of that netsh command. 4. They're the same. 5. The certificate is good, but I'm not sure I would know how to make sure the backup server cana trust it. Should I just visit the OWA page and make sure it can view the cert without issue? If so, it does. I also clicked "Install Certificate...", but that didn't seem to help. 6. I have the firewall disabled on both of these servers. 7. From which server should I run this? The backup server or the Exchange CAS? Either way it brings up a list of items to run: Running command "Set-WSManQuickConfig" to enable this machine for remote management through WinRM service. This includes: 1. Starting or restarting (if already started) the WinRM service 2. Setting the WinRM service type to auto start 3. Creating a listener to accept requests on any IP address 4. Enabling firewall exception for WS-Management traffic (for http only). Also, remember, it says it is trying to connect to "utl004.domain.local" in the first line of the EMC, not the actual Exchange server.

OK one step back utl004.domain.local" is you Backupserrverr right and on that serrver the EMC doesn´t start and the Exchange Shell doesn´t work as well. But if you log on to th CAS or Databaseserverr then the EMC works. right? So the winrm on the Backupserrver (utl004.domain.local") has got problems.Because first of all it tries to connect locally (implicit remoting)regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

No, as I stated in the initial post the Shell connects/works fine from utl004; it is only the Console that will not connect. The error states that it cannot connect to http://utl004.domain.local/PowerShell, but it should be connecting to http://exc003.domain.local/PowerShell. Also, I can connect to exc003 (the CAS server) from my workstation (named pnewell) with both the Console and the Shell without an issue. From exc003 (the CAS) I can connect to itself and I can connect to exc002 (the database server) with the Console and Shell. From exc002 I can connect to itself and to exc003 with the Console and Shell. EDIT: Oh, and remember, I can connect to a "Separate" Exchange forest by choosing "Add Exchange Forest...", it's just that it's not the "Default" Exchange On-Premises forest.

I figured it out. I figured it had to be in the registry or a config file somewhere, and it was indeed in the registry: HKCU\Software\Microsoft\ExchangeServer\v14\AdminTools\NodeStructureSettings (REG_BINARY key) I compared that key on utl004 to the same key on my workstation. My workstation mentioned exc003.domain.local, while the one on utl004 said utl004.domain.local. The key on utl004 was also twice as long as the one on my workstation. I backed it up, deleted it, then reopened the EMC, and it connected to exc003 right away! Maybe now I can try to take care of the errors with the backup. ;) Thanks for your time and suggestions, Peddy.