Transport architecture from the perspective of the Management Shell

This section briefly reviews the core transport architecture from the perspective of the Management Shell

Get-Queue

Set-Queue
Suspend-Queue
Resume-Queue
Retry-Queue
Get-TransportPipeline
Get-TransportServer
Set-TransportServer
Get-TransportConfig
Set-TransportConfig
Get-NetworkConnectionInfo

To view the Hub Transport pipeline, use the Get-TransportPipeline cmdlet as shown in

The TransportPipeline cmdlet also exposes two transport agents installed by default on the Hub Trans port server: the Journaling Agent and the Transport Rule Agent

Messages can enter the transport pipeline through any of four methods:
* Through an SMTP Receive Connector communicating on port 25.

* Through message files dropped into the Pickup or Replay directories.

* Through placement of messages in the Submission queue by the store driver.

* Through message submission via an agent.

How to get delaynotifiaction and messageExpiration timeout

Using the Set-TransportServer cmdlet you can modify these settings.

Test-MapiConnectivity

This is just FYI on a cmdlet which I use daily – Test-MapiConnectivity!

Use Test-MapiConnectivity to troubleshoot connectivity problems. Remember as the name implies, it will only test MAPI connectivity.

Use this to test connectivity between your users and your servers.

Use it in the following format:

Mailboxes: Get-Mailbox <Mailbox Name> | Test-MapiConnectivity

Mailbox databases: Get-MailboxDatabase <Database Name> | Test-MapiConnectivity

Servers: Get-MailboxServer <Server Name> | Test-MapiConnectivity

A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop working

You configure a failover cluster on some computers that are running Windows Server 2008 R2 and communication failure occurs in the cluster.

Below is the Link from Microsoft Link which resolve the Issue

http://support.microsoft.com/?kbid=2550886

How to remove a mail of mailbox database from server end

User R2 sends an email to a set of people with the subject line “I Love you”. Now, Stallone being the IT manager wants you to delete that email from the server side.

All you gotta do is to run this cmdlet:

Get-Mailbox -Server EXCH | Export-Mailbox -TargetMailbox TempMailbox -TargetFolder ” To Delete” -SenderKeywords R2@E2Esolultions.com -SubjectKeywords ” I Love You ” –StartDate “07/03/13″ –EndDate “07/04/13″ -ExcludeFolders “\Calendar”, “\Contacts”, “\Deleted Items” –DeleteContent –MaxThreads 10

Terms

* Server name is EXCH

* Data will be extracted from user mailboxes to the folder “To Delete” in a mailbox called TempMailbox

* Start date and End Date switch let you choose a date range

* Set the ExcludeFolders switch if you don’t want to search specific folders

* DeleteContent is the switch which deletes the email

* MaxThreads is to specify 10 mailboxes will be processed at a time

Now remember that Export-Mailbox first copies content to the destination mailbox before performing the search and the target mailbox can get quite large and create heavy IO. This is different from creating a transport rule to filter incoming messages.

Users can still use the “Recall” option in outlook.

Exchange 2013 Server Role Architecture

Exchange Server 2010 incoming email with Chinese characters

Working with an outside company that sends automated emails
to us, these emails are html formatted, but when they arrive
the html tags are missing almost every < symbol and added
were chinese characters throughout. It looked something like
this : "ℼDOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN"> 䠼TML>䠼EAD> 䴼ETA http-equiv=Content-Type
content="text/html; charset=unicode"> 㰊META content="MSHTML
5.50.4807.2300" name=GENERATOR>⼼HEAD> 㰊BODY㰾FONT size=2> 吼
ABLE border=1> 吼R> 吼D>䘼ONT size=2>" 

Took a while to find the issue and resolution. Turns out
that the MIME type in the header didn't match either the
encoding type of the email, or our legal notice that gets
added was in a different encoding type, which made Exchange
mess up all of the tags. It could also be because Outlook
uses Word as its HTML viewer instead of IE.

The solution is to add a line to the
edgetransport.exe.config file,
key="DisableDetectEncodingFromMetaTag" value="true" />

This forces Exchange to figure out the encoding on its own
and not trust the MetTag