Hello, I'm setting up a demo environment, and to keep it portable I'm trying to keep all products on a single virtual server. This includes: AD, Exchange 2010, SQL 2008 and FIM 2010 - everything. I'm running into the following issue: FIM documentation states "Ensure that the Exchange Web Service and IIS default Web site are not both configured to use port 80". In a lab environment, you may want to run Exchange on the same server as the FIM Service. If you do, ensure that you are reconfiguring Exchange Web Service to not use the default port 80, or Exchange Web Service will not be reachable. After installing Exchange 2010, I change the Default Web Site bindings to another port. Now I can't connect through Exchange Management or Power Shell. Further reading I find the following here http://msexchangeteam.com/archive/2010/02/04/453946.aspx. "Remote PowerShell requires port 80 to be available on the Default Web Site." So it seems that OOTB Exchange 2010 and FIM 2010 aren't compatible on the same box. I need to do the following: 1) correctly change the port for Exchange remote PowerShell, or 2) be able to change the port for FIM. Any help would be appreciated, I'll keep tinkering in the meantime. -Peter

Peter, Create a separate site for Exchange and change the ports/bindings to non-default ports. I use the configuration below on a test and demo server, which needs to run the entire environment on 1 machine. Like: And using the Exchange powershell commands you can link/move the Exchange virtual directories to the new IIS site. You cannot move the VDirs using the Exchange GUI. http://technet.microsoft.com/en-us/library/bb124413.aspx These links should point you in the right direction: Client Access New-WebServicesVirtualDirectory Remove-WebServicesVirtualDirectory Get-WebServicesVirtualDirectory Set-WebServicesVirtualDirectory OWA Get-OwaVirtualDirectory Set-OwaVirtualDirectory New-OwaVirtualDirectory Remove-OwaVirtualDirectory OAB Get-OABVirtualDirectory New-OABVirtualDirectory Remove-OABVirtualDirectory Set-OABVirtualDirectory I might forget a few commands to complete the task, but you must make sure all Exchange related IIS components and virtual directories are moved to the new site (using the Exchange powershell commands). Exploring the Exchange powershell get commands will show you quickly which virtual directories to move. The following code examples create a set of new Outlook Web Access legacy virtual directories named "exchange", "public", and "exchweb" in a non-default IIS Web site named "contoso.com" on the local Exchange server. New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType Mailboxes -Name "exchange" -WebSiteName "Contoso.com" New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType PublicFolders -Name "public" -WebSiteName "Contoso.com" New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType Exchweb -Name "exchweb" -WebSiteName "Contoso.com" HTH, Peter Peter Geelen - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

Hi Peter, Thanks so much. I took a different approach myself instead of changing the Exchange port, I left them both on port 80 and specified an IP address of the Default Web Site, while leaving the other open (*). Then I went in to the HOST file and manually entered the IP address for Default Web Site to the netbios and FQDN for the server, and added another IP address for the FIM address. A bit hocky but it works too.