Exchange 2008 w/o Edge or Hub transport servers

We are moving to Exchange 07 for somewhere between 5-10K users. I've already talked management into using IronPort instead of MS Edge Transport servers. Would anyone who is currently doing this like to comment on how it is working?
More importantly, it seems to me that IronPort can also do the job of the Hub Transport servers. However, I've been told that Exchange 07 cannot run without them. We are currently using LDAP accept and LDAP routing on IronPort (with AD). Can't that take the place of the Hub servers for Exchange?
I have been looking long time similar solution. If You have more information, please let me know. IronPort and Microsoft support didn't know is this possible.
We are using Exchange 2007 as internal mail server and Exchange
2007 uses for outgoing (public internet) traffic IronPort cluster as mail (anti spam/anti
virus) gateway, so for example if some our [email protected] sends email to
[email protected], the message goes true external mail gateway.
But when AD/MS domain and Outlook users sending messages between themselves, like
[email protected] > [email protected], the messages does not goes true external
mail gateway right now.
This seems to be Hub Transport Server default behavior.
But as in IronPort we are using a a lot different content filters to remove headers, add
headers, drop specific attachment, look into archives encrypt and decrypt, notify,
quarantine, message tracking etc, so I'd like to route every single message true IronPort
but can't find any way to do it.
As far I know Hub Transport Servers can run specific software, like Forefront etc which
intercept the local traffic.
So So basically IronPort should act as external security appliance for Hub Transport Servers.

Similar Messages

Installing Exchange 2010 on Server 2008 R2 Get error with Hub Transport Role

Hub Transport Role
Failed
Error:
The following error was generated when "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " was run: "Installing product D:\Program Files\Microsoft SQL Server\Microsoft\Exchange Server\V14\TransportRoles\agents\Hygiene\ASEntIRS.MSI failed. Fatal error during installation. Error code is 1603.".
Installing product D:\Program Files\Microsoft SQL Server\Microsoft\Exchange Server\V14\TransportRoles\agents\Hygiene\ASEntIRS.MSI failed. Fatal error during installation. Error code is 1603.
Fatal error during installation
Elapsed Time: 00:00:01
Client Access Role
Cancelled

Hi,
From the description, I recommend you copy the Exchange installation files to the local machine, or download a fresh copy of Exchange 2010 and then reinstall it.
Besides, please ensure that you install Exchange 2010 on 64-bit edition of Windows Server 2008 R2 Standard with SP1 or Windows Server 2008 R2 Enterprise with SP1.
If the issue persists, please refer to the following KB further troubleshooting.
You receive error 1603 when you try to install the Exchange Server 2010 RU1
https://support.microsoft.com/kb/981474
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

How to migrate Exchange HUB transport 2007 server with Exchange Hub transport 2010.

Hi,
How to migrate hub transport 2007 server with Exchange 2010 hub transport server.
Regards
Anil

Hi Anil
You do not do an in-place upgrade of Exchange - you build new Exchange 2010 Hub Transport Servers, you can utilize existing hardware by uninstalling and installing Exchange 2010 - but you must have Hub Transport Servers that match the Exchange version in
place for all Mailbox Servers that have the same Exchange version.
Essentially there must be Exchange 2007 Hub Transport servers in place whilst there are Exchange 2007 Mailbox servers.
Read "Upgrading from Exchange 2007 Transport -
http://technet.microsoft.com/en-us/library/dd346708%28v=exchg.141%29.aspx"
Exchange 2010 will synchronise certain configuration like Transport Rules and journaling when installing the first Exchange 2010 Hub Transport server, but from then on you must ensure synchronisation yourself.
Send Connectors and Recieve Connectors will need manual configuration.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Exchange 2010 hub-transport server

i have 2 exchange 2010 hubtransport servers.
ideally when i send email my email should be load-balanced but emails send using hubcas1 goes fine and hubcas2 kepts in queues
suppose if i send at a time 5 mail
3 emails go through hubcas1
2 emails stucks in queue in hubcas2

Hi,
As you said you have added both the hub transport servers in the source server option of the send connector.Same time you have mentioned you don't have the smart host to deliver the emails to the internet and also the server hubcas2 can able to resolve the
external domain namespaces .Then do the following .
step 1 :Then please enable the protocol logging on the send connector to see the why the connections from the server hubcas2 is rejected to send emails to internet.
Step 2: Then do the outbound email test from EXRCA tool by using the ip address or name which is mapped on the MX record which belongs to the server hubcas2.
Please feel free to reply me if you have any queries .
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Adding new Hub Transport server in existing environment

