Hi Can you help please? A) The issue/problem MS-Exchange 2010 standard - We have a problem where by our outgoing mails are leaving from our DR Exchange server at DR site instead of the exchange server at the main site. B) Actions /Steps has been taken but did not resolve the issue The original settings whereby the Exchange and File servers were strictly part of 2 different AD sites i.e. Main site and DR site hence eliminating any possibility of a fail over on DFS. This has created the problem of e-mails are sent to DR exchange and started queuing up at DR Exchange server DR site and did not know how to go out. Changed the setting and joined both sites as ONE AD option – under this options the main exchange servers go through the failure process and send e-mails to DR site and e-mail go out through the DR exchange server at DR site have configured highest priority for the main site and lowest for the DR but this has not helped and emails still prefers to going via DR Site Although current settings offer more resilience at Exchange level i.e. emails can go via DR or Main site but unfavourable for DFS and slow up the network considerably. In any case e-mails should go out via main exchange unless it is out of action. C) Brief description of the environment - The setup at the main site consists of ONE main Exchange server (MBX/HT) and two CAS servers backing up each other. - The setup at the DR site consists of ONE DR Exchange server (MBX/HT/CAS) - Both sites are connected via VPN - Operating system is MS windows 2008 R2 enterprise and exchange is MS exchange - 2010 standard on exchange and CAS servers - Operating system is MS windows 2008 R2 standard on all other servers - DFS running between the Main and DR sites for file servers too. Thanks MA

Sounds like you have now got only 1 AD with all your exch server in them. If this is the case, then Exch will use either HUB server in the AD site, it will load balance, unless you have DAG on your mailboxe servers with an active db then it will use the other hub as preference. However, you're saying emails go out to via the DR site. How many send connectors have you got and what is the cost/address space of each. See if you have set SubmissionServerOverrideList on your mailbox servers by using the get-mailboxserver -identity "yourservername" |fl >c:\mbx.txt You can use the SubmissionServerOverrideList to force maibox servers to use your HUB servers in the main site. Sukh

On Mon, 16 May 2011 11:38:01 +0000, MA-1 wrote: >Hi Can you help please? > >A) The issue/problem MS-Exchange 2010 standard - We have a problem where by our outgoing mails are leaving from our DR Exchange server at DR site instead of the exchange server at the main site. > >B) Actions /Steps has been taken but did not resolve the issue > >The original settings whereby the Exchange and File servers were strictly part of 2 different AD sites i.e. Main site and DR site hence eliminating any possibility of a fail over on DFS. This has created the problem of e-mails are sent to DR exchange and started queuing up at DR Exchange server DR site and did not know how to go out. > >Changed the setting and joined both sites as ONE AD option ? under this options the main exchange servers go through the failure process and send e-mails to DR site and e-mail go out through the DR exchange server at DR site You're using a DAG? And you have copies of the databases in both locations? And both machines have the HT role installed on them? If that's true, then the mailbox server is going to use a HT role on another server (provided there's one available). So, if the active mailbox is in the "main" location it will use the HT role in the "dr" location. >have configured highest priority for the main site and lowest for the DR but this has not helped and emails still prefers to going via DR Site That's correct. >Although current settings offer more resilience at Exchange level i.e. emails can go via DR or Main site but unfavourable for DFS and slow up the network considerably. In any case e-mails should go out via main exchange unless it is out of action. C) Brief description of the environment > >- The setup at the main site consists of ONE main Exchange server (MBX/HT) and two CAS servers backing up each other. - The setup at the DR site consists of ONE DR Exchange server (MBX/HT/CAS) - Both sites are connected via VPN - Operating system is MS windows 2008 R2 enterprise and exchange is MS exchange - 2010 standard on exchange and CAS servers - Operating system is MS windows 2008 R2 standard on all other servers - DFS running between the Main and DR sites for file servers too. You could move the HT role in the "main" location to each of the CAS servers (making them HT/CAS servers) -- provided the machines are sturdy enough to deal with both roles. But as long as all the HT roles are in the same site you'll continue to use all of them. If your goal is DR, then go back to the two-site set-up and use separate HT servers. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, More information about exchange 2007 Active Directory Site-Based Routing: http://technet.microsoft.com/en-us/library/aa998825(EXCHG.80).aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Hi Sukh Thank you for your e-mail and comments. I have executed the command you suggested however override value is not found. Command results as follows: [PS] C:\Windows\system32>get-mailboxserver -identity ebexh01 Name Database Availability Group MAPI Encryption Required Auto Database Mount Dial Database Copy Auto Activation Policy EBEXH01 EBDAG01 False Good Availability Unrestricted [PS] C:\Windows\system32> As you can see from the above the command has been successfully executed although output is not in a text file but it doesn’t say any thing about override value Regards MAMA-1

