Re: Exchange Migration Part II

I think I understand. Basically I need to add an additional Address to the
users in the source domain and route via a connector using that address and
add a forwarder in the target domain to route back to the sourc. Is that
correct?

"Ed Crowley [MVP]" wrote:

Please disregard my previous post and use this corrected one. Sorry for the
error and any ensuing confusion.

While it's possible to do it the way you want, I think it's a lot easier to
add another domain for intra-forest routing, say a.xxx.com and b.xxx.com,
and use these addresses for contacts to ensure that mail is sent between
them properly. For example, in domain A, you'd have a contact that points
to a mailbox in domain B, with target address joe@xxxxxxxxx and under E-Mail
Addresses he'd have addresses joe@xxxxxxx and joe@xxxxxxxxxx His
mailbox-enabled user account in domain B would have a reply addres of
joe@xxxxxxx and proxy address joe@xxxxxxxxxx You could then create SMTP
Connectors that route these subdomains to servers in other forests through
smart hosts, or you could add internal DNS MX records if you preferred.
You'd also need to add recipient policies to make the addresses legal. This
method makes sharing a e-mail domain a lot more transparent.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"NEWTECH" <NEWTECH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D16573BC-64D5-4AD9-89FA-E827107EEEAA@xxxxxxxxxxxxxxxx
The mail domain is as follows: xxx.com which is used by the current email
server. I created in the new domain, domain B and added an additional
address of xxx1.com to distingush between the two sides. In the SMTP
properties of the migrated user in exchange on the B domain I have both
name@xxxxxxx and name@xxxxxxx for the email addresses, with xxx1.com as
the
primary address for now until I finish the migration. I want to be able
to
email xxx.com but I can not. I did set up a SMTP connector from Domain B
using xxx.com in the Address name space and the IP address of the server
in
Domain A for "Forwarding all mail to the following smart host".

One the other side Domain A i have the SMTP connector to xxx1.com in the
name space with the IP address of the Exchange Server in Domain B. In
addition to that, I 've create a contact in Domain A with the addess of
username@xxxxxxxx and attached it as a forward to the exchange account to
deliver the mail to both xxx.com (the origional exchange A) and forward to
xxx1.com the new exchange B.

If there's a way to
a)sync the mail on both sided, I haven't found it between 2 exchange 2003
servers
b)I don't seem to be able to email any user on the xxx.com domain A side.
It bounces. - This is the issue I'm trying to resolve.

I hope i've explained it enough so you'll understand.
"Ed Crowley [MVP]" wrote:

What do you mean by "secondary address" on the contact? You would make
the
Domain B address the "target address", the one that shows up in the
General
tab, because that's the one that is the one to which mail is routed. Is
that what you did? This is not "forwarding", it is routing because it is
handled by the routing engine. Nobody opens the message and forwards it.

I don't understand the second part of what you posted.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"NEWTECH" <NEWTECH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6EB78933-10AD-4DB8-A449-E2E82C6A64A4@xxxxxxxxxxxxxxxx
In Domain A i created a contact with a secondary address for Domain B.
In
the account on the Exchange Server in Domain A that coinsides to the
account
migrated to Domain B, I added a a forward to the email account in
Domain
A
using that contact to forward the mail Domain B . I then checked the
box
to
deliver to both places.

"Ed Crowley [MVP]" wrote:

Again, what do you mean about "created a forward"? Please use
standard
terms.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral
problems."
..

"NEWTECH" <NEWTECH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:44DA210E-0007-42E3-9398-C118DE3F6D05@xxxxxxxxxxxxxxxx
Once again I'm sorry for giving you incomplete infomation. I have
one
account migrated to the new domain - domain B, In it's own OU. I've
moved
the email for that account via exmerge the new server (Domain B). I
haven't
closed the origional account in the old domain - domain A. So mail
still
resides in Domain A on Domain A's Exchange server. On that account
I've
create a forward to reach Domain B so mail gets delivered to both
places.