Hi everyone,
Currently we have 5 exchange servers 2010 :
2 CAS Servers (Virtual)
2 MB and Hub Transport servers (Physical)
1 Edge server in DMZ. (Virtual)
Now I have added 2 more servers
with MB and Hub Tranport Roles (VIRTUAL) and want to configure the mail flow from these new transport servers.
Can anyone help with the steps I should follow. Please note we have 1 existing Edge server in 2010 and email flow should be from Hub Transport to Edge server then from Edge to internet.
Existing environment is working fine without any issues. Main reason to do this is to virtualize the physical servers. Mailbox DB already migrated to new servers.
Thanks.
Manish Kumar MCSA, MCITP Enterprise Admin. MCTS Exchange server 2007, MCITP Virtualization Admin.

Dear Manish
Please find your answers below
For mail flow to happen through new hub transport I will make the new edge subscription from new HUB server
to Edge server. Is there any other changes I have to do ?
No other changes is required
Create a new edge subscription and then import it and run start endge sync
So when I will do create the new edge subscription then it will delete the old send connectors and will
create the new one?
IT will create old edge sync and create a new edge sync which will not make any impact on your config
Will there be any downtime while doing this activity ?
Better to do this on after production hours since definitely there will be mail delay and may delay more if you try this on production hours
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Hub Transport Server Routing

Hello All,
We have two AD sites consist of below. Exchange 2010 HT server @ Site 1 is routing mails to both Hub transport Servers @ Site 2. How do i enforce HT server @ site 1 to send all to 2010 HT server @ Site 2 without shutting down the 2007 HT.
Site 1
AD 2008 Server
Exchange 2010 HT/CAS
Exchange 2010 Mailbox
Site 2
AD 2008 Server
Exchange 2010 HT/CAS -> Send Connector source server for external domain.
Exchange 2010 Mailbox
Exchange 2007 HT/CAS

There are by default hidden internal connectors between all the Hub Transport servers so emails can be routed out-of-the-box automatically to all parts of the mail infrastructure without any additional need for manual connectors. It would be good to turn
up logging on these hidden connectors by running the cmdlet below (source is
here, section "Use the Shell to enable or disable protocol logging on the intra-organization Send connector"). This will yield if indeed mails are routed from your 2010 HT in Site1 to the 2007 HT in Site2.
If all mailboxes are moved from 2007, what is the point of keeping that server online ? For manually blocking connections - or making it so that a connection to it is not selected you could either (1) change the default IP ranges the 2007 listens on as to
avoid the 2010 HT in the first site or (2) create a separate AD site specifically for the 2007 HT server's IP (this will increase the cost of the route from the 2010 HT in Site1, making it unattractive for delivering outside mails. However please note that
these 2 methods are overkill and it would be best to see the exact reason of still keeping the 2007 box.

SBS2011 Hub Transport

I did a migration from SBS2003 to SBS2011. Everything went smoothly but when I go into exchange I see 3 receive connectors in Exchange. One that says "Default (Servername)", another that says "Windows SBS Fax Sharepoint Receive
(Servername)", and one that says "Windows SBS Internet Receive (Servername)". The company is small and we don't use the fax feature or sharepoint on the server but an reluctant to get rid of the one that says SBS Fax Sharepoint Receive.
the other two are perplexing me, they are different.
The Default (Servername) shows the IP address of the server itself and allowing receive from the entire network range. the authentication is TLS, Basic Auth, Exhange Server auth, Integrated Windows Auth. could this be left over from the migration?
Should it be deleted?
the Windows SBS Internet Receive (Servername) shows to use the IP address of the Servername and allows receive from my firewall and my Barracuda. the firewall routes mail to the barracuda appliance before relaying it to the exchange server.
Should I just have the barracuda IP address in there as a receive connector and remove the firewall address?
I know that SBS has been real finicky with the hub transport and don't want to screw up the receive when everything is working fine. just don't feel I am well protected from internal computers getting malware and it looks right now that the Hub Transport
allows relaying from any computer in the network.

Hi,
I recommend you refer to the following article to understand the receive connector:
Understanding Receive Connectors
Default Receive Connectors Created on a Hub Transport Server.When you install the Hub Transport server role, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases
the default Receive connectors don't require a configuration change. The usage type and configuration of these connectors are described in the following table.
Connector name and usage type
Configuration
Default Servername   This Receive connector accepts
connections from other Hub Transport servers and any Edge Transport servers you have.
Status: Enabled.
Protocol logging level: None.
Connector FQDN:
Servername.forestroot.extension
Local server Receive        connector bindings: All available IP addresses. The server accepts mail
received through any network adapter on the Hub Transport server.
Port: 25.
Remote server IP address        range: 0.0.0.0–255.255.255.255 IPv4 and        0000:0000:0000:0000:0000:0000:0.0.0.0–ffff:ffff:ffff:ffff:ffff:ffff:255.255.255.255
       IPv6.. The Hub Transport server accepts mail that's sent from any        IP address.
