Hello, I want to add more domains for email sending via Exchange server but my clients don't want to host them on Windows. They are working fine on cPanel. What'll be the best practice to add extra domains in Exchange server and websites still hosted on remote servers? Thanks HLNixGurus

Version of Exchange would be helpful here. You don't have to host the web site on Exchange. Where the web site is located is completely immaterial. Therefore you just add the domains to Exchange in the usual way and then change the MX records for the domain to point at the Exchange server. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hello Agree with Simon you no need to have hosting website for exchange just make a MX record with that domain from your ISP and point the public ip to your exchange server. Apart from this you need to add that domain in your Exchange server as accepted domains create a email policy for those users mailbox who will be using this domain. Thanks Mhussain

Version of Exchange would be helpful here. You don't have to host the web site on Exchange. Where the web site is located is completely immaterial. Therefore you just add the domains to Exchange in the usual way and then change the MX records for the domain to point at the Exchange server. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me. I have Exchange 2010 SP1. Where I need to put new domain related entries? I can setup MX records easily. Do I need to put that new domain in DNS of Exchange Machine?NixGurus

Hi You will need to add the smtp domain into accepted domain, and also provide the mailboxes with the appropriate emailaddresses accordingly to the new smtp domain http://technet.microsoft.com/en-us/library/bb124423.aspx Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

Hi You will need to add the smtp domain into accepted domain, and also provide the mailboxes with the appropriate emailaddresses accordingly to the new smtp domain http://technet.microsoft.com/en-us/library/bb124423.aspx Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82 I added the domain in Accepted domain. But when I try to add the mailbox there's no such domain available in drop down. Is there any other place where I need to input the new domain? Or is there any service which need to be restarted ? EDIT: I also added Email Address Policy but still I am unable to create account with another domain. NixGurus

Hi Are you referring to the user account or the emailaddress? Regarding the email address policy you can check the link below http://technet.microsoft.com/en-us/library/bb232171.aspx Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

Someone has made the mistake of thinking the drop down list in the user account creation is connected to email addresses. It has nothing to do with it. That is the UPN, and is a DOMAIN setting. Nothing to do with email. The fact that it may well be the same as your existing domains will be a coincidence, because the Windows DNS name and your Exchange server's domain name are the same. If your domain was just domain.local, then that is all that would appear in that list. Don't confuse the WINDOWS domain with the SMTP/EMAIL domain in Exchange. They can be the same, they can be different. Therefore create the user account as normal, then use email address policy to control the email address that the user gets. If you want the user to be able to login to WINDOWS with their email address, then you need to add the domain as an additional UPN, which is a WINDOWS setting, configured in Active Directory, not Exchange. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Someone has made the mistake of thinking the drop down list in the user account creation is connected to email addresses. It has nothing to do with it. That is the UPN, and is a DOMAIN setting. Nothing to do with email. The fact that it may well be the same as your existing domains will be a coincidence, because the Windows DNS name and your Exchange server's domain name are the same. If your domain was just domain.local, then that is all that would appear in that list. Don't confuse the WINDOWS domain with the SMTP/EMAIL domain in Exchange. They can be the same, they can be different. Therefore create the user account as normal, then use email address policy to control the email address that the user gets. If you want the user to be able to login to WINDOWS with their email address, then you need to add the domain as an additional UPN, which is a WINDOWS setting, configured in Active Directory, not Exchange. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me. Let me explain the situation. I have a Web Hosting company. I want to offer paid Exchange Mail boxes to clients. I never worked with Exchange nor installed before. This is my first try with exchange and the default domain is working fine. I can send / receive email easily. For customers I'll need to add customer's domain as SMTP domain and provide them customer1@customerdomain.tld I hope this will shed some lights on situation.NixGurus

Hosted Exchange is a completely different issue altogether. It has to be licenced in a different way, setup in a different way and managed in a different way. You cannot just take a regular Exchange server and use it for hosted Exchange. Having no knowledge of Exchange and trying to setup a hosted platform is like trying to drive and the first thing you get behind the wheel is a coach. The learning curve is straight up. From a pure financial aspect, unless you are going to put at least 10,000 mailboxes on to the platform, then it is simply not financially viable. It is a lot better to use a white label provider which you resell. Exchange isn't a POP3 mailbox system that you can setup in an afternoon. The parts aren't available off the shelf, they require custom development. You will have to use scripts to manage it, there is limited or no GUI. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hosted Exchange is a completely different issue altogether. It has to be licenced in a different way, setup in a different way and managed in a different way. You cannot just take a regular Exchange server and use it for hosted Exchange. Having no knowledge of Exchange and trying to setup a hosted platform is like trying to drive and the first thing you get behind the wheel is a coach. The learning curve is straight up. From a pure financial aspect, unless you are going to put at least 10,000 mailboxes on to the platform, then it is simply not financially viable. It is a lot better to use a white label provider which you resell. Exchange isn't a POP3 mailbox system that you can setup in an afternoon. The parts aren't available off the shelf, they require custom development. You will have to use scripts to manage it, there is limited or no GUI. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me. What's the difference between Exchange Server and Hosted Exchange ? Both are different software piece? Is Hosted Exchange not available in MSDN?NixGurus

The features are similar but they have different licenses. Also, Exchange server is installed on local server but Exchange online is hosted. To use the trial version, please refer to the following article. http://www.microsoft.com/en-us/office365/online-software.aspx#fbid=at_qgMeVxkQ Thanks. Novak

My current exchange server have Enterprise License. And it is hosted on hyper-v vm on my dedicated server with public IPv4 IPs.NixGurus

My current exchange server have Enterprise License. And it is hosted on hyper-v vm on my dedicated server with public IPv4 IPs. NixGurus To Host Exchange for customers you will need to be on an SPLA. You should contact an SPLA specialist to sign that agreement, which requires monthly payments. You should consider that most third party software also requires different licence agreements for use in a hosted environment. Self Hosted Exchange rarely makes sense because of the econmies of scale to do things correctly and the price you can charge. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

My current exchange server have Enterprise License. And it is hosted on hyper-v vm on my dedicated server with public IPv4 IPs. NixGurus To Host Exchange for customers you will need to be on an SPLA. You should contact an SPLA specialist to sign that agreement, which requires monthly payments. You should consider that most third party software also requires different licence agreements for use in a hosted environment. Self Hosted Exchange rarely makes sense because of the econmies of scale to do things correctly and the price you can charge. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me. Thanks for detailing the things. Can you please tell me about which 3rd party application I'll need to use to attain such features? NixGurus