This subject has been discussed several times, I know... but I just need a few pointers to cover what I am doing, google is practicing very dark humor on me... Current Scenario: Mail.company.com is a stand-alone exchange server , DNS, DHCP and PDC (bad idea I know, but that's how I found this when I got the job) , it has the certificate for the mail.company.com name as well. Running on it is Exchange 2007 and Windows 2003 server. Work done so far: I Installed Windows 2008 R2 on 3 servers, installed Exchange 2010 (mailbox roles and hub transport) on the first 2 , and on the third installed the hub transport only to make it the witness server. Now the DAG is made, I have 2 databases, cross mounted and seeded , healthy, sent test emails to find it directly duplicated on both OWAs ... Questions: I am trying to migrate everything from my 2007 exchange to the new setup DAG... but I need to keep the mail.company.com as the public name.. - Where do I configure the hub transport stuff? (like receiver connector, smtp connector and OWA settings?) , do I do it on all 3 servers? or just the witness server? - How do I take the name mail.company.com to the new environment, and who will get it? the witness, one of the DAGs ... I imported the certificate to all 3 ... but not sure where this will get me.. - related to above questions: who gets the ip address that I have the mx record IP natted to? I know I am almost done, but I really need your help on bringing it home here...

Hello, where have you installed the 2010 Client Access servers? Please be aware that load balancing with a CAS array on the DAG members is only supported in a scenario with a hardware load balancer. With Windows NLB you have to separate the CAS from the DAG. Most of the Hub Transport configuration (send connectors for example) is stored in Active Directory and is replicated to the other HT servers automatically. Greetings, Toni

Hello, where have you installed the 2010 Client Access servers? Please be aware that load balancing with a CAS array on the DAG members is only supported in a scenario with a hardware load balancer. With Windows NLB you have to separate the CAS from the DAG. Most of the Hub Transport configuration (send connectors for example) is stored in Active Directory and is replicated to the other HT servers automatically. Greetings, Toni Hey Toni, I have the client access installed on both DAG servers (not the witness), should i install it on only one? is it safe to simply uninstall this role from one of them now? from your comment on seperating the CAS from DAG , does this mean I should have it on the witness server, or should I simply have it on the exchange 2007 maybe (this solves the naming issue for me) with it reading the DB from the DAG? Cheers Wassim

Hello, for real high availability on Exchange side you should have 4 servers: 2x DAG 2x CAS/HT The problem with 3 servers is: it's good to have a DAG for high availability but with only one CAS you'll get problems when this CAS goes down because your clients are connecting to the CAS so they won't be able to connect anymore. Have you done any configuration on the new CAS? If no you can safely uninstall the CAS role from the server. Greetings, Toni

Hello, for real high availability on Exchange side you should have 4 servers: 2x DAG 2x CAS/HT The problem with 3 servers is: it's good to have a DAG for high availability but with only one CAS you'll get problems when this CAS goes down because your clients are connecting to the CAS so they won't be able to connect anymore. Have you done any configuration on the new CAS? If no you can safely uninstall the CAS role from the server. Greetings, Toni Well all the Exchange 2010 servers are in beta/test mode... so I can uninstall and reinstall anything I want, it will not affect my users, as they are still using the exchange 2007 I am trying to migrate from.... Once all is done I can maybe configure the old Exchange 2007 as the secondary CAS... So the CAS is the same as the witness server? or does this have to be another CAS only server?

Hello, place the FSW on one of your CAS/HT servers since the recommendation of Microsoft is to put the FSW on a HT server. You can configure a CAS array with only one CAS server. The advantage is that you have the name of your array provided for your clients so you can just simply add the second CAS and you don't have to change anything on the clients. Greetings, Toni

Hello, place the FSW on one of your CAS/HT servers since the recommendation of Microsoft is to put the FSW on a HT server. You can configure a CAS array with only one CAS server. The advantage is that you have the name of your array provided for your clients so you can just simply add the second CAS and you don't have to change anything on the clients. Greetings, Toni Hey Toni, Ok I will uninstall the client access role from the 2 DAG servers, and install it on the HT/FSW server... this will make the DAG servers running the DB only, and one server acting as HT , FSW and CAS ... This will take time as I am installing exchange 2010 SP1 on all of them (some of my clients use Outlook 2011 , it only supports 2010 with SP1). But the main issue is the transition, how do I move the name from 2007 to FSW ? downtime and DB move (my DB size is around 300 GB) Thanks by the way for your replies so far! Cheers Wassim

But the main issue is the transition, how do I move the name from 2007 to FSW ? downtime and DB move (my DB size is around 300 GB) Hi Wassim, I would suggest you read this Technet document first: Exchange 2007 - Planning Roadmap for Upgrade and Coexistence http://technet.microsoft.com/en-us/library/dd638158.aspx You move the mailboxes from Exchange 2007 to Exchange 2010 rather than move the DB. Frank Wang