Available authentication methods:        TLS, Basic authentication, Integrated Windows authentication.
Permission groups: Exchange        users, Exchange servers, Legacy Exchange servers.
Using a Receive Connector for Anonymous Relay
In Exchange 2010, relaying is typically handled by using accepted domains. Accepted domains are configured on the Edge Transport server or Hub Transport server. The accepted domains are additionally classified as internal relay domains or external relay
domains. For more information about accepted domains, see
Understanding Accepted Domains.
You can also restrict anonymous relay based on the source of the incoming messages. This method is useful when an unauthenticated application or messaging server must use a Hub Transport server or an Edge Transport server as a relay server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Is it possible to remove 2010 Hub Transport entirely in an Exchange 2013 environment?

I'm using Exchange 2010 Edge Transport in our organization that I've recently upgraded to Exchange 2013. I like Edge Transport - along with our spam filter it is an effective and simple way to send and receive external e-mail - and I don't want
to get rid of it. But it seems like it needs a 2010 Hub Transport server to interact with.
Right now the only other Exchange 2010 Server I have left running in the organization is the one Hub Transport server that interacts with the Edge Server. Is there a way to undeploy this server too and connect the Edge Server directly to one of the
2013 Mailbox Servers? Or will this need to stay as part of the organization as a pair with Edge Transport?
I noticed mail flow was running just fine while the Hub Transport server was turned off. So it seems like it's possible. But I want to be able to undeploy it safely without hurting mail flow. Are there any links or white papers that show
how best do do this?
----------- Ron E Biggs Chief Tech Officer Entertainment Studios

Before you remove your HUB servers, make sure you re-subscribe the Edge server using the below steps:
On Edge Server:
New-EdgeSubscription -FileName "C:\EdgeSubscription.xml"
copy the file to one of the mailbox servers, and run:
New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeSubscription.xml " -Encoding Byte -ReadCount 0)) -Site
"ADSITENAME"
once completed, most of the tasks to manage/test your Edge sync will be via PowerShell, please see the below link for more details:
http://technet.microsoft.com/en-us/library/aa996865(v=exchg.150).aspx
Mohammad Saeed | MCSE 2003 | MCTS: Lync, OCS, Exchange This posting is provided "AS IS" with no warranties, and confers no rights

Service 'MSExchangeADTopology' failed to reach status 'Running' while installing Hub transport role of exchnage server 2010 sp1 on Window Server 2008 r2

Hi
Getting this error while installing hub transport role of exchange server 2010 sp1 on window server 2008 R2.
Hub Transport Role
Failed
Error:
The following error was generated when "$error.Clear();
          if ($exsSid -eq $null -or $exsSid -eq "")
          $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController
          start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController
        " was run: "Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.".
Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:25:35
Sandeep Gupta

Hi,
It might be a permission issue.
1 :
Add Manage auditing and security log Properties
Administative Tools > Local Security Policy > Local Policies > User Rights
Assignment > Manage auditing and security
Add
Exchance Servers.
2. Check Exchange Trusted Subsystem
1)Open Active Directory Users and Computers
2)Under domain name (For example contoso.com),navigate to the Builtin Container,on
the right hand side select the Administrator group,goto the properties
3)Click members tab and add Exchange Trusted Subsystem
4)Click ok twice
5)Reboot the Exchange server
6)Rerun the Exchange setup
Best Regards!

Error Installing Service Pack 3 for Exchange Server 2010 (Hub Transport)

I get the following error;
"[ERROR] Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
This is one of two Hub Transport only servers. The Client Access servers upgrade without a problem.
Thanks,
Randel

Hi,
Based on my research, to remove the error, here is a solution you can refer to:
1. Run the MsiExec.exe /X {4934d1ea-be46-48b1-8847-f1af20e892c1} to uninstall the Microsoft Full Text Indexing Engine for Exchange.
2. Manually start the World Wide Web Publishing Service and IIS Admin Service then run the setup again.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 Hub Transport

