?
Solved

Exchange 2010 install in exising exchange environment

Posted on 2011-02-18
6
Medium Priority
?
339 Views
Last Modified: 2012-05-11
ok, just a quick question hopefully..lol,  Installing a 2010 exchange server into a domain that already has a 2007 exchange server that has nothing to do with the users that will be using the 2010.  They have 2 of their own accepted domains.  The new server will have its own.  After installing 2010 i noticed that it went out and linked itself to the 2007 exchange server and pulled in all the mailboxes from that other server.  I haven't added any mailboxes for the new users yet.  Should i just leave those there or remove them.  Is there a way i could filter them from the address policy so they won't get the 2010 policies?
0
Comment
Question by:jasonmichel
  • 3
  • 3
6 Comments
 
LVL 58

Expert Comment

by:tigermatt
ID: 34930640

When you install an Exchange Server into a forest which has Exchange Servers already, the new boxes will share configuration data and share control over the existing Exchange deployment. That's a matter of design -- the product is designed to co-operate with other Exchange Servers on the network for companies with large environments, split role servers, many servers for high availability etc.

For you, that means that your new Exchange 2010 server also thinks it is responsible for the two accepted domains. It will also read all the existing Exchange configuration in Active Directory, and as a result, it can see which users have mailboxes. The mailboxes you see in the 2010 Management Console are not located on the 2010 server. The data is still on the 2007 box, so do not remove them, because it will fully remove those users' mailboxes (and potentially their Active Directory logon accounts, depending on how you delete them).

There are also issues with Transport and Client Access in the set-up you are looking to achieve. The primary problems here are how you set each box to send to the Internet -- and, more importantly, ensuring emails from users on 2010 Exchange can still get to 2007 Exchange internally. This shouldn't be a major issue, but it's one which could be overlooked.

If you want a totally isolated environment for the two Exchange Servers, you need to build a new forest for the 2010 server to run in. It then has its own configuration and no bearing over the existing 2007 system.

-Matt
0
 
LVL 1

Author Comment

by:jasonmichel
ID: 34930689
could i still create the send connector to go to internet, and then just create a entry in the 2010 server hosts file for the mail.accepteddomain.com?
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 34930873

That really depends on what you're trying to do.

What is accepteddomain.com? If that is one of your internal accepted domains, then no, that won't work. Exchange won't even look at DNS or MX records if it's sending to a domain which it is authoritative for. An authoritative domain is one which that particular Exchange organization controls, so Exchange tries to route email internally to the correct mailbox on whatever server it resides on.

That means you need to make sure your interconnects - the receive connectors - between the 2010 and 2007 box are sound. That essentially means using the default configuration - as long as you haven't modified it, that will work in 99% of cases for email delivery between the two environments.

-Matt
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
LVL 1

Author Comment

by:jasonmichel
ID: 34930894
yeah i haven't modified the default setup at all..i basically just added all the new users for the 2010 domain.  so i just want them to still be able to email everyone in the 2007 domains and vice versa
0
 
LVL 58

Accepted Solution

by:
tigermatt earned 2000 total points
ID: 34930906
>> so i just want them to still be able to email everyone in the 2007 domains and vice versa

If that's the case, that should work right out of the box. The two servers will deliver email internally, and only talk to the Internet when it's email for a mailbox outside the Exchange environment (i.e. on the Internet).

-Matt
0
 
LVL 1

Author Comment

by:jasonmichel
ID: 34930915
good deal, just wanted to be safe..thanks!
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

You can use the network upload option and the Office 365 Import service to bulk-import PST files to user mailboxes. Network upload means that you upload the PST files a temporary storage area in the Microsoft cloud.
Fix RPC Server is unavailable Error in Exchange 2013, 2010, 2007, and 2003 Server. Different reason can such as network connectivity issue, name resolution issue, firewall, registry corruption that lead to RPC Server Unavailable error.
how to add IIS SMTP to handle application/Scanner relays into office 365.
To export Lotus Notes to Outlook PST or Exchange and Domino Server files to Exchange Server or PST files with ease, go for Kernel for Lotus Notes to Outlook conversion tool. Through the video, you can watch the conversion process. A common user with…

589 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question