I've created an SMTP connector from Domain A in Exchange to Domain B
in
Exchange. In Domain B I've created on Exchange an SMTP connector
and
I've
added the IP to allow it to Relay to Domain A on Domain A's Exchange
server.
In addition I've added a Policy to my Firewall to route out Domain
B's
email.
I have only one mx record xxx.xxx.com which I'm sharing the
namespace
for
both domains. So Domain B has xxx.com which is the same as Domain A
and
in
addition Domain B has @xyz.com for email to I can forward the mail.
(My
firewall's external IP address is the same as my MX record and then
it
NAT's
via a policy to Domain A's exchange server. My plan is later on to
switch
Domain B's exchange server to the IP of the current Domain A's
exchange
server.)

Since I've added the Policy to my firewall, I've been able to email
outside
email address from Domain B without any issue. And it even picks up
the
proper header information. I can't email between domain's. So if i
want
to
send an email to someone inside the company in Domain A it bounces.

That's my issue. I want to move people by groups at a time and in
stages,
but I can't do that if they can not email people in Domain A. So I
need
to
be able to communicate with the people in Domain A from Domain B via
email.
Do you know how I can accomplish being able to email people in my
current
Domain A?

"Ed Crowley [MVP]" wrote:

You keep giving us incomplete information, which makes it difficult
to
help
you. What do you mean by "forward from the old domain to the new"?
And
surely you do more than just create an OU, which wouldn't effect
anything
Exchange-wise.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral
problems."
..

"NEWTECH" <NEWTECH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C33FC310-C378-41A4-8A62-A2EB81AA60B4@xxxxxxxxxxxxxxxx
Not using 2007 still 2003, But I'll try the sync. As for the
mechanism, I
create an OU for those migrated with a forward from the old
domain
to
the
new.

"Ed Crowley [MVP]" wrote:

You can configure the Exchange 2007 to allow SMTP relay by the
Exchange
2003
box.

If you are going to maintain accounts for the same domain
between
the
two
servers you're going to need some sort of mechanism so that each
one
knows
about the recipients on the other. That's usually done by
directory
synchronization, where you create contacts on one for mailboxes
on
the
other
and vice-versa.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral
problems."
..

"NEWTECH" <NEWTECH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F08D97B3-A447-4DBA-ABBA-CA228DBBA0AB@xxxxxxxxxxxxxxxx
I have one last issue to conquer. Perhaps someone can guide me
to
the
proper
information. I have my exchange servers talking. Both in
different
forests.
The Source can send to the Target via a forwarder and an SMTP
connector.
The Target can send mail internally without an issue. Is
there
anyway
to
route the mail from the Target to the Source so it can go
outbound
to
the
world.

I have a firewall and I'm not sure if that is the issue. I
don't
want
to
add
another SMTP connector for this target server unless is
necessary.










.

Relevant Pages

  • RE: Email failed
    ... Run the CEICW and go through the Internet, firewall and Web Server ... Connector for POP3 Mailboxes" option. ... you could just leave the option unchanged, since your Exchange could ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Sending email to mydomain.com
    ... server will appear as undeliverable. ... This happens because you are using the POP3 connector... ... an NDR when an account doesn't exist). ... >different from the user account names for the exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2007 - Sending to External Domains
    ... Exchange Server auth is checked, ... The other Receive connector is the one Created by default fro Client ... Hosted Services or a third-Party SMTP gateway, ...
    (microsoft.public.exchange.connectivity)
  • Re: Entourage account setup applescript not working
    ... I pasted the script at the end just in case. ... When comparing the account settings on 2 computers, ... This script assists a user with the setup of his Exchange account ... Customize the network and server properties below with information ...
    (microsoft.public.mac.office.entourage)
  • Re: Problems sending email in SBS 2008
    ... I had a KM scanner that was upsetting Exchange IMF, IMF properties, ... I work remotely from this client so I can only make changes to the server ... I'm confident the receive connector is ...
    (microsoft.public.windows.server.sbs)
Loading