Hi Spiceheads, I thought that with Exchange 2010 mailboxes will always use the local hub transport on that server first but alas I was wrong. We need to migrate an exchange 2010 box to virtual hardware, I setup and configured a new server with the old one still live, as soon as I installed the HT role on the new server mail immediately started flowing out of it first even though every mailbox and DB was still on the old server, of course this ended up causing our mail to get flagged as spam as the spf records didn't match, thankfully this lasted all of 3 minutes while I uninstalled the role from the new server, My question is - is there a way to add the HT role but still have mail flow out of the old HT server vs the new one?
I want to add the role so I can configure all the options first, including some third party software we have...

Hi allAfter a rather heated conversation with our MSP I come to you for guidance.We've recently acquired another business and need to add two new sites plus a butt hosted server to our network. The current layout is as follows (forgive my terrible diagram):Top is our business, bottom is the one we've purchase, red indicates how the VPNs are structured. We have extensive on-premise infrastructure at the Main Office (top left) so we are planning to retire my butt hosting once our systems have been merged but in the meantime we need to be able to access their system and vice versa so I am hoping for the following:In summaryNew link from my butt hosting to the Main OfficeNew link from the alt-main office to Main officeNew link from the new "other site" to Main OfficeNow, our VPNs are controlled by our MSP, after a two week delay waiting...

Keep exchange 2007 Hub transport & CAS during migration to Exchange 2010

Hello,
during a migration from exchange 2007 to exchange 2010 is it supported to keep the old exchange 2007HUB and CAS in charge of the outside mail flow (send/receive) and OWA service.
Here is the scenario :
Actual OWA url : https : // webmail . compagnie . com (2007)
Future OWA url : https : // owa . compagnie . com 2010)
Keep the old url accessible for the users which have not be migrated to the new exchange 2010 MBX server.
Indicate to the migrated users to use the new url instead of the old one.
Keep the old hub transport server (2007) handle the mail flow (send/receive) to the outside.
At the end, when all the users will be migrated, configure the new 2010 Hub/cas to handle the mail flow (send/receive) to the outside.
Thanks a lot for your answers.
David

Thanks for your answers.
So if I have understood right, the only thing I have to take care about (in order to let the 2007 cas/hub server handle the external mail flow (on which the MX is bind) until all mailboxes are migrated) is to add the 2010 cas/hub server in :
Organization Configuration ---> send connector ---> Actual 2007 send connector --> Source server
Thanks a lot.
David
That will take care of the outbound message flow, yes.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange server 2010 - Hub Transport rule not working

Hello,
I'm trying to create a hub transport rule that blocks any incoming / outgoing email with attachments larger than 10MB with an exception of a few users.
I've followed this article https://www.simple-talk.com/sysadmin/exchange/increasing-email-size-limits-for-your-high-profile-users-in-exchange-2010/.
The send connector & receive connector is at 30MB right now and the distribution group has been made.
I added myself to the distribution group which allowed me to send a 20MB size email.
If I remove myself from the distribution group, exchange still allowed me to send the 20MB email size.
Any advise is much appreciated.
Thanks,
Daniel

Hi Daniel,
Thanks for your response.
The Hub Transport server is responsible for handling transport rules. The transport rules can't work without a Hub server.
If there are any problems with Exchange, welcome to our forum.
Best regards,
Amy
Amy Wang
TechNet Community Support

Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

Hi guys (and girls)!
Hear me up. The idea is like this:
A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
bostjanc

Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
already answered by PS CL above
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
Just install the Edge Transport Server and make sure you install ADLDS services.
as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
Where Technology Meets Talent

Service Hub Transport not started

