Finally, the long awaited Exchange Server 2010 Architecture Poster is here!
This is similar to the Exchange 2007 Component Architecture poster and contains the architecture highlights and feature set of Microsoft Exchange Server 2010. This architecture poster is additional to the already published Microsoft Exchange Server 2010 Transport Server Role Architecture Diagrams which you could already get here.
You can download the Microsoft Exchange Server 2010 Architecture poster here.
While upgrading one of my existing Exchange 2010 lab machines from RTM to SP1, I encountered the following error message during the upgrade:
Error:
The following error was generated when "$error.Clear();
if (!(get-service MSExchangeADTopology* | where {$_.name -eq "MSExchangeADTopology"}))
{
install-ADTopologyService
}
" was run: "There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)".
There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
The message appeared at the stage of upgrading the Unified Messaging components. I had a look at the ExchangeSetup.log file and it contained the the following information:
[08/27/2010 10:08:13.0948] [2] Beginning processing install-UMService [08/27/2010 10:08:14.0011] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9) [08/27/2010 10:08:14.0027] [2] [ERROR] There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9) [08/27/2010 10:08:15.0823] [1] The following 1 error(s) occurred during task execution: [08/27/2010 10:08:15.0823] [1] 0. ErrorRecord: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9) [08/27/2010 10:08:15.0823] [1] 0. ErrorRecord: System.Runtime.InteropServices.COMException (0x800706D9): There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9) at Interop.NetFw.INetFwRules.Add(NetFwRule rule) at Microsoft.Exchange.Security.WindowsFirewall.ExchangeFirewallRule.Add() at Microsoft.Exchange.Configuration.Tasks.ManageService.Install() at Microsoft.Exchange.Management.Tasks.UM.InstallUMService.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord()
It seems the error is caused while trying to add a firewall rule, indicated by Interop.NetFw.INetFwRules.Add (INetFwRules is the rules collection of the built-in Windows Firewall).
I had a quick check with the firewall settings on the machine and it turned out the Windows Firewall was disabled. I figured that perhaps adding the rules failed because setup couldn’t communicate with the firewall service.
I enabled the Windows Firewall and this time the upgrade process went fine:
[08/27/2010 10:23:10.0988] [2] Beginning processing install-UMService [08/27/2010 10:23:11.0145] [2] Ending processing install-UMService
Many of us have been setting up and testing SP1 Beta in (I hope) lab environments. One of the nice additions to the setup process people reported is the option Automatically install Windows Server roles and features required for Exchange Server, shown during the Installation Type selection. Be advised that this option is – as stated – limited to Windows Server roles and underlying features only. You still need to install other possible prerequisites first, such as the 2007 Office System Converter. Also, the option doesn’t seem to work 100% in SP1 Beta, as I had to manually add IIS features like IIS7 Basic Authentication and IIS7 Windows Authentication.
Although this potentially saves us executing the well-known Add-WindowsFeauture cmdlets (2008 R2 or ServerManagerCmd in 2008 SP2, see this article), I hope Microsoft includes automatic installation of the additional prerequisite components in SP1 RTM as well. I expect it would be little trouble to include these components as well, accelerating the process of installing Exchange 2010 SP1 and rendering prerequisite installation scripts like this script from Pat Richard obsolete.
Note that Exchange 2010 setup also supports resuming. Nice when setup discovers a pending restart; resuming means you can reboot, start setup again and continue where you left off; no need to enter all the information again. More information on resuming setup and watermarks here.
Note that I’ve been installing Exchange 2010 SP1 Beta on Windows Server 2008 R2 only so far, so on Windows Server 2008 SP2 your mileage may vary.
EighTwOne (821) 