two exchange servers 1 external domain, two different local domains.
We are in the process of setting up a "new" domain...new DC, Exchange, the entire deal. The "old" stuff will stay up till the switch over.
So I am clear we are talking all new hardware/software....our old stuff was pretty darn old. The domain-name.local will be different between the two, user names are going to change email address are going to change, however the domain for email will be the same. So where the old email and user id's went like this:
123@mycompany.com
and your domain login was
123
or
domain-name\123
The new "domain" will go something like this
Email
first.lastname@mycompany.c
and the new domain login will be
first.lastname
or
local\first.lastname
The "email" domain is mycompany.com, the email servers MX record is mail.mycompany.com, and the "internal" domain name is domain-name.local.
The "new" stuff is going to be the same email domain, but users are going to be different...first.lastname
Now that I hope I got the idea across....here is the question.
I would like to setup on a new public routable IP with a new MX record for the new exchange server, but have the old production server still going....is this possible, if so how....all this will be running on the same @mycompany.com and that will not change.
I am not sure I am explaining this well.
The end result will be two exchange servers on the same "external" domain, the public routable domain of mycompany.com.....but one server will service the local domain domain-name.local, and one exchange will serve local.local, with different users on each.
is this possible.....
So I am clear we are talking all new hardware/software....our old stuff was pretty darn old. The domain-name.local will be different between the two, user names are going to change email address are going to change, however the domain for email will be the same. So where the old email and user id's went like this:
123@mycompany.com
and your domain login was
123
or
domain-name\123
The new "domain" will go something like this
first.lastname@mycompany.c
and the new domain login will be
first.lastname
or
local\first.lastname
The "email" domain is mycompany.com, the email servers MX record is mail.mycompany.com, and the "internal" domain name is domain-name.local.
The "new" stuff is going to be the same email domain, but users are going to be different...first.lastname
Now that I hope I got the idea across....here is the question.
I would like to setup on a new public routable IP with a new MX record for the new exchange server, but have the old production server still going....is this possible, if so how....all this will be running on the same @mycompany.com and that will not change.
I am not sure I am explaining this well.
The end result will be two exchange servers on the same "external" domain, the public routable domain of mycompany.com.....but one server will service the local domain domain-name.local, and one exchange will serve local.local, with different users on each.
is this possible.....
ASKER
I am not really sure I explained this well enough.
The two email servers will not be on the same internal domain, will not have the same users, and will never talk to each other.
Really in a nutshell I guess what I am asking is can I have two exchange servers on the same external domain service two different internal "local" domains.
The two email servers will not be on the same internal domain, will not have the same users, and will never talk to each other.
Really in a nutshell I guess what I am asking is can I have two exchange servers on the same external domain service two different internal "local" domains.
Hi,
it is a bit complicated, but it can be done.
What you need to do is configure old exchange as internal relay, and new exchange as authoritative for @mycompany.com domain.
MX for the @mycompany.com domain would point to old exchange.
Then you would configure connector on old one, to send email for users that don't exist on it, to new server.
That way mail flow would be MX --> old exchange --> new exchange --> drop (if no user is found on both servers)
So mail goes to old exchange, and if user is there, mail goes to mailbox and that is it.
If user does not exist on old exchange, then email is forwarded via connector to new exchange, and delivered to that user.
If there is no user there as well, then sender gets message that user does not exist, just like sent to any server.
As for internal email, it would work with no problem, since exchange automatically see what users are on it, and deliveres.
One problem is that if you want someone from new server to send email to user on old server, it would not be delivered, since new server is authoritative for domain and will not try to deliver it to some other server.
PS> These rules can be modified, to switch old/new server.
Regards,
Ivan.
it is a bit complicated, but it can be done.
What you need to do is configure old exchange as internal relay, and new exchange as authoritative for @mycompany.com domain.
MX for the @mycompany.com domain would point to old exchange.
Then you would configure connector on old one, to send email for users that don't exist on it, to new server.
That way mail flow would be MX --> old exchange --> new exchange --> drop (if no user is found on both servers)
So mail goes to old exchange, and if user is there, mail goes to mailbox and that is it.
If user does not exist on old exchange, then email is forwarded via connector to new exchange, and delivered to that user.
If there is no user there as well, then sender gets message that user does not exist, just like sent to any server.
As for internal email, it would work with no problem, since exchange automatically see what users are on it, and deliveres.
One problem is that if you want someone from new server to send email to user on old server, it would not be delivered, since new server is authoritative for domain and will not try to deliver it to some other server.
PS> These rules can be modified, to switch old/new server.
Regards,
Ivan.
The two email servers will not be on the same internal domain, will not have the same users, and will never talk to each other
Without talking your mail flow coexistence will not work
this is typical shared name space scenario
This is surely possible !
What about user old profile?
do you want old email data for migrated users ?
you need to clearly differentiate business requirements and technical requirements and then can identify exact solution
ASKER
Ivan,
No one on the old server would need to send mail to anyone on the new...or the other way around, so that part is not really a worry for me.
Mahesh,
The old user profile will not go over....we do not want it to go over.....the old domain is a real mess.
Really what we want is to leave the old up and going, then one morning flick the switch and everything is new....everything.
What would would like is to leave the old exchange up and going but not taking care of any new emails, just have it sit there so people can OWA into it or something to that effect, and reference stuff.
Really we want to divorce ourselves from the old domain and bring as little as possible to the new....this includes your contacts, saved mail, all the way down to the 74 copies of the same 500mb file you have saved in 74 different places (you think I am kidding...nope)
we want a clean sheet.
No one on the old server would need to send mail to anyone on the new...or the other way around, so that part is not really a worry for me.
Mahesh,
The old user profile will not go over....we do not want it to go over.....the old domain is a real mess.
Really what we want is to leave the old up and going, then one morning flick the switch and everything is new....everything.
What would would like is to leave the old exchange up and going but not taking care of any new emails, just have it sit there so people can OWA into it or something to that effect, and reference stuff.
Really we want to divorce ourselves from the old domain and bring as little as possible to the new....this includes your contacts, saved mail, all the way down to the 74 copies of the same 500mb file you have saved in 74 different places (you think I am kidding...nope)
we want a clean sheet.
If its really that's simple, then actually no question at all
setup new AD domain
setup new exchange
set your primary smtp name space on exchange (same as older one)
Create users with new AD, grant them mailboxes with above SMTP name space
point your MX to new domain and that's all
new users will start receiving mails..
disjoin there old workstations (may be you have new workstations) from old domain and join them to target domain, configure outlook and end
Now:
you said that old exchange need working...here you need to setup co-existence mail flow to just old exchange keep receiving emails
further in order to transact emails between old and new because your business will require all communication to be delivered on new email ID, you need to setup mail flow co-existence, this would require one more SMTP domain to simply work with co-existence
For ease of user, don't you think that they need GAL of old and new users - some kind of GAL synchronization would require here
One last thing, you still would require old emails copied to new email account ?, again here mailbox migration will come in picture...
if you don't want mail flow co-existence , then you need to change target SMTP name space, this will avoid all configurations and possible issues
From my experience, no migration projects are easy, they always have environmental challenges, technology challenges and hence need careful planning, design and execution with proper roll back plans
Hence I suggested earlier...
setup new AD domain
setup new exchange
set your primary smtp name space on exchange (same as older one)
Create users with new AD, grant them mailboxes with above SMTP name space
point your MX to new domain and that's all
new users will start receiving mails..
disjoin there old workstations (may be you have new workstations) from old domain and join them to target domain, configure outlook and end
Now:
you said that old exchange need working...here you need to setup co-existence mail flow to just old exchange keep receiving emails
further in order to transact emails between old and new because your business will require all communication to be delivered on new email ID, you need to setup mail flow co-existence, this would require one more SMTP domain to simply work with co-existence
For ease of user, don't you think that they need GAL of old and new users - some kind of GAL synchronization would require here
One last thing, you still would require old emails copied to new email account ?, again here mailbox migration will come in picture...
if you don't want mail flow co-existence , then you need to change target SMTP name space, this will avoid all configurations and possible issues
From my experience, no migration projects are easy, they always have environmental challenges, technology challenges and hence need careful planning, design and execution with proper roll back plans
Hence I suggested earlier...
ASKER
We are in the process of setting up the new domain.....I am really happy we finally have the time to set it up correctly, and not a rush....this is down get it up and going as soon as possible kind of deal.
Hopefully we will have exchange up and going this week.....it has been a bit nutty lately....will update on progress.....
Thanks.
Hopefully we will have exchange up and going this week.....it has been a bit nutty lately....will update on progress.....
Thanks.
ASKER
We have changed things a little bit in the time I have checked in last.
I think I said all of our existing stuff is pretty old, and finally we are getting all new hardware...all the way around.
We just ordered a new Sonicwall ES5000....so this thing is going to sit in front of the new email server.
I would still like to keep the old "stuff" up and going and have both working side by side.
I am wondering if this has drifted out of the scope of this thread....if so let me know and I will start a new topic.
I am thinking I am going to have to make a new MX record on godaddy, pointing to the new IP of the new appliance.....the routable IP's are not an issue for me.
Everything is still the same as the start....we are just sticking this sonicwall thing in front.
I think I said all of our existing stuff is pretty old, and finally we are getting all new hardware...all the way around.
We just ordered a new Sonicwall ES5000....so this thing is going to sit in front of the new email server.
I would still like to keep the old "stuff" up and going and have both working side by side.
I am wondering if this has drifted out of the scope of this thread....if so let me know and I will start a new topic.
I am thinking I am going to have to make a new MX record on godaddy, pointing to the new IP of the new appliance.....the routable IP's are not an issue for me.
Everything is still the same as the start....we are just sticking this sonicwall thing in front.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
this is possible
but answer is too big as there is migration and co-existence involved which is tricky part
I suggest you go fo gigs or hier consultant for same
we can help on this blog but that will be limited help