Hi Rich Thank you for your e-mail and comments You're using a DAG? And you have copies of the databases in both locations? And both machines have the HT role installed on them? YES If your goal is DR, then go back to the two-site set-up and use separate HT servers. That is what we have originally planned / installed but for some reason this setup have the mail queuing in the main sit and does not go out! Regards, MA MA-1

Hi Gen Lin Thank you for your reply and the link - it is very useful, thank you, but it does not have an anser per say, it is 2007 rather than 2010 although they are very similar. again thanks MAMA-1

see the command I posted again.Sukh

On Wed, 18 May 2011 17:41:30 +0000, MA-1 wrote: >Thank you for your e-mail and comments >>You're using a DAG? And you have copies of the databases in both locations? And both machines have the HT role installed on them? >YES >If your goal is DR, then go back to the two-site set-up and use separate HT servers. > >That is what we have originally planned / installed but for some reason this setup have the mail queuing in the main sit and does not go out! For what reason is the e-mail remaining in the delivery queues? What servers are named in the "Source Servers" tab of your Send Connector? Do all of the servers mentioned in that list have the ability to send e-mail to the Internet (or to a smart host, if that's what you're doing)? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Sukh Please find attached 2 output files of get-mailboxserver -identity "yourservername" |fl >c:\mbx.txt for the 2 exchange servers, 01 is the main site and 02 is the DR site. In addition to the Auto-routing main first, DR second would it be possible to advice the relevant command to setup HT mail submission preference manually as an alternative option to configure the main exchange server 01 as a priority to submit mails thru A) MAIN EXCHANGE 01 RunspaceId : ae3b5784-9b87-4cbe-926e-e51a7442d987 Name : EBEXH01 CalendarRepairWorkCycle : CalendarRepairWorkCycleCheckpoint : SharingPolicyWorkCycle : 1.00:00:00 SharingPolicyWorkCycleCheckpoint : 1.00:00:00 SharingSyncWorkCycle : 03:00:00 SharingSyncWorkCycleCheckpoint : 03:00:00 ManagedFolderWorkCycle : 1.00:00:00 ManagedFolderWorkCycleCheckpoint : 1.00:00:00 TopNWorkCycle : 7.00:00:00 TopNWorkCycleCheckpoint : 1.00:00:00 UMReportingWorkCycle : 1.00:00:00 UMReportingWorkCycleCheckpoint : 1.00:00:00 CalendarRepairSchedule : {} SharingPolicySchedule : {Sun.03:00-Sun.11:00, Mon.03:00-Mon.11:00, Tue.03:00-Tue.11:00, Wed.03: 00-Wed.11:00, Thu.03:00-Thu.11:00, Fri.03:00-Fri.11:00, Sat.03:00-Sat.1 1:00} CalendarRepairMissingItemFixDisabled : False CalendarRepairLogEnabled : True CalendarRepairLogSubjectLoggingEnabled : True CalendarRepairLogPath : C:\Program Files\Microsoft\Exchange Server\V14\Logging\Calendar Repair Assistant CalendarRepairIntervalEndWindow : 30 CalendarRepairLogFileAgeLimit : 00:00:00 CalendarRepairLogDirectorySizeLimit : unlimited ManagedFolderAssistantSchedule : {Sun.01:00-Sun.09:00, Mon.01:00-Mon.09:00, Tue.01:00-Tue.09:00, Wed.01: 00-Wed.09:00, Thu.01:00-Thu.09:00, Fri.01:00-Fri.09:00, Sat.01:00-Sat.0 9:00} LogPathForManagedFolders : C:\Program Files\Microsoft\Exchange Server\V14\Logging\Managed Folder A ssistant LogFileAgeLimitForManagedFolders : 00:00:00 LogDirectorySizeLimitForManagedFolders : unlimited LogFileSizeLimitForManagedFolders : 10 MB (10,485,760 bytes) MessageTrackingLogEnabled : True MessageTrackingLogMaxAge : 30.00:00:00 MessageTrackingLogMaxDirectorySize : 1000 MB (1,048,576,000 bytes) MessageTrackingLogMaxFileSize : 10 MB (10,485,760 bytes) MessageTrackingLogPath : C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Mess ageTracking MessageTrackingLogSubjectLoggingEnabled : True MigrationLogLoggingLevel : Information MigrationLogFilePath : MigrationLogMaxAge : 180.00:00:00 MigrationLogMaxDirectorySize : 10 GB (10,737,418,240 bytes) MigrationLogMaxFileSize : 100 MB (104,857,600 bytes) IrmLogEnabled : True IrmLogMaxAge : 30.00:00:00 IrmLogMaxDirectorySize : 250 MB (262,144,000 bytes) IrmLogMaxFileSize : 10 MB (10,485,760 bytes) IrmLogPath : C:\Program Files\Microsoft\Exchange Server\V14\Logging\IRMLogs MAPIEncryptionRequired : False RetentionLogForManagedFoldersEnabled : False JournalingLogForManagedFoldersEnabled : False FolderLogForManagedFoldersEnabled : False SubjectLogForManagedFoldersEnabled : False SubmissionServerOverrideList : {} AutoDatabaseMountDial : GoodAvailability ForceGroupMetricsGeneration : False GroupMetricsGenerationTime : IsPhoneticSupportEnabled : False Locale : {} DatabaseAvailabilityGroup : EBDAG01 DatabaseCopyAutoActivationPolicy : Unrestricted TransportSyncDispatchEnabled : False MaxTransportSyncDispatchers : 5 TransportSyncLogEnabled : False TransportSyncLogLoggingLevel : None TransportSyncLogFilePath : TransportSyncLogMaxAge : 7.00:00:00 TransportSyncLogMaxDirectorySize : 10 GB (10,737,418,240 bytes) TransportSyncLogMaxFileSize : 10 MB (10,485,760 bytes) TransportSyncMailboxHealthLogEnabled : False TransportSyncMailboxHealthLogFilePath : TransportSyncMailboxHealthLogMaxAge : 14.00:00:00 TransportSyncMailboxHealthLogMaxDirectorySize : 10 GB (10,737,418,240 bytes) TransportSyncMailboxHealthLogMaxFileSize : 10 MB (10,485,760 bytes) IsExcludedFromProvisioning : False MaximumActiveDatabases : AdminDisplayVersion : Version 14.1 (Build 218.15) ServerRole : Mailbox, HubTransport ExchangeLegacyServerRole : 0 IsValid : True ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=EBEXH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT ),CN=Administrative Groups,CN=mydomain,CN=Microsoft Exchange,CN=Service s,CN=Configuration,DC=mydomain,DC=co,DC=uk Identity : EBEXH01 Guid : 7b6b31b2-7c87-41a2-b653-4d15f4bd7a75 ObjectCategory : mydomain.co.uk/Configuration/Schema/ms-Exch-Exchange-Server ObjectClass : {top, server, msExchExchangeServer} WhenChanged : 09/03/2011 18:46:43 WhenCreated : 15/11/2010 13:25:56 WhenChangedUTC : 09/03/2011 18:46:43 WhenCreatedUTC : 15/11/2010 13:25:56 OrganizationId : OriginatingServer : EBDMC01.mydomain.co.uk B) DR EXCHANGE 02 RunspaceId : ae3b5784-9b87-4cbe-926e-e51a7442d987 Name : EBEXH02 CalendarRepairWorkCycle : CalendarRepairWorkCycleCheckpoint : SharingPolicyWorkCycle : 1.00:00:00 SharingPolicyWorkCycleCheckpoint : 1.00:00:00 SharingSyncWorkCycle : 03:00:00 SharingSyncWorkCycleCheckpoint : 03:00:00 ManagedFolderWorkCycle : 1.00:00:00 ManagedFolderWorkCycleCheckpoint : 1.00:00:00 TopNWorkCycle : 7.00:00:00 TopNWorkCycleCheckpoint : 1.00:00:00 UMReportingWorkCycle : 1.00:00:00 UMReportingWorkCycleCheckpoint : 1.00:00:00 CalendarRepairSchedule : {} SharingPolicySchedule : {Sun.03:00-Sun.11:00, Mon.03:00-Mon.11:00, Tue.03:00-Tue.11:00, Wed.03: 00-Wed.11:00, Thu.03:00-Thu.11:00, Fri.03:00-Fri.11:00, Sat.03:00-Sat.1 1:00} CalendarRepairMissingItemFixDisabled : False CalendarRepairLogEnabled : True CalendarRepairLogSubjectLoggingEnabled : True CalendarRepairLogPath : C:\Program Files\Microsoft\Exchange Server\V14\Logging\Calendar Repair Assistant CalendarRepairIntervalEndWindow : 30 CalendarRepairLogFileAgeLimit : 00:00:00 CalendarRepairLogDirectorySizeLimit : unlimited ManagedFolderAssistantSchedule : {Sun.01:00-Sun.09:00, Mon.01:00-Mon.09:00, Tue.01:00-Tue.09:00, Wed.01: 00-Wed.09:00, Thu.01:00-Thu.09:00, Fri.01:00-Fri.09:00, Sat.01:00-Sat.0 9:00} LogPathForManagedFolders : C:\Program Files\Microsoft\Exchange Server\V14\Logging\Managed Folder A ssistant LogFileAgeLimitForManagedFolders : 00:00:00 LogDirectorySizeLimitForManagedFolders : unlimited LogFileSizeLimitForManagedFolders : 10 MB (10,485,760 bytes) MessageTrackingLogEnabled : True MessageTrackingLogMaxAge : 30.00:00:00 MessageTrackingLogMaxDirectorySize : 1000 MB (1,048,576,000 bytes) MessageTrackingLogMaxFileSize : 10 MB (10,485,760 bytes) MessageTrackingLogPath : C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Mess ageTracking MessageTrackingLogSubjectLoggingEnabled : True MigrationLogLoggingLevel : Information MigrationLogFilePath : MigrationLogMaxAge : 180.00:00:00 MigrationLogMaxDirectorySize : 10 GB (10,737,418,240 bytes) MigrationLogMaxFileSize : 100 MB (104,857,600 bytes) IrmLogEnabled : True IrmLogMaxAge : 30.00:00:00 IrmLogMaxDirectorySize : 250 MB (262,144,000 bytes) IrmLogMaxFileSize : 10 MB (10,485,760 bytes) IrmLogPath : C:\Program Files\Microsoft\Exchange Server\V14\Logging\IRMLogs MAPIEncryptionRequired : False RetentionLogForManagedFoldersEnabled : False JournalingLogForManagedFoldersEnabled : False FolderLogForManagedFoldersEnabled : False SubjectLogForManagedFoldersEnabled : False SubmissionServerOverrideList : {} AutoDatabaseMountDial : GoodAvailability ForceGroupMetricsGeneration : False GroupMetricsGenerationTime : IsPhoneticSupportEnabled : False Locale : {} DatabaseAvailabilityGroup : EBDAG01 DatabaseCopyAutoActivationPolicy : Unrestricted TransportSyncDispatchEnabled : False MaxTransportSyncDispatchers : 5 TransportSyncLogEnabled : False TransportSyncLogLoggingLevel : None TransportSyncLogFilePath : TransportSyncLogMaxAge : 7.00:00:00 TransportSyncLogMaxDirectorySize : 10 GB (10,737,418,240 bytes) TransportSyncLogMaxFileSize : 10 MB (10,485,760 bytes) TransportSyncMailboxHealthLogEnabled : False TransportSyncMailboxHealthLogFilePath : TransportSyncMailboxHealthLogMaxAge : 14.00:00:00 TransportSyncMailboxHealthLogMaxDirectorySize : 10 GB (10,737,418,240 bytes) TransportSyncMailboxHealthLogMaxFileSize : 10 MB (10,485,760 bytes) IsExcludedFromProvisioning : False MaximumActiveDatabases : AdminDisplayVersion : Version 14.1 (Build 218.15) ServerRole : Mailbox, HubTransport ExchangeLegacyServerRole : 0 IsValid : True ExchangeVersion : 0.1 (8.0.535.0) DistinguishedName : CN=EBEXH02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT ),CN=Administrative Groups,CN=mydomain,CN=Microsoft Exchange,CN=Service s,CN=Configuration,DC=mydomain,DC=co,DC=uk Identity : EBEXH02 Guid : f70f9883-e836-4146-b2e1-927b43c55c74 ObjectCategory : mydomain.co.uk/Configuration/Schema/ms-Exch-Exchange-Server ObjectClass : {top, server, msExchExchangeServer} WhenChanged : 26/04/2011 11:52:39 WhenCreated : 16/11/2010 13:26:23 WhenChangedUTC : 26/04/2011 10:52:39 WhenCreatedUTC : 16/11/2010 13:26:23 OrganizationId : OriginatingServer : EBDMC01.mydomain.co.uk Thank you. MAMA-1