Hi all
I have single virtual machine with Win2008EEx64 with role Domain Controller i try install Exchange 2010 with roles Mailbox,CAS and HUB When i install HUB role occur error. Service HUB Transport not start :(
Here link with error http://img7.imageshack.us/img7/1245/errorhub.jpg I can Uploading full logs install Exchange 2010. Perhaps do you have
concurrent errors ?
Small fragment log :(
"[04/18/2009 12:43:51.0403] [1] Processing component 'Bridgehead Service Configuration' (Starting Hub Transport services).
[04/18/2009 12:43:51.0403] [1] Executing 'if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }', handleError = False
[04/18/2009 12:43:51.0403] [2] Launching sub-task '$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }'.
[04/18/2009 12:43:51.0403] [2] Runspace context: Executing user: Exchange2010.local/Users/Administrator, Executing user organization: , Current organization: .
[04/18/2009 12:43:51.0403] [2] Beginning processing.
[04/18/2009 12:43:51.0403] [2] Current ScopeSet is: {Domain Read Scope: {, }, Domain Write Scope(s): {, }, Configuration Scope: {, }, Server Configuration Scope(s): , Exclusive Scope: {, }}
[04/18/2009 12:43:51.0403] [2] Resolved current organization: .
[04/18/2009 12:43:53.0840] [2] The maximum wait for the operation is set to '00:15:00'.
[04/18/2009 12:43:53.0840] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[04/18/2009 12:43:53.0840] [2] Previous service status query time is '4/18/2009 4:43:53 PM'.
[04/18/2009 12:43:53.0840] [2] Current service status query time is '4/18/2009 4:43:53 PM'.
[04/18/2009 12:43:53.0840] [2] Will wait '2000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:43:55.0934] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '2000' milliseconds.
[04/18/2009 12:43:55.0934] [2] The remaining time for service status change is '00:14:58'.
[04/18/2009 12:43:55.0934] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.
[04/18/2009 12:43:55.0934] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:45:26.0012] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:45:26.0012] [2] The remaining time for service status change is '00:13:28'.
[04/18/2009 12:45:26.0012] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:45:26.0012] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:45:26.0012] [2] Current service status query time is '4/18/2009 4:45:26 PM'.
[04/18/2009 12:45:26.0012] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:46:56.0043] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:46:56.0043] [2] The remaining time for service status change is '00:11:58'.
[04/18/2009 12:46:56.0043] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:46:56.0043] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:46:56.0043] [2] Current service status query time is '4/18/2009 4:46:56 PM'.
[04/18/2009 12:46:56.0043] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:48:26.0293] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:48:26.0293] [2] The remaining time for service status change is '00:10:28'.
[04/18/2009 12:48:26.0293] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:48:26.0293] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:48:26.0293] [2] Current service status query time is '4/18/2009 4:48:26 PM'.
[04/18/2009 12:48:26.0293] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:49:56.0465] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:49:56.0465] [2] The remaining time for service status change is '00:08:58'.
[04/18/2009 12:49:56.0465] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:49:56.0465] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:49:56.0465] [2] Current service status query time is '4/18/2009 4:49:56 PM'.
[04/18/2009 12:49:56.0465] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:51:26.0481] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:51:26.0481] [2] The remaining time for service status change is '00:07:28'.
[04/18/2009 12:51:26.0481] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:51:26.0481] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:51:26.0481] [2] Current service status query time is '4/18/2009 4:51:26 PM'.
[04/18/2009 12:51:26.0481] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:52:56.0496] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:52:56.0496] [2] The remaining time for service status change is '00:05:58'.
[04/18/2009 12:52:56.0496] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:52:56.0496] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:52:56.0496] [2] Current service status query time is '4/18/2009 4:52:56 PM'.
[04/18/2009 12:52:56.0496] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:54:26.0668] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:54:26.0668] [2] The remaining time for service status change is '00:04:28'.
[04/18/2009 12:54:26.0668] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:54:26.0668] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:54:26.0668] [2] Current service status query time is '4/18/2009 4:54:26 PM'.
[04/18/2009 12:54:26.0668] [2] Will wait '90000' milliseconds for the service 'MSExchangeTransport' to reach status 'Running'.
[04/18/2009 12:55:56.0700] [2] Service 'MSExchangeTransport' failed to reach status 'Running' on this server after waiting for '90000' milliseconds.
[04/18/2009 12:55:56.0700] [2] The remaining time for service status change is '00:02:58'.
[04/18/2009 12:55:56.0700] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='1'- Current checkpoint='1'.
[04/18/2009 12:55:56.0700] [2] Previous service status query time is '4/18/2009 4:43:55 PM'.
[04/18/2009 12:55:56.0700] [2] Current service status query time is '4/18/2009 4:55:56 PM'.
[04/18/2009 12:56:10.0246] [2] Generated Watson report with dump for the service MSExchangeTransport
[04/18/2009 12:56:10.0246] [2] [ERROR] Unexpected Error
[04/18/2009 12:56:10.0246] [2] [ERROR] Service 'MSExchangeTransport' failed to reach status 'Running' on this server.
[04/18/2009 12:56:10.0262] [2] Ending processing.
[04/18/2009 12:56:10.0262] [1] The following 1 error(s) occurred during task execution:
[04/18/2009 12:56:10.0262] [1] 0. ErrorRecord: Service 'MSExchangeTransport' failed to reach status 'Running' on this server.
[04/18/2009 12:56:10.0262] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeTransport' failed to reach status 'Running' on this server.
[04/18/2009 12:56:10.0278] [1] [ERROR] The execution of: "$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }", generated the following error: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".
[04/18/2009 12:56:10.0278] [1] [ERROR] Service 'MSExchangeTransport' failed to reach status 'Running' on this server.
[04/18/2009 12:56:10.0278] [1] [WARNING] <<< Setup failed to execute a task. Dumping all variables.... >>>
[04/18/2009 12:56:10.0278] [1] $ =
[04/18/2009 12:56:10.0278] [1] ? = True
[04/18/2009 12:56:10.0278] [1] ^ =
[04/18/2009 12:56:10.0278] [1] _ =
[04/18/2009 12:56:10.0278] [1] addressSpace = MOBILE:*
[04/18/2009 12:56:10.0278] [1] agent =
[04/18/2009 12:56:10.0278] [1] agentAssembly = C:\Program Files\Microsoft\Exchange Server\V14\bin\Microsoft.Exchange.MobileDriver.dll
[04/18/2009 12:56:10.0278] [1] agentFactory = Microsoft.Exchange.TextMessaging.MobileDriver.TextMessagingDeliveryAgentFactory
[04/18/2009 12:56:10.0278] [1] agentName = Text Messaging Delivery Agent
[04/18/2009 12:56:10.0278] [1] args =
[04/18/2009 12:56:10.0278] [1] assembly = Microsoft.Exchange.ProvisioningAgent.dll
[04/18/2009 12:56:10.0278] [1] classFactory = Microsoft.Exchange.ProvisioningAgent.AdminLogAgentClassFactory
[04/18/2009 12:56:10.0278] [1] comClassFile = C:\Program Files\Microsoft\Exchange Server\V14\bin\Monitoring\x86\DiagnosticCmdletController.dll
[04/18/2009 12:56:10.0278] [1] ConfirmPreference = None
[04/18/2009 12:56:10.0278] [1] connector = Text Messaging Delivery Agent Connector
[04/18/2009 12:56:10.0278] [1] connectorName = Text Messaging Delivery Agent Connector
[04/18/2009 12:56:10.0278] [1] ConsoleFileName =
[04/18/2009 12:56:10.0278] [1] DebugPreference = SilentlyContinue
[04/18/2009 12:56:10.0278] [1] deliveryProtocol = MOBILE
[04/18/2009 12:56:10.0278] [1] dllFile = C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSMIME.dll
[04/18/2009 12:56:10.0278] [1] Error = System.Collections.ArrayList
[04/18/2009 12:56:10.0278] [1] ErrorActionPreference = Continue
[04/18/2009 12:56:10.0278] [1] ErrorView = NormalView
[04/18/2009 12:56:10.0278] [1] ExchangePropertyContainer = Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer
[04/18/2009 12:56:10.0278] [1] ExecutionContext = System.Management.Automation.EngineIntrinsics
[04/18/2009 12:56:10.0278] [1] exsSid = S-1-5-21-3189551677-1878205415-1818128433-1104
[04/18/2009 12:56:10.0278] [1] false = False
[04/18/2009 12:56:10.0278] [1] file = microsoft.exchange.protectedservicehost.exe.config
[04/18/2009 12:56:10.0278] [1] FormatEnumerationLimit = 4
[04/18/2009 12:56:10.0278] [1] fullPath = C:\Program Files\Microsoft\Exchange Server\V14\bin\microsoft.exchange.protectedservicehost.exe
[04/18/2009 12:56:10.0278] [1] HOME = C:\Users\Administrator
[04/18/2009 12:56:10.0278] [1] Host = System.Management.Automation.Internal.Host.InternalHost
[04/18/2009 12:56:10.0278] [1] input =
[04/18/2009 12:56:10.0278] [1] installedAgents =
[04/18/2009 12:56:10.0278] [1] InternalPowerShellUrl = https://WIN-EMFQIRKOWAL.Exchange2010.local/powershell
[04/18/2009 12:56:10.0278] [1] journalAgent =
[04/18/2009 12:56:10.0278] [1] localSite = Exchange2010.local/Configuration/Sites/Default-First-Site-Name
[04/18/2009 12:56:10.0278] [1] localSiteEdgeSyncConfig =
[04/18/2009 12:56:10.0278] [1] localSiteName = Default-First-Site-Name
[04/18/2009 12:56:10.0278] [1] MaximumAliasCount = 4096
[04/18/2009 12:56:10.0278] [1] MaximumDriveCount = 4096
[04/18/2009 12:56:10.0278] [1] MaximumErrorCount = 256
[04/18/2009 12:56:10.0278] [1] MaximumFunctionCount = 4096
[04/18/2009 12:56:10.0278] [1] MaximumHistoryCount = 64
[04/18/2009 12:56:10.0278] [1] MaximumVariableCount = 4096
[04/18/2009 12:56:10.0278] [1] mflFilePath = C:\Program Files\Microsoft\Exchange Server\V14\bin\en\Exchange.MFL
[04/18/2009 12:56:10.0278] [1] mofFilePath = C:\Program Files\Microsoft\Exchange Server\V14\bin\Exchange.MOF
[04/18/2009 12:56:10.0278] [1] MyInvocation =
[04/18/2009 12:56:10.0278] [1] NestedPromptLevel = 0
[04/18/2009 12:56:10.0278] [1] null =
[04/18/2009 12:56:10.0278] [1] organizationConfig = Exchange2007
[04/18/2009 12:56:10.0278] [1] OutputEncoding = System.Text.ASCIIEncoding
[04/18/2009 12:56:10.0278] [1] PID = 2380
[04/18/2009 12:56:10.0278] [1] ProgressPreference = Continue
[04/18/2009 12:56:10.0278] [1] PSBoundParameters = System.Collections.Generic.Dictionary`2[System.String,System.Object]
[04/18/2009 12:56:10.0278] [1] PSCmdlet =
[04/18/2009 12:56:10.0278] [1] PSCulture = en-US
[04/18/2009 12:56:10.0278] [1] PSEmailServer =
[04/18/2009 12:56:10.0278] [1] PSHOME = C:\Windows\system32\WindowsPowerShell\v1.0\
[04/18/2009 12:56:10.0278] [1] PSMaximumReceivedDataSizePerCommandMB = 2047
[04/18/2009 12:56:10.0278] [1] PSMaximumReceivedObjectSizeMB = 2047
[04/18/2009 12:56:10.0278] [1] PSSessionApplicationName = wsman
[04/18/2009 12:56:10.0278] [1] PSSessionConfigurationName = http://schemas.microsoft.com/powershell/Microsoft.PowerShell
[04/18/2009 12:56:10.0278] [1] PSTypePath =
[04/18/2009 12:56:10.0278] [1] PSUICulture = en-US
[04/18/2009 12:56:10.0278] [1] PSVersionTable = System.Collections.Hashtable
[04/18/2009 12:56:10.0278] [1] PWD = C:\Windows\Temp\ExchangeSetup
[04/18/2009 12:56:10.0278] [1] regsvr = C:\Windows\system32\regsvr32.exe
[04/18/2009 12:56:10.0278] [1] regSvr32WOW = C:\Windows\sysWOW64\regsvr32.exe
[04/18/2009 12:56:10.0278] [1] ReportErrorShowExceptionClass = 0
[04/18/2009 12:56:10.0278] [1] ReportErrorShowInnerException = 0
[04/18/2009 12:56:10.0278] [1] ReportErrorShowSource = 1
[04/18/2009 12:56:10.0278] [1] ReportErrorShowStackTrace = 0
[04/18/2009 12:56:10.0278] [1] RoleBinPath = C:\Program Files\Microsoft\Exchange Server\V14\Bin
[04/18/2009 12:56:10.0278] [1] RoleCustomerFeedbackEnabled = True
[04/18/2009 12:56:10.0278] [1] RoleDatacenterPath = C:\Program Files\Microsoft\Exchange Server\V14\Datacenter
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointABCHContactService = <ServiceEndpoint><Url>http://pvt-contacts.msn.com/abservice/abservice.asmx</Url></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointDomainPartnerManageDelegation = <ServiceEndpoint><Url>https://domains.live.com/service/managedelegation.asmx</Url></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointLiveFederationDeprecatedMetadata = <ServiceEndpoint><Url>https://nexus.passport.com/FederationMetadata/2006-02/FederationMetadata.xml</Url></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointLiveGetUserRealm = <ServiceEndpoint><Url>https://login.live.com/GetUserRealm.srf</Url></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointLiveRmsCertificationService = <ServiceEndpoint><Url>https://licensing.drm.microsoft.com/licensing/licensing.asmx</Url><CertificateSubjectName>TO BE FILLED IN </CertificateSubjectName></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointLiveRmsLicensingService = <ServiceEndpoint><Url>https://certification.drm.microsoft.com/certification/certification.asmx</Url><CertificateSubjectName>TO BE FILLED IN </CertificateSubjectName></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointLiveRmsPublishingService = <ServiceEndpoint><Url>https://licensing.drm.microsoft.com/licensing/publish.asmx</Url><CertificateSubjectName>TO BE FILLED IN </CertificateSubjectName></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointLiveServiceLogin2 = <ServiceEndpoint><Url>https://login.live.com/RST2.srf</Url></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDatacenterServiceEndpointRmsPremiseAuthenticationCertificate = <ServiceEndpoint><CertificateSubjectName>CN=exchangelabs.live-int.com, OU=Exchange, O=Microsoft, L=Redmond, S=Washington, C=US</CertificateSubjectName></ServiceEndpoint>
[04/18/2009 12:56:10.0278] [1] RoleDomainController = WIN-EMFQIRKOWAL.Exchange2010.local
[04/18/2009 12:56:10.0278] [1] RoleFqdnOrName = WIN-EMFQIRKOWAL.Exchange2010.local
[04/18/2009 12:56:10.0278] [1] RoleInstallationMode = Install
[04/18/2009 12:56:10.0278] [1] RoleInstallPath = C:\Program Files\Microsoft\Exchange Server\V14\
[04/18/2009 12:56:10.0278] [1] RoleInvocationID = 20090418-1525100043514005697
[04/18/2009 12:56:10.0278] [1] RoleIsAdminToolsRoleInstalled = True
[04/18/2009 12:56:10.0278] [1] RoleIsDatacenter = False
[04/18/2009 12:56:10.0278] [1] RoleLanguagePacksPath = C:\1\
[04/18/2009 12:56:10.0278] [1] RoleLoggedOnUser = EXCHANGE2010\Administrator
[04/18/2009 12:56:10.0278] [1] RoleLoggingPath = C:\Program Files\Microsoft\Exchange Server\V14\Logging
[04/18/2009 12:56:10.0278] [1] RoleNetBIOSName = WIN-EMFQIRKOWAL
[04/18/2009 12:56:10.0278] [1] RolePreviousVersion =
[04/18/2009 12:56:10.0278] [1] RoleProductPlatform = amd64
[04/18/2009 12:56:10.0278] [1] RoleRoleName = BridgeheadRole
[04/18/2009 12:56:10.0278] [1] RoleRoles = AdminToolsRole
[04/18/2009 12:56:10.0278] [1] RoleSetupLoggingPath = C:\ExchangeSetupLogs
[04/18/2009 12:56:10.0278] [1] RoleStartTransportService = True
[04/18/2009 12:56:10.0278] [1] RoleTargetVersion = 14.00.0482.020
[04/18/2009 12:56:10.0278] [1] RoleUpdatesDir = C:\1\Updates
[04/18/2009 12:56:10.0278] [1] server = WIN-EMFQIRKOWAL
[04/18/2009 12:56:10.0278] [1] ShellId = Microsoft.PowerShell
[04/18/2009 12:56:10.0278] [1] StackTrace =
[04/18/2009 12:56:10.0278] [1] this =
[04/18/2009 12:56:10.0278] [1] true = True
[04/18/2009 12:56:10.0278] [1] user = Exchange2010.local/Users/Administrator
[04/18/2009 12:56:10.0278] [1] vdirName = PowerShell
[04/18/2009 12:56:10.0278] [1] VerbosePreference = SilentlyContinue
[04/18/2009 12:56:10.0278] [1] w3svc = System.ServiceProcess.ServiceController
[04/18/2009 12:56:10.0278] [1] WarningPreference = Continue
[04/18/2009 12:56:10.0278] [1] wasRunning = True
[04/18/2009 12:56:10.0278] [1] WhatIfPreference = False
[04/18/2009 12:56:10.0278] [1] WSManMaxRedirectionCount = 5
[04/18/2009 12:56:10.0278] [1] [WARNING] <<< Variable dumping complete. >>
[04/18/2009 12:56:10.0309] [1] Setup is halting task execution because of one or more errors in a critical task.
[04/18/2009 12:56:10.0309] [1] Finished executing component tasks.
[04/18/2009 12:56:10.0371] [1] Ending processing.
[04/18/2009 13:07:51.0090] [0] [WARNING] Setup has made changes to operating system settings that require a reboot to take effect. Please reboot this server prior to placing it into production.
[04/18/2009 13:07:51.0153] [0] End of Setup
[04/18/2009 13:07:51.0153] [0] **********************************************

Hi
I tested your problem in test lab and when desable ip v6 on network connection Transport service will take long time to start.
Try again after enable ipv6.
BTW-Also i was found good article for similar case with your case 
http://www.exchangeinbox.com/article.aspx?i=111
RegardsChinthaka
-If you think my thread is helpful for you, Please vote.

Exchange 2008 w/o Edge or Hub transport servers

Similar Messages

Maybe you are looking for