I have two offices on either side of the country (one main, one branch), sharing the same Domain via a VPN. I want to install Exchange 2010 on the branch office domain controller, everyone there currently uses Outlook Anywhere to connect to the exchange 2007 server at the main office. What server roles do I need? All I want to do is move the branch office users mailboxes to their local server, for them to be able to email large files to themselves or local clients without it having to go back over the VPN to the main office first. Do I need the client access role if its installed on the other server? Can they just use the webmail interface at the main office to view their emails if they need to, or will it only work for mailboxes on the server with the Client role installed? Do I need hub transport as well? Regards, Alex

If you have Exchange 2007 in one office then you will have to install all three roles on the Exchange 2010 server. You can't do anything else. You are also going to have to expose that server to the Internet for OWA access as Exchange 2007 doesn't proxy to an older version of Exchange. Even if you already had Exchange 2010, you would still need all three roles in that location, due to the way that Exchange works. Therefore deploy the server, it will need its own unique URL for OWA, Outlook Anywhere etc. That will mean your SSL certificate will need to be replaced on both servers (As most SSL providers will not allow two certificates with the same host name, and you need Autodiscover in the certificate). Do ensure that you get your AD sites and services configured correctly and use an RPC CAS Array from the start, otherwise you are setting yourself up for a world of pain in a few years time. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

DO I need a CAS array if I won't be utilising DAG, as they are both standard editions? Can I use a self signed SSL on the 2nd Exchange (at least in the shortterm)? They will rarely need to use webmail or Outlook Anywhere. It would be a hassle revoking the SSL at the main branch. Regards, Alex

If you have Exchange 2007 in one office then you will have to install all three roles on the Exchange 2010 server. You can't do anything else. You are also going to have to expose that server to the Internet for OWA access as Exchange 2007 doesn't proxy to an older version of Exchange. Even if you already had Exchange 2010, you would still need all three roles in that location, due to the way that Exchange works. Therefore deploy the server, it will need its own unique URL for OWA, Outlook Anywhere etc. That will mean your SSL certificate will need to be replaced on both servers (As most SSL providers will not allow two certificates with the same host name, and you need Autodiscover in the certificate). Do ensure that you get your AD sites and services configured correctly and use an RPC CAS Array from the start, otherwise you are setting yourself up for a world of pain in a few years time. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I have two offices on either side of the country (one main, one branch), sharing the same Domain via a VPN. I want to install Exchange 2010 on the branch office domain controller, everyone there currently uses Outlook Anywhere to connect to the exchange 2007 server at the main office. Hello, do you have the option to install Exchange 2010 on a member server of the branch office? It's not a best practise to install Exchange on a domain controller. Greetings, Toni

I have two offices on either side of the country (one main, one branch), sharing the same Domain via a VPN. I want to install Exchange 2010 on the branch office domain controller, everyone there currently uses Outlook Anywhere to connect to the exchange 2007 server at the main office. Hello, do you have the option to install Exchange 2010 on a member server of the branch office? It's not a best practise to install Exchange on a domain controller. Greetings, Toni Completely missed that. If you installExchangee on to a domaincontrollerr then it is going to have an impact on the other Exchange server. Exchange will only use thedomainn controller that it is installed on. If you have other Exchange servers then they will ONLY use that same domain controller as well, which will mean Exchange in your main office will only use the domain controller in the branch office - and therefore there will be performance issues. You need to put Exchange in the branch office on a member server, not the domain controller. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

DO I need a CAS array if I won't be utilising DAG, as they are both standard editions? Can I use a self signed SSL on the 2nd Exchange (at least in the shortterm)? They will rarely need to use webmail or Outlook Anywhere. It would be a hassle revoking the SSL at the main branch. Regards, Alex I implement a RPC CAS array on all Exchange deployments, whether or not they are using a DAG. I don't consider it to be optional. The reason is that if you have mailboxes on that server and then move them to another server so that you can remove thefirstt server, Outlook will NOT update to use that second server, because the first server is still valid. The CAS array is the only way to get the mailboxes to useanotherr server. An RPC CAS Array takes less than two minutes to setup, but can save you a LOT of work later on. I wouldn't even consider using the self signed certificate. It isn't supported for use with Outlook Anywhere and can cause you problems with certificate prompts in Outlook. Again you will save yourself a lot of work and headache from the end users if you deploy Exchange correctly right from the start. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

DO I need a CAS array if I won't be utilising DAG, as they are both standard editions? Can I use a self signed SSL on the 2nd Exchange (at least in the shortterm)? They will rarely need to use webmail or Outlook Anywhere. It would be a hassle revoking the SSL at the main branch. Regards, Alex I implement a RPC CAS array on all Exchange deployments, whether or not they are using a DAG. I don't consider it to be optional. The reason is that if you have mailboxes on that server and then move them to another server so that you can remove thefirstt server, Outlook will NOT update to use that second server, because the first server is still valid. The CAS array is the only way to get the mailboxes to useanotherr server. An RPC CAS Array takes less than two minutes to setup, but can save you a LOT of work later on. I wouldn't even consider using the self signed certificate. It isn't supported for use with Outlook Anywhere and can cause you problems with certificate prompts in Outlook. Again you will save yourself a lot of work and headache from the end users if you deploy Exchange correctly right from the start. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi, You If You Are Planning For Exchange 2010 then you must install Cas Server Role+Global Catalog Server in Each Active Directory Site. As Exchange 2010 client Connects To Cas Server instead of Mailbox Server As in Exchange 2007. If You Wont Install CAS Role In Branch Site they might face connectivity Issue. Regards Sushant