1. If you have one AD site then this you can try the submissionserveroverridelist. Set-MailboxServer -Identity Server1 -SubmissionServerOverrideList HubServer01,HubServer02,HubServer03 2. Then ensure that you create your 2 send connectors and configure each source server as appropiate with address space and cost. Sukh

Hi Sukh Thank you for the information provided. Our original configuration is for 2 separate AD’s one AD for the Main site and one AD for the DR site. In this case e-mail queues at main site that is why we have converted to ONE AD as A TEMPORARY ARRANGEMENT in order to process the emails. Under the one AD condition the emails are sent via DR and equally the DFS is also keeps falling over to DR results in the network slowing considerably, hence the post for assistance. We need both the Main AD and the DR AD sites to avoid the DFS failing over to DR issue however in this case we need to have a resolution to for e-mail queues at main site under 2 AD’s. As your reply refers to ONE AD only, therefore will not be able to use this override command as a resolution. We are looking for a solution so that the emails are to be processed and sent from the main site under the normal conditions. And only under DR condition the e-mail is routed and sent via the DR. What do you think the options are? One of our guys thought that perhaps move our HT role away from MBX servers e.g. A) One approach is to Install HT role on 1 member of CAS array that exists on main site and to install secondary HT on a DR MBX/CAS server, in this case the total HT will be 2. B) The other approach is install HT role on both members of CAS array that exists on main site and also install HT role on MBX/CAS Server in DR. in this case the total HT will be 3. In summary we looking for 2 separate AD’s with the best option to ensure e-mail delivery from the main site under normal condition and only failover to DR site if there is a problem with the main site servers. Regards, MAMA-1

