Hi Everybody, My name is Matt and I'm a 15 year veteran in IT. I have gone back to college for additional training and certification. Currently we are in our "CapStone" class, undergoing a large project which we have to define a solution. For our team solution we are using Windows Server 2008 R2 Enterprise x64, SQL Server 2008 R2, SharePoint Server 2010 Enterprise, and Exchange 2010. I've managed to get my core network up and running such as the ADDS, WSUS, WDS, etc... We are running with three servers (ADM, MAIL, SQL). ADM runs ADDS, DNS, DHCP, WSUS, WDS. MAIL runs Exchange and SharePoint, and SQL is well... SQL. I succesfully installed SQL, no complaints, and SharePoint. However after I installed SharePoint, I proceeded to install Exchange 2010, only to learn that the EMC wanted to connected to port 80. I look into this and found in IIS that I had a site "SharePoint - 80" with bindings to port 80. Went back into the SharePoint Admin Web App and removed "SharePoint -80" and recreated it as "SharePoint -8080". I now receive the follwing error from the EMC... INITIALIZATION FAILED The following error occured when searching for On-Premises Exchange server: [mail.capstone.edu] Connecting to remore server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'. I've gone around and around for the last two hours trying to read up on anything that would help, to no avail. Can anyone help me with this? If all else fails I could just re-image the server and install Exchange first then SharePoint, unless anyone know of any incompatibilities?Matthew

I am dizzy from reading your post. Suffice it to say that if you've mucked with IIS, you very well could have screwed up WinRM (remote PowerShell, upon which the Exchange Management Console is based) since it is served up by IIS.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi I find many interesting solution. 1. Update 2010 to SP1 and turn off Antivirus software. 2. In my case I had removed the http binding on port 80 from my default web site that Exchange is using for OWA etc. I left if with just HTTPS bound. I belive this is what caused the issue. As soon as I added a http port 80 binding back to the default web site everything started working again. 3. You can read this article.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 for the input. I discovered that WinRM wasn't installed before I installed Exchange, however installing is after-the-fact hasn't help either. I'm going to try and install Exhange SP1 and see if that resolves the issue now that SharePoint isn't consuming the TCP:80 port. Should this fail to resolve my issue, I going to install Hyper-V and install Windows Server 2008 R2 to the virtual machine and load exchange there. Should that approach fail then I'll just re-image the server all together, need to resolve this as easily as possible by tonight so my team can begin development. I really do appreciate the help. Matthew

Hi Do you have anything to update your issue ?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.