We have a single box with multiple roles installed and are moving to HA(Clustered mailbox) and NLB HUB/CAS Thanks for the above solution , i have a different Question now . I will be configuring NLB cluster for HUB & CAS . NLB will Windows 2003 R2 with Exchange 2007. I would like to know ---which one should be installed first? NLB or install HUB & CAS role ? ---Can i import the existing certificate from the standalone server which has SAN enabled 3rd party certificate to the new NLB box ? and finally how can we have smooth migration without any downtime while transitioning from standalone HUB to NLB My Plan is once i have NLB up , i will change NATed IP on my ASA to point to the NLB Virtual IP (to change MX to NLB HUB & also OWA IP URL will be changed simultaneously) Then will create new send & recieve connector on each of the HUB Server Node. I have around 1500 users i cannot move all of the users in one shot , how do i manage the users on the standalone box to be able to send/recieve mails even after changing the MX to the NLB Virtual IP? Thanks & Appreciate all the replies Raghu

Hi I would first install and configure the NLB and test so it works like it should When you're done with test and it works like you want it continue with installing CAS and HUB on it Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Jonas, How about the Certificates & how we have a smooth migration from single box to Multiple boxes .. does my plan above sounds good ?

Certificate names need to be planned very carefully YOu will need at least: owa.company.com autodiscover.company.com legacy.company.com nlbname.domain.com This certificate should you use on your legacy server also, and using coexistence.. Take a look at this link http://technet.microsoft.com/en-us/library/aa998186.aspx Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Here is a step by step on CAS NLB setup on Exch 2007. http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/load-balancing-exchange-2007-client-access-servers-windows-network-technology-part1.html (3 part article)Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

I do already have the certificate which is being used on my standalone box with SAN for autodiscover.external.domain,owa.external.domain,owa.internal.domain,autodiscover.internal.domain . Can i use the same certificate for the NLB Cluster by adding the NLB Cluster FQDN ?

I do already have the certificate which is being used on my standalone box with SAN for autodiscover.external.domain,owa.external.domain,owa.internal.domain,autodiscover.internal.domain . Can i use the same certificate for the NLB Cluster by adding the NLB Cluster FQDN ? Yes you can, no problemsJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

yeah, that should work if you include the CAS NLB Cluster fqdn into the names you have now.Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

Now into the actual migration .. how do i make the new NLB HUB/CAS as the primary server , cos once i have Clustered mailbox configured and NLB Cluster is running i have to migrate or move the users from the standalone exchange 2007 box(Standalone box too has HUB and CAS Configured) to the clustered mailbox server. I cannot move all the users at once so i'm planning to move group of 30 to 50 users/mailbox to the new clustered server. Before moving the users i have to get my act right by configuring NLB Cluster as my primary transport server which will recieve & send all the mails to & from my domain .

Make sure you create the appropriate receive connectors And for NLB you can see the cluster like "active/active" while MBX is "active/passive" And also, move a test user and have a checklist with all the necessary checkpoints that should work.Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

ok thats great .. so before moving user i will have my CAS server uninstalled or stop the CAS service on the standalone box , then how would the users who have their mailbox on the standalone box send the mails.. can we configure the send connector on the standalone to use smarthost as the NLB Cluster address ?

You need to have CAS/HUB installed into your environment and then install MBX with CCR and have it tested before moving any production users You setup a send connector, they are still in same organization for what i've interpreted so that will not be a problem. So don't stop anything before everything is moved and up and running Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

see its like this , i have Exchange 2007 standalone box with MBX,HUB and CAS roles installed . For the New boxes will have clustered MBX and NLB cLuster HUB and CAS .. Now i have CLustered MBX and NLB CLuster configured . Now i want OWA users to connect to NLB CAS rather than old box . I will change the MX to point to NLB Clustered IP . I hope you understood this , after which i will be moving the users by group . i want users on the clustered MBX and standalone MBX server to use common OWA URL ... yes its in the same org Hope im not confusing

Ok, I see Then I have 2 links you should take a look at I published a while ago a post about coexistence between 2003 and 2007, I think it will almost be same, some steps are different. http://www.testlabs.se/blog/2010/02/04/owaactivesync-with-exchange-2007-coexist-with-exchange-2003/ And also a coexistence link from technet http://technet.microsoft.com/en-us/library/aa998186%28EXCHG.80%29.aspxJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi Raqhu, Jonas gave some very good information, if you have some issue when you do the migration, please post here, we could do more research for you. Regards! :) Gavin