Hi Rich Thank you for your rply and comments. please have a look at the latest information I have provided to Sukh, published on this thread. Does this answer your questions and give you a better idea on the issues in hand? Regards MAMA-1

my thoughts. 1. Create 2 AD sites. Each site has Hub/Cas/DAG member. 2. Main has active DAG copies. 3. Create two send connecotors, specify one with MAIN site HUB (source) and the 2nd with HUB at second site (source). Assign different costs with same address space. 4. If MAIN sites goes down, everything runs out of DR. SukhSukh

On Thu, 19 May 2011 16:37:31 +0000, MA-1 wrote: >Thank you for your rply and comments. > >please have a look at the latest information I have provided to Sukh, published on this thread. > >Does this answer your questions and give you a better idea on the issues in hand? Not really. Your last problem was that e-mail would not leave your organization. I asked why the messages remained on the HT server. I don't see any mention of the reason in your answers. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich Thank you for your reply. Under 2 separate AD’s environment e-mails processing at main site for some reason selects DR HT for outgoing and does not use main site’s HT or connector. Therefore when HT in DR is selected then send connector in DR can’t talk back for being in different AD site and mails start queuing up at the main site. We have joined both AD’s into one as A TEMPORARY ARRANGEMENT in order to process the emails. Under this temporarily arrangement of one AD the emails are sent via DR however consequence of this is that the DFS keeps falling over to DR and causing the network to slow-down quite considerably, hence the post for assistance Regards MA MA-1

