New High Availability Features in Exchange 2010 SP1

New High Availability Features in Exchange 2010 SP1

* Continuous replication - block mode
In the RTM version of Exchange 2010 and in all versions of Exchange 2007, continuous replication operates by shipping copies of the log files generated by the active database copy to the passive database copies. Beginning with SP1, this form of continuous replication is known as continuous replication - file mode. SP1 also introduces a new form of continuous replication known as continuous replication - block mode




* Active mailbox database redistribution
This feature is present in two forms. The first form is a script that can be periodically run by administrators to balance the distribution of active database copies across a database availability group (DAG). The second form we hope to implement is the addition of copy distribution awareness to Active Manager's best copy selection (BCS) process.

* Improved Outlook cross-site connection behavior and experience

* Enhanced datacenter activation coordination support  :  In the RTM version, DAC mode is limited to DAGs with at least three members that have at least 

two or more members in the primary datacenter.

In SP1, DAC mode has been extended to support two-member DAGs that have each member in a separate datacenter. 


* New and enhanced management and monitoring scripts
CheckDatabaseRedundancy.ps1 (new) 
StartDagServerMaintenance.ps1 and StopDagServerMaintenance.ps1 (new)
CollectOverMetrics.ps1 (enhanced)
CollectReplicationMetrics.ps1 (enhanced)


* Improvements in failover performance

http://blogs.technet.com/b/jribeiro/archive/2010/04/26/new-high-availability-features-in-exchange-2010-sp1.aspx

Manually move the Primary Active manager in DAG

Under any circumstances, if you have to move the Primary Active Manager to another server of a DAG then from Exchange management shell use the following command

cluster.exe “DAG Name” /MoveTo:NewDAG

what is BDAT (Binary Data)

BDAT
-------------------------------------------------------
The SMTP BDAT command is an alternative to the DATA command, which can be used when a remote SMTP server presents the CHUNKING verb. CHUNKING is an ESMTP functionality. Microsoft Exchange servers implement this feature by default, as do other SMTP servers.

The BDAT verb takes two arguments. The first argument indicates the length, in octets, of the binary data chunk. The second optional argument indicates that this data chunk is the last.

Servers that offer the BDAT extension MUST continue to support the regular SMTP DATA command.

After all MAIL and RCPT responses are collected and processed, the message is sent using a series of BDAT commands. The BDAT command takes one required argument, the exact length of the data segment in octets. The message data is sent immediately after the trailing <CR> <LF> of the BDAT command line. Once the receiver-SMTP receives the specified number of octets, it will return a 250 reply code.

The optional LAST parameter on the BDAT command indicates that this is the last chunk of message data to be sent. The last BDAT command may have a byte-count of zero indicating there is no additional data to be sent. Any BDAT command sent after the BDAT LAST is illegal and MUST be replied to with a 503 "Bad sequence of commands" reply code. The state resulting from this error is indeterminate. A RSET command MUST be sent to clear the transaction before continuing.

DATA and BDAT commands cannot be used in the same transaction. If a DATA statement is issued after a BDAT for the current transaction, a 503 "Bad sequence of commands" MUST be issued.

The equal logic array sends messages in small chunks using BDAT command. Exchange 2007 & 2010 will by default tarpit (slow down) any BDAT command that is not the “LAST” chunk. Each chunk gets delayed 5 seconds before Exchange confirms it has received it. As there are plenty of BDAT commands sent per message with a 5 second delay per packet it adds up very quickly. Now equal logic array has a timeout of 2 minutes and hence the failure

The problem occurs when multiple email messages are transferred within the same TCP session using multiple BDAT commands. The transfer of a single email per session, with the use of only one BDAT command does not pose a problem.
-------------------------------------------------------

550 5.7.1 Client does not have permissions to send as this sender

​

POP3 and IMAP
-------------------------
Status: offline Clients like IMAP and POP3 uses the Client <servername> Receive -Connector. In order to allow clients to submit messages via this connector, you need to issue below command: 

get-receieveconnector Client <servername> | add-adpermission -user AU -extendedrights ms-Exch-SMTP-Accept-Authoritative-Domain-Sender 
  
Issue 
=============
RE: 550 5.7.1 Client does not have permissions to send as this sender

Resolution
=============

In adsiedit under :  Configuration - Services - Microsoft Exchange - 
<organization name> - Administrative Groups - Exchange Administrative Group
- Servers - <Servername> - Protocols - SMTP Receive Connectors - Client <servername>

Right click and click properties, click the security tab and grant the Authenticated users group the Accept Authoritative Domain Sender allow permission.

Other settings can be checked is as follows

From EMC 
Get-IMAPsettings 
check  logintype,

We checked the settings on the Outlook and is correct. SPA is unchecked.
In Advanced we have IMAP port as 993- SSL.
In outgoing server we have "use same server as incoming server" checked.

Tested mail flow but incoming IMAP passes the test and Sending mail SMTP fails.

How Mail from outlook sent to another outlook via Exchange server

The Mail Submissions Service on the Exchange 

2010 Mailbox Server notifies the Hub 

Transport Server that a message is in the Outbox. The 

Store Driver on the Hub Transport 

Server retrieves the message from the Mailbox Server. 

RPC is used for communication between the Hub and the 

Mailbox Server.


or 

1. The Microsoft Exchange Mailbox Submission service that's running on Mailbox1 notifies an Exchange 2010 Hub Transport server that's located in the same Active Directory site of the new mail item for transport.
2. Using RPC, the store driver component on an Exchange 2010 Hub Transport server in the same Active Directory site retrieves the message and puts it in the Submission queue on the local server.
3. From the Submission queue, the message moves through categorization. The categorizer first performs recipient resolution and determines that joe@contoso.com is an external recipient.
4. The routing component selects the best connector through which to route the message and calculates the least-cost routing path to that connector. In this example, a Send connector has the address space *.contoso.com and is the connector selected by the routing component. All the source servers for this Send connector are located in Site B.
5. The routing component determines the next hop required to reach a source server for the Send connector. The Hub Transport server in Site A queues the message for SMTP delivery to Site B.
6. If the receiving server in Site B is a source server for the Send connector, it queues the message for delivery to that Send connector. If the receiving server isn't a source server for the *.contoso.com Send connector, the message is relayed by using SMTP to a Hub Transport server in Site B that's the source server for the connector.

From Microsoft Site

Netmon from Command Prompt

Netmon from Command Prompt

Start > Run type CMD click OK. 

cd "c:\Program Files\Microsoft Network Monitor 3"

C:\nmcap.exe /network * /capture /file ExchangeTrace-client.chn:100M 


c:\nmcap.exe /Network * /Capture /CaptureProcesses /File ExchangeTrace.chn:100M

In the below example the client IP is 10.10.50.40 and the server IP is 10.1.75.20

nmcap.exe /Network * /Capture "(ipv4.Address == 10.10.50.40 and ipv4.Address == 10.1.75.20)" /CaptureProcesses /File ExchangeTrace.chn:100M

http://blogs.technet.com/b/kpapadak/archive/2011/01/31/template-how-to-take-network-traces-between-clients-and-exchange-servers.aspx


Netmon Command
IPv4.address == IP address

How to LogOff from Command Prompt
shutdown /l = Log off and /f = force  
Eg : C:/> Shutdown /l 
C:/> Shutdown /f

File share folder is inaccessible from the Exchange server 2010

File share folder is inaccessible from the Exchange server.

We checked and found the folder permission is fine.

We added the "Exchange subtrusted system", still the same issue.

We click the "Share" under "Network file and Folder sharing" (>apply > OK)

Now issue is resolved.