Re: Exchange Migration Part II

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: Dave Goldman help: rename AD user creates prob w autocomplete Outl
    ... To rename the account I followed the following steps: ... Then I went to the account properties and made sure that the new Display ... her mailbox name in the Mailbox store in Exchange had not ... I rebuilt the Offline Address Book on the Exchange server and redownloaded ...
    (microsoft.public.exchange.admin)
  • Re: ActiveSync warning
    ... in short the binding is wrong on the exchange server. ... I have run it with my local account and with my domain administrator account ... up-to-date notifications on their device until the correct SMTP address is ...
    (microsoft.public.exchange.clients)
  • Re: Exchange Migration Part II
    ... 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. ... the account on the Exchange Server in Domain A that coinsides to the account ... > resides in Domain A on Domain A's Exchange server. ...
    (microsoft.public.exchange.setup)
  • [NT] Vulnerability in Exchange Server Allows Remote Code Execution (MS05-021)
    ... A remote code execution vulnerability exists in Microsoft Exchange Server ... their choice in the security context of the SMTP service. ...
    (Securiteam)
  • Re: smarthost authentication
    ... We have a small group of users on an Exchange 2003 server. ... clients to directly handle internet stuff. ... The second account is the Exchange Server account. ...
    (microsoft.public.exchange.setup)