Hi Sukh Thank you for your thoughts. I have two questions for you, if I may 1) The original issue of e-mail queuing at the main site and only goes via the DR site – you kindly provided a work around for a single AD. What I would like, if possible the answer to the problem under the normal 2 AD’s scenario. Please see my first post “Description of the environment” and my reply to Rich above. 2) With regard to your thoughts: A) This is how we have setup but problem is that database being active on main site causes HT in DR to send emails B) Would like to know implications of moving the HT role to CAS array on main site and MBX/CAS server in DR site C) Do we need to install HT on both members of CAS array on main site? or 1 member of CAS array on main site and on MBX/CAS server in DR site D) At Main site : we have 3 Exchange 2010 Standard servers i.e. a CAS array with only CAS role installed and MBX/HT servers, E) At DR site DR we have 1 Exchange 2010 Standard Server with MBX/HT/CAS role (all 3) installed on one server Regards, MAMA-1

Hi Rich Re-my earlier reply, what we are looking for is a resolution to the original issue and be be able to have 2 ADs one for each site and able to send e-mails without being queuing in the main site. Regards MAMA-1

1. If you have 2 AD sites with HUB in each, I can't see why it's trying to use your DR server. As mentioned above, how are your send connector(s) setup? Post your results of describe them in details. Use Get-sendconnector 2. not sure why you want to do 2. B) 3.You need a HUB in EACH AD site, if you've got it on the MBX on both sites it will still work. If you move the HUB to the CAS array then that would work too (not sure what HLB/WNLB you using). 4. So as I understand now, you now have two AD sites, each with a HUB and MBX server combined as DR server has CAS too. 5. What emails are getting routed via DR, internal or external?Sukh

