Quantcast
Viewing all articles
Browse latest Browse all 8820

An old mailbox server switches over to a new CAS/HT server even though an old CAS/HT server was still available

Hi guys,

I have 2 Exchange 2010 SP server in an organisation. I was asked to migrate these to 2 new Windows servers, so I built 2 new Exchange servers (mailbox + CAS/HT). Once the new HT was up and running, the old and mailbox (the one with all the DBs) started using the new HT which cased issue as there were no connectors configured for the new HT. This then caused all outgoing email to queue up indefinitely. Then I configured a send connector and manually initialised the processing (right clicked the queue and clicked Retry), but nothing happened. Then I restarted the Exchange Trasport service on the new HT (the one where the messages were queued) and it finally started procesisng the queued messages on its own. All clients (Outlook 2010) ahve been connecting to the old CAS/HT server all the time. So I have 2 questions.

Why would an existing mailbox server stop using an HT server to which it was already connected and start using a new HT server?

Why the new HT server refused to process the queued messages both on its own and when I initialised it, even though it was procesisng all newly created messages (once I created a connector), until I restarted its Exchange Transport service?

Thanks a lot for any input.

Zoran


Viewing all articles
Browse latest Browse all 8820

Trending Articles