Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 252
  • Last Modified:

Migrating from 2007 to 2010 with DAG

Our environment has 5 exchange servers. 1 is a mailbox. Two serve as CAS and one is strictly a HUB transport server.

As soon as the new CAS servers (2 of them) were built with 2010 and patched the log files shows the transport sever (2007) trying to send mail to them. The only thing I can see in the old config that I think would cause this is an internal SMTP interogranization send connector.

I need to make sure I can have these boxes online so I can build the environment without messages being stopped or failing because they are trying to access boxes not in production yet. Please assist.

The new environment is 2008 R2 fully patched with all new servers (2 CAS and 3 MBX) all running 2010 exchange sp2 rollup 6. Clients are 2007 and 2010 office.

Thank you
0
MXadmin
Asked:
MXadmin
  • 7
  • 5
1 Solution
 
MXadminAuthor Commented:
That does not address anything in the question I have asked.

The CAS server for 2010 cant be powered on, when they are the old trasnport/hub server tries to direct mail towards them. I need to be able to have the machines powered on in order to configure them and test the new builds.
0
 
AmitIT ArchitectCommented:
CAS role doesn't play any role in mail routing...It seems you have install Hub role also. If so, you can remove Hub role for the time being.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
MXadminAuthor Commented:
The two new server are doing both CAS and HUB/Transport services. But if not receive or send connectors are configured why is this happening? I also had not at that time installed the exchange software yet on the mailbox servers. I need to be able to have the CAS/HUB boxes for 2010 online while I configure them. Whats the easiest way to do this? I also now have a hot head client becuase they are claiming for the 20 minutes the servers were online the mail was sent, verified through message tracking, but never delivered and they want to know where the mail would have went to as it was not delivered. Exchange wouldnt just discard this would it?
0
 
AmitIT ArchitectCommented:
check tracking logs and queue viewer.
0
 
MXadminAuthor Commented:
The only thing I see in the tracking logs is showing the message being sent to the new CAS/HUB server but nothing afterwards. The message id abc123 abc456 neither of those appear again after it shows it was sent to the new boxes
0
 
AmitIT ArchitectCommented:
Is this a External message? or Internal?
0
 
MXadminAuthor Commented:
These are internal messages for the most part around 200 messages.
0
 
AmitIT ArchitectCommented:
okay open EMS and run

Test-servicehealth
Get-queue

both from Exchange 2007 and 2010 and post it
0
 
MXadminAuthor Commented:
Well the 2010 stuff I have powered off since mail stops flowing when I turn them on. Howerer the 2007 shows client access and hub tranport both true for serices running and 7 messages under messagecount for in the que.
0
 
Simon Butler (Sembee)ConsultantCommented:
As soon as you introduce an hub transport server to the domain, Exchange will use it. Nothing you can do to stop it other than stopping the transport service. It may even prefer it, because it is a higher version.

As long as you have Send Connectors in place correctly, then Exchange should route the email back to those servers for sending to the internet. You need to ensure that any restrictions on the Receive Connectors on the existing servers allow the Exchange 2010 servers to connect.

Any reason for deploying Exchange 2010 SP2 rather than straight to SP3 for new builds?

Simon.
0
 
MXadminAuthor Commented:
Simon,

On the new server there are no receive, no send and no transport rules installed, configured or enabled. Nothing at all. That's why this makes no sense.

SP3 does a schema change and the client is not looking to have that done otherwise sp3 with the newest rollup would be the choice I would have made.
0
 
MXadminAuthor Commented:
Issue was with rogue receive connector limiting ip range of exchange server with wrong authentication method
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now