On Fri, 20 May 2011 15:13:46 +0000, MA-1 wrote: >Under 2 separate AD?s environment e-mails processing at main site for some reason selects DR HT for outgoing and does not use main site?s HT or connector. Therefore when HT in DR is selected then send connector in DR can?t talk back for being in different AD site and mails start queuing up at the main site. Why can't the HT servers in the sites send messages between them? That's what they're designed to do! If the HT servers in the two AD sites cannot talk to one another then you need to discover why. When you look at the SMTP Send protocol log on one HT server, do you see the conversation in the SMTP Receive protocol log on the other HT server? If you don't, then you probably have some sort of DNS or network problem. How are you joining, or separating, the two AD Sites? Are you changing the IP addresses assigned to the servers? >We have joined both AD?s into one as A TEMPORARY ARRANGEMENT in order to process the emails. I hope you meant "AD Sites" and not two AD forests. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 20 May 2011 15:37:32 +0000, MA-1 wrote: >Re-my earlier reply, what we are looking for is a resolution to the original issue and be be able to have 2 ADs one for each site and able to send e-mails without being queuing in the main site. I understand that. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 20 May 2011 15:13:46 +0000, MA-1 wrote: >Under 2 separate AD?s environment e-mails processing at main site for some reason selects DR HT for outgoing and does not use main site?s HT or connector. Therefore when HT in DR is selected then send connector in DR can?t talk back for being in different AD site and mails start queuing up at the main site. I fogot to add this to my previous e-mail: If you don't see the SMTP conversation between the HT server, use this on each HT server: Set-TransportServer <name> -IntraOrgConnectorProtocolLoggingLevel Verbose The conversation between two HT servers isn't logged by default. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 20 May 2011 16:25:44 +0000, Sukh828 wrote: > > >1. If you have 2 AD sites with HUB in each, I can't see why it's trying to use your DR server. As mentioned above, how are your send connector(s) setup? > >Post your results of describe them in details. > >Use Get-sendconnector HT servers don't use static Send or Rceive Connectors. Looking at the configuration of a Send Connector is useful when the e-mail is sent through that connector, but in the case of HT-to-HT exchanges it isn't used. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Rich, I was thinking along the line that there might be one send connector which has both the main and dr site as source servers, which may be why email is trying to go via dr and mainSukh

