Dear all, I have this scenario and need guidance on how to go about it. 1. I have three Exchange server 2007 in my environment, namely MX2, MX3 and Edge MX2 is the first exchange server deployed in the environment, running on windows server 2003 R2 ent. and Exchange server 2007 SP1 build 240.6. MX3 is the second Exchange server running on windows server 2008 R2 ent, and Exchange server 2007 SP3 version 8.3 Edge, this routes to and fro external Mails throu MX2, running on windows server 2003R2 standard R2 and exchange server 2007 SP1 build 240.6 NOW: I want to upgrade MX2 and Edge from SP1 to SP3, what can be the best practice to follow, in order to have a smooth upgrade. Thanks in advance. Michael

Best Practices is having all the Exchange Servers in the Same Service Pack -- So have MX2, and MX3 Upgraded to SP3 And then the Edge to SP3 If Possible Apply the latest Roll up As well So that you can relax in the future.Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you

The order for upgrade is below. Client AccessHub TransportUnified MessagingMailbox The Edge Transport server role can be upgraded at any time. However, we recommend upgrading the Edge Transport server role either before or after all other server roles are upgraded. However since you already have mx3 on sp3 it really doesnt matter the order. Go ahead and do mx2 then your edge. Also dont forget to get the latest rollup 7 after you install sp3. Update Rollup 7 for Exchange 2007 SP3 http://www.microsoft.com/en-us/download/details.aspx?id=29426James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi Satheshwaran I ve noticed that since I installed MX3 with SP3, while MX2 and egde still on SP1 mails both local and external are delaying to be delivered, and also that the status of MSExchange Transport Service is saying starting on MX2 and NOT started. when I try Upgrading MX2, the setup is failing to stop MSExchange Transport Service. I am stuck kindly Help.

Hi James I ve noticed that since I installed MX3 with SP3, while MX2 and egde still on SP1 mails both local and external are delaying to be delivered, and also that the status of MSExchange Transport Service is saying starting on MX2 and NOT started. when I try Upgrading MX2, the setup is failing to stop MSExchange Transport Service. I am stuck kindly Help.

hi all I ve noticed that since I installed MX3 with SP3, while MX2 and egde still on SP1 mails both local and external are delaying to be delivered, and also that the status of MSExchange Transport Service is saying starting on MX2 and NOT started. when I try Upgrading MX2, the setup is failing to stop MSExchange Transport Service. I am stuck kindly Help.

WIth upgrades work from the outside in. Therefore as you have Edge, that should be done first. Then do the other two. Until the ugprade is completed on both servers I wouldn't trust any results. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

On mx2 when you say the transport service is stuck on starting, you mean when you try to perform the upgrade or it won't start period? If it's not starting have you rebooted? Have you mucked around with setting the static rpc port for the transport service in the registry? Need to know whether you mean its not starting during the upgrade or not starting at all.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

hi all The service is hunging before the Upgrade, I have also noted that in the Drive:\Exchange\TransportRoles\Data\Queue, there are more logs accumulating and once I do repair and defragment the database, the service is able to start for a short time then stops again once the logs and the Database reaches more than 1GB. Am experiencing this before upgrading MX2 and Edge I am wondering whether MX3 is contributing to this or not. Since MX3 is the second Mail server as I explained above, I appreciate your usual help. Michael

hi all The service is hunging before the Upgrade, I have also noted that in the Drive:\Exchange\TransportRoles\Data\Queue, there are more logs accumulating and once I do repair and defragment the database, the service is able to start for a short time then stops again once the logs and the Database reaches more than 1GB. Am experiencing this before upgrading MX2 and Edge I am wondering whether MX3 is contributing to this or not. Since MX3 is the second Mail server as I explained above, I appreciate your usual help. Michael

That is the expected behavior to shutdown the service if your system is queueing to avoid running out of disk space. Go ahead and run the repair on the queue db so the transport can at least start, then kick off the sp upgrade right away. I would also upgrade your edge at the same time since you are not getting emails anyways.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

That is the expected behavior to shutdown the service if your system is queueing to avoid running out of disk space. Go ahead and run the repair on the queue db so the transport can at least start, then kick off the sp upgrade right away. I would also upgrade your edge at the same time since you are not getting emails anyways.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hi All, I Appreciate guys, all your suggestion helped me and gave me a clue of what might have been causing this service not starting. One of my user who was fired,sent a very big document that was failing to be routed and hence affected the transport service from functioning properly. after removing this email every thing started working fine Thanks once again