Hi Rich Thank you for your reply and comments. Currently we have 1 Internetmail connector that has both main and DR HT as source servers. Get-Connector Output is as follows: [PS] C:\Windows\system32>Get-SendConnector Identity AddressSpaces Enabled EBInternetConnector {SMTP:*;1} True With regard to joining domains, we are use AD and not IP change. The following drawing is an overview of the environment (tried to past but it does not allow drwaings, sorry!) Please let me know if you want me to run other commands Regards, MA MA-1

Hi Sukh Thank you for your reply and comments Currently we have 1 Internetmail connector that has both main and DR HT as source servers. Get-Connector Output is as follows: [PS] C:\Windows\system32>Get-SendConnector Identity AddressSpaces Enabled EBInternetConnector {SMTP:*;1} True Please let me know if you want me to run other commands Regards, MAMA-1

1. so the emails that you see queuing up are for external. 2. I assume you can reproduce this problem. I would remove the DR server from the source servers, then test your mailflow. Sukh

Hi Sukh Thank you for your reply and comments. Re your questions 1. Yes - The email queuing up are for external 2. With regard to “I would remove the DR server from the source servers, then test your mailflow” We did this previously – when only main HT server is running emails are sent and no problem. The main problem we are having is this: When we have the main exchange on one AD (e.g. Main-AD) and DR exchange on another AD (e.g. DR-AD) the emails start queuing up and not sent out. Temporary work around If Main-AD and DR-AD are joined to be under one AD e.g. main-AD then mails go via DR mail server, this provides a temporary solution to the queuing issue. However this temporary solution has a knock-on effect for DFS hence we need to retain 2 separate AD’s environment. The 10 million dollar question is, under 2 AD’s environment Main-Ad & DR-AD, how can we get the e-mail sent out with being held queuing on the main HT server? Regards, MAMA-1

On Mon, 23 May 2011 18:30:30 +0000, MA-1 wrote: >1. Yes - The email queuing up are for external On which server are the messages delayed? And for what reason are they delayed? In a one-site configuration, all three of the HT servers should be used. If messages are delayed only on the HT server in the DR location then the problem is very likely to be connectivity to the Internet. In a two-site configuration the messages have to move from the mailbox server to a HT server in the same AD site. Messages sent from a mailbox on machine #1 would use the HT role on machine #2, and messages from a mailbox on machine #2 would use the HT role on machine #1. From the in-site HT, the messages should leave the organization from the in-site HT server and the DR HT server shouldn't be used (unless there are mailboxes in the DR site). >2. With regard to ?I would remove the DR server from the source servers, then test your mailflow? > >We did this previously ? when only main HT server is running emails are sent and no problem. Create a 2nd Send Connector that uses the HT server in the DR site. Remove the HT server in the DR site from the Send Connector in the "mail" site. When you have one connector and source servers in two different AD sites you'll have a problem. Running the ExBPA while you were in that configuration would probably have pointed that out. >The main problem we are having is this: > >When we have the main exchange on one AD (e.g. Main-AD) and DR exchange on another AD (e.g. DR-AD) the emails start queuing up and not sent out. > >Temporary work around > >If Main-AD and DR-AD are joined to be under one AD e.g. main-AD then mails go via DR mail server, this provides a temporary solution to the queuing issue. > >However this temporary solution has a knock-on effect for DFS hence we need to retain 2 separate AD?s environment. > >The 10 million dollar question is, under 2 AD?s environment Main-Ad & DR-AD, how can we get the e-mail sent out with being held queuing on the main HT server? Try the 2nd Send Connector suggestion. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

1. As mentioned, if the queues are on the DR server, there should be no reason why they cant send emails out to the internet. Verify routing and see if a route exists from the DR server to the internet. You may want to ask you network team to verify. Also, what I'm trying to understand is why external emails are going via your DR. Not sure what setup you have now, as it's changed from a single AD site to 2 AD sites. I'm going on the basis that you will have 2 AD sites as this seems like your goal. So, as mentioned in my post above as well as Rich's, try creating 2 send connectors, i.e one for each site. Email should not route via DR in your case if your have setup the AD sites correctly and have no active mailbox copies in the DR site. Also, if your send connectors are setup right. 2. I would also make sure, that although you have 2 AD sites, that your IP configuration is actually correct, i.e so that the DR server isn't being mapped to Main AD site. Make sure your subnets are also correctly mapped to the correct AD sites. 3. After creating the 2 send connectors check your results. One other config you can try is to scope the send connector so it's only used by the HUB's in the maine site, i.e MAIN AD siteSukh

On Tue, 24 May 2011 09:04:15 +0000, Sukh828 wrote: >1. As mentioned, if the queues are on the DR server, there should be no reason why they cant send emails out to the internet. He hasn't said yet were the messages are remaining enqueued. All he's said is that "The email queuing up are for external". If the messages remain on the HT servers in the mail site, the knowing the "next hop" is important. If the messages from the mail site remain queued on ther DR HT server then knowing the reason why they aren't delivered is important. [ snip ] >2. I would also make sure, that although you have 2 AD sites, that your IP configuration is actually correct, i.e so that the DR server isn't being mapped to Main AD site. Make sure your subnets are also correctly mapped to the correct AD sites. > >3. After creating the 2 send connectors check your results. One other config you can try is to scope the send connector so it's only used by the HUB's in the maine site, i.e MAIN AD site That won't help if things actually have to run in the DR AD site. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

@Ma1 - Any update? Changes in config? If you restrict the scope to the MAIN AD site, then the HUB in DR Site should not use this connector. If a failiover/switchiver occurs, then you can easily set the scope to the DR site with a few clicks and within a minute right. It just means a manual process which must be documented in your DR procedure.Sukh

Good Morning Rich / Sukh Thank you for your replies and comments. Just to focus, the main problem we are having: When we have the main exchange on one AD (e.g. Main-AD) and DR exchange on another AD (e.g. DR-AD) the emails start queuing up AT MAIN SITE and not sent out. That is why we have the Temporary work around of joining the two sites one AD so e-mails can go out. Understand active/passive HT, No active mail boxes at DR site. We could not do the changes yesterday, it is a live environment so need make the changes at a time slot that does not impact on the business operation. Could not do it yesterday We are trying to install the second connector today. Any thoughts are appreciated. Regards, MA MA-1

Good Morning Rich / Sukh Thank you for your replies and comments. Just to focus, the main problem we are having: When we have the main exchange on one AD (e.g. Main-AD) and DR exchange on another AD (e.g. DR-AD) the emails start queuing up AT MAIN SITE and not sent out. That is why we have the Temporary work around of joining the two sites one AD so e-mails can go out. Understand active/passive HT, No active mail boxes at DR site. We could not do the changes yesterday, it is a live environment so need make the changes at a time slot that does not impact on the business operation. Could not do it yesterday We are trying to install the second connector today. Any thoughts are appreciated. Regards, MAMA-1

On Wed, 25 May 2011 08:32:17 +0000, Sukh828 wrote: > > >@Ma1 - Any update? Changes in config? > >If you restrict the scope to the MAIN AD site, then the HUB in DR Site should not use this connector. If a failiover/switchiver occurs, then you can easily set the scope to the DR site with a few clicks and within a minute right. It just means a manual process which must be documented in your DR procedure. Sure . . . provided the failover happens when someone's watching. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Sukh / Rich Thank you for your thoughts and comments, very helpful. We have done the following: Created a second send internet connector e.g. “internetconnectorDR” and added the DR exchange server “Exchage02” as a source server Removed DR Exchange server “Exchage02” as a source from the main connector “internetconnector” Separated the AD’s as they were originally before the temporary work around back to two separate sites / separate AD’s So final setup under 2 separate AD’s main Exchage01 is source server for main connector internetconnector and DR Exchage02 is the source server for the second connector internetconnectorDR This seem to work ok for both Exchange and DFS Thank you for your assistance, it is really appreciated. Regards, MAMA-1