Cross Download: exchange

Showing posts with label exchange. Show all posts

Friday, March 24, 2017

Exchange Get VirtualDirectory cmdlets take a long time to run in Exchange Server

In a Microsoft Exchange Server environment, you run one of the following cmdlets to obtain the properties of a virtual directory for a server in another site thats connected over a wide area network (WAN):

Get-WebServicesVirtualDirectory
Get-OwaVirtualDirectory
Get-ActiveSyncVirtualDirectory
Get-AutodiscoverVirtualDirectory
Get-EcpVirtualDirectory
Get-PowerShellVirtualDirectory
Get-OABvirtualDirectory

However, the cmdlet takes much longer than expected to run (about 15 minutes).

Workarond:

To work around this issue, use the AdPropertiesOnly switch with the cmdlet in the calls to the IIS metabase.

Example 1
Get-OwaVirtualDirectory -Server Contoso –AdpropertiesOnly
Example 2
Get-OwaVirtualDirectory -Identity "Contosoowa (default Web site)" –AdpropertiesOnly
The ADPropertiesOnlyswitch specifies that only the virtual directory properties that are stored in Active Directory Domain Services (AD DS) are returned.

For more information about ADPropertiesOnly switch, see Get-OwaVirtualDirectory.

Support KB 2896472:

https://support.microsoft.com/en-us/kb/2896472

Available link for download

Exchange 2007 10 How export to pst single mailbox or all mailboxes with single command or powershell command

With Exchange 2010 SP1 there is possibility to automatically export single mailbox or all mailboxes and convert them to .pst file (it could be alternative backup procedure)

Here are steps that you need to follow:

1. Give a domain user ability to import Export mailbox with this command

New-ManagementRoleAssignment –Role "Mailbox Import Export" –User "Domainuser_domain"

otherwise:

New-MailboxExportRequest -Mailbox "TEST, user" -FilePath SERVERNAMEshare_nameTEST.user-export.pst

2. Create a network share and give “Exchange Trusted Subsystem” groups read and write on that share.

3. Create export request like follow:

New-MailboxExportRequest -Mailbox “mailbox_bame” -FilePath “network share”

4. To verify Export request status

Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

Get-MailboxImportRequest

5. To view mailbox export completed and remove them:

Get-MailboxExportRequest | where {$_.status -eq "Completed"}

Remove export mailbox completed:

Get-MailboxExportRequest | where {$_.status -eq "Completed"} | Remove-MailboxExportRequest

Get-MailboxExportRequest | Remove-MailboxExportRequest

6. If you want to backup all mailboexes you can use this script

foreach ($i in (Get-Mailbox | Where {$_.ExchangeVersion.ExchangeBuild.Major -eq 14})) { New-MailboxExportRequest -Mailbox $i -FilePath "SERVER_BAMESHARE${$i.Alias).pst" }

In case you want to backup only some mailboxes you need to create a .csv file with first row with Alias name followed by Mailboxes alias name or simple mailbox name

foreach ($i in (Import-Csv .exports.csv)) { New-MailboxExportRequest -Mailbox $i.Alias -FilePath "SERVER_BAMESHARE$($i.Alias).pst" }

Later you can perform Mass Exports as a scheduled task.

<----------->

<===============================>

With Exchange 2007 SP3 there is possibility to automatically export single mailbox or all mailboxes and convert them to .pst file but procedure is slightly different than Exchange2010

On Exchange 2007 otherwise you need to perform this task on 32 bit Server with outlook 2003 SP2 using this syntax.

In order to export or import mailboxes to PST files the following requirements must be met:

Export/Import to PST must be run from a 32 bit client machine with Exchange Management Tools installed (Version Exchange 2007 SP1 or later). The 32bit requirement comes from a dependency with the Outlook client.

Microsoft Exchange Server 2007 Management Tools (32-Bit)
Either Outlook 2003 or Outlook 2007 must be installed on the client machine.

The user running the task must be an Exchange Organization Admin or an Exchange Server Admin on the server where the mailbox to export/import lives.

Export-Mailbox -Identity “domainuserdomain” -PSTFolderPath f: ArchiviedPSTArchiviedusers.pst

More details here:

https://blogs.technet.microsoft.com/exchange/2007/04/13/how-to-export-and-import-mailboxes-to-pst-files-in-exchange-2007-sp1/

[original article]

http://exchangeserverpro.com/export-mailboxes-exchange-server-2010-sp1/

http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/

<-------->

You could be interested to these similar article too:

Exchange 201X- How get all users who have a forwarding email, redirect rule and delegate permission on them mailboxes or Outlook folders

Exchange 2013 - How to monitor it with powershell command

Exchange - Microsoft Exchange Server User Monitor

Exchange 2010 - Poster dellarchitettura

Exchange 2010 - How to monitor Exchange Health

Exchange 2010 - How export to pst single mailbox or all mailboxes with single command or powershell command

Exchange 2013 - How to monitor it with powershell command

Exchange 2010 - How to get info on Mobile devices connected via ActiveSync, quarantine any new device and remote Wipe them.

Exchange 2003/2010 - Add a photo to user contact

Available link for download

Exchange Your Administrator has made a change and requires you to restart Outlook

If you are facing this kind of problem on Exchange and outlook there are severar reason fo that.

1. At first you can download this tool and evaluate any Office 20XX client problems

Office Configuration Analyzer Tool (OffCAT) information

https://support.microsoft.com/en-us/kb/2812744

https://www.microsoft.com/en-us/download/details.aspx?id=36852

The problem arises when an Outlook client connects to the CAS array and initially, if outlook connects to the CAS array member that contains the PF role, then Outlook converges all connections and displays both the Public and Private logons as one single connection (the CAS array name). When the Clients IP address changes, and it Re-connects, if it gets connected to a CAS array member that does not have the PF server, then we get an ECwrong server Response from Exchange, Outlook in its reconnect logic Cannot follow the Redirection Result that contains the correct PF server name, and displays the Error "The Administrator has made a change that requires you restart Outlook"

2. Mitigations:

You have the option to completely suppress the dialog:

How to suppress the pop-up "The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook" in Outlook 2010

• Uncheck the option “Show Microsoft Exchange Messages” from the Outlook icon on taskbar, and test the behavior.

This setting is controlled by the registry value..

HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0OutlookDisplay TypesBalloons

Name: Exchange

Type: DWORD

Value: 1 (on) / 0 (off)

3. It could be related to Public folder problem

https://msexchange.me/2014/04/20/the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook/

https://exchangemaster.wordpress.com/tag/the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook/

https://msexchange.me/2014/04/20/the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook/

http://paulroman.pras.ro/2012/08/the-microsoft-exchange-administrator.html

4. If you put in standby your pc and outlook is not correctly closed autodiscover and pc wake un can give you that alert

[update 2016.05.18]

5. Here is an interesting article that explain ADSI edit check to view if Exchange DB references to wrong Public Folder DB

https://jaapwesselius.com/2014/08/05/the-microsoft-exchange-administrator-has-made-a-change/

[UPDATE 2016.05.30]

On a DAG Exchange 2010 configuration here is an interesting article that indicate public folder wrong configuration was the main problem, in my case was the correct answer.

On a Exchange server PF was correctly configured with replication, on the other one PF was not well configurated replication, once done that everythings worked better.

http://www.msexchangegeek.com/the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook/

Available link for download

Exchange Server 2007 Service Pack 3

Overview
Microsoft Exchange Server 2007 Service Pack 3 (SP3) has been designed specifically to meet the challenges facing our customers and to help address the needs of all the different businesses and organizations utilizing our Exchange Server 2007 enterprise messaging system.

Exchange Server 2007 SP3 is a mission-critical communications tool that enables employees to be more productive and access their information anywhere and anytime while providing a messaging system that enables rich, efficient access to e-mail, calendar items, voice mail, and contacts.

For administrators, Exchange Server 2007 SP3 provides further flexibility with the addition of Windows Server 2008 R2 support for server roles and Windows 7 support for the Exchange management tools. These additions, along with enhancements for the advanced protection options against e-mail security threats, such as spam and viruses and the tools which help manage internal compliance and high availability needs provide Exchange administrators with the tools they need to manage their Exchange 2007 environments efficiently.

Clean installations of Exchange 2007 SP3 on a new server are possible by using this download in the same manner as you would install Exchange 2007 RTM, Exchange 2007 SP1 or Exchange 2007 SP2.

System requirements

Supported Operating Systems: Windows 7, Windows Server 2003 R2 (32-Bit x86), Windows Server 2003 R2 x64 editions, Windows Server 2003 Service Pack 2, Windows Server 2003 Service Pack 2 x64 Edition, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP Service Pack 3

DOWNLOAD

Available link for download

Exchange 2010 How to create report about biggest mailboxes exportied to csv

If you need to identify users that have bigger mailboxes size you can use these scripts on your exchange server:

First 100 mailboxes

Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | Sort-Object TotalItemSize -Descending | Select-Object DisplayName,TotalItemSize -First 100 | Export-Csv -Path "c:Top100mailboxusersSize_1_00.csv" -Delimiter ";"

All mailboxes

Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | Sort-Object TotalItemSize -Descending | Select-Object DisplayName,TotalItemSize | Export-Csv -Path "c:AllmailboxusersSize_1_00.csv" -Delimiter ";"

Meanwhile you could be interested to get, for each mailboxes, relatives limits that was setting up on Exchange server

Get-Mailbox -ResultSize Unlimited | Select-Object DisplayName,Database,IssueWarningQuota,ProhibitSendQuota,ProhibitSendReceiveQuota | Export-Csv -Path "c:AllmailboxusersIssueWarning_1_00.csv" -Delimiter ";"

So in this specific case you will get two .csv reports.

AllmailboxusersIssueWarning_1_00.csv
AllmailboxusersSize_1_00.csv

You can merge these files importing these .csv files in a single excel file and and use this Excel File function:

CERCA.VERT(A13;AllMailboxexLimits!1:1048576;3;FALSO)

In english function name should be find.vert

Where A13 is our Mailboxes user name and first column (AllmailboxusersSize_1_00.csv)

Where AllMailboxexLimits!1:1048576 is second Excel tab imported (AllmailboxusersIssueWarning_1_00.csv)

Where 3 is the relavive IssueWarningQuota found in second Excel tab imported (AllmailboxusersIssueWarning_1_00.csv)

You can repeat this task for other values:

ProhibitSendQuota
ProhibitSendReceiveQuota

<-----------other -------="" articles="" blog="" related="">

<-------->

Available link for download

Exchange 2003 Fixing “backOfficeStorage” MBX is not accessible Error When Opening OWA Folders

If you got, on Exchange Server this error:

“backOfficeStorage” MBX is not accessible Error When Opening OWA Folders

I succesfully solved appling this procedure:

https://ittutorials.net/fixing-backofficestorage-mbx-is-not-accessible-error-when-opening-owa-folders

Available link for download

Exchange Microsoft Exchange PST Capture 2 0

Microsoft released an interesting tool to discover pst on remote Pcs and published with GPO.

In precedent blog post we mentioned implementation that I did with .vbs and .cmd that collect, with GPO, local pst and they are backup up with hobobcopy and robocopy.

http://www.alessandromazzanti.com/2015/09/backups-how-to-backup-remote-clients.html

Microsoft Exchange PST Capture 2.0 is used to discover and import .pst files into Exchange Server or Exchange Online.

https://www.microsoft.com/en-us/download/details.aspx?id=36789

In any case this article well explain tool usage and implementation:

http://msexchangeguru.com/2016/01/29/pst-capture-walk-through/

Available link for download

Exchange 201x How to enable Mailbox logging

On Exchange is very important to view if there are any strange accesses on other users mailboxes.

Here they are some command lines that works fine on Exchange 2016:

Set-Mailbox -AuditEnabled $true

Get-Mailbox |fl name,AuditEnabled

To view log retention:

Get-Mailbox | fl name,AuditEnabled,AudiLogAgeLimit

If you want to change log retention (default 90 days)

Set-Mailbox -Identity ” -AuditLogAgeLimit numberofdaysto keep

Get-Mailbox -ResultSize Unlimited -Filter {RecipientTypeDetails -eq “UserMailbox”} | Set-Mailbox -AuditLogAgeLimit 180

If you want to enable logging on all mailboxes:

Get-Mailbox -ResultSize Unlimited -Filter {RecipientTypeDetails -eq "UserMailbox"} | Set-Mailbox -AuditEnabled $true

Disable Mailbox logging

Set-Mailbox -AuditEnabled $false

Consider that Mailbox Owner activities are not logged, to enable it you must consider that we will have plenty of auditings:

Set-Mailbox -AuditEnabled $true

Get-Mailbox |fl name,AuditEnabled

Get-Mailbox -ResultSize Unlimited -Filter {RecipientTypeDetails -eq "UserMailbox"} | Set-Mailbox -AuditEnabled $true

Disable the mailbox audit logging:

Set-Mailbox -AuditEnabled $false

Here they are whtat we log with these changes

Original Technet Article

https://technet.microsoft.com/it-it/library/ff459237(v=exchg.160).aspx

Action	Description	Admin	Delegate***	Owner
Copy	An item is copied to another folder.	Yes	No	No
Create	An item is created in the mailbox. (For example, a message is sent or received.) Note that folder creation isnt audited.	Yes*	Yes*	Yes
FolderBind	A mailbox folder is accessed.	Yes*	Yes**	No
HardDelete	An item is deleted permanently from the Recoverable Items folder.	Yes*	Yes*	Yes
MailboxLogin	The user signed in to their mailbox.	No	No	Yes
MessageBind	An item is accessed in the reading pane or opened.	Yes	No	No
Move	An item is moved to another folder.	Yes*	Yes	Yes
MoveToDeletedItems	An item is moved to the Deleted Items folder.	Yes*	Yes	Yes
SendAs	A message is sent using Send As permissions.	Yes*	Yes*	No
SendOnBehalf	A message is sent using Send on Behalf permissions.	Yes*	Yes	No
SoftDelete	An item is deleted from the Deleted Items folder.	Yes*	Yes*	Yes
Update	An items properties are updated.	Yes*	Yes*	Yes

You can get reporting here:

more details :

Microsoft - Enable or disable mailbox audit logging for a mailbox on Exchange 2016

https://technet.microsoft.com/it-it/library/ff461937(v=exchg.160).aspx

Microsoft - Mailbox audit logging in Exchange 2016

https://technet.microsoft.com/it-it/library/ff459237(v=exchg.160).aspx

Microsoft - Mailbox Audit Logging on Exchange 2010

https://technet.microsoft.com/en-us/library/ff459232(v=exchg.141).aspx

Microsoft - Mailbox Audit Logging on Exchange 2013

https://technet.microsoft.com/en-us/library/ff461939(v=exchg.150).aspx

Available link for download

Exchange 2010 How to identify GD DC used and change it

If you need to verify Dc used from your Exchange server you can view procedure following this simple workflow:

http://www.sysadminlab.net/exchange/which-global-catalog-gc-is-my-exchange-2010-using

Available link for download

Exchange Scoped Send Connector meaning and how to manually change Routing weight overriding Ad Sites costs

On Exchange Server about hub transport connector for outgoing email there is an option that some time it could be misunderstood, it is "Scoped Send Connector" checkbox.

When you mark a send connector as scoped, this means it can only be used by Exchange 2007/2010 hub transport or Exchange 2013 mailbox servers in the same Active Directory site as the send connector.

If not selected, the connector can be used by all transport servers in the Exchange environment.

A Send Connector is not bound/limited to any specific Active Directory site but a merely object in Active Directory!

Example:

Let us suppose to have an AD Site called "Contoso HQ" and the site has 4 transport servers whether they be Exchange 2010 Hub Transport servers or Exchange 2013 mailbox servers.

Two of these servers are marked as source servers of the scoped send connector and two arent.

The two servers which are a member as a source server of the send connector can obviously use the send connector. The other two transport servers in the same Active Directory site which are not source servers can also use the scoped send connector, all other transport servers in other sites - bad luck!

Unchecking as scoped it means that transport servers in other sites can relay through the send connector if there is no closer option for external mail relay.

To get AD Site and View Cost:

Get-AdSiteLink

Almost all are aware of the fact that Exchange 2010 uses AD Sites and Services information to route emails from one AD site to another.

So you could think to change AD Sites costs but, in large organizations, as changing the existing AD site costs may affect the production network or the AD team just don’t want to make any changes.

Exchange 2010 (infact 2007 as well) has a solution for the above scenario. There is a way by which you can change the email routing without making any changes to the AD site link costs. It is known as “Exchange Cost” and is not configured by default.

This is the command syntax:

Set-ADSiteLink –identity “link name” –ExchangeCost “cost”

The maximum message size that passes through a site link can be restricted as well. It will come in handy if the link between the site is not great. Run the command below to specify a size limit for communications between various AD sites.

Set-ADSiteLink –identity “link name” –MaxMessageSize “size”

[original Article http://clintboessen.blogspot.fr/2014/01/what-are-scoped-send-connectors.html]

[http://theucguy.net/change-email-routing-using-exchange/]

Available link for download

Exchange mailbox recovery and repair

Exchange mailbox recovery and repair

Given the increasing number of transactions that people e-mail these days and the importance of the contents of the e-mail, people need an effective way to get all the messages you send and those who were sent to tackle . For, as already mentioned, if the system is rebellious, it is very confusing, and things would go wrong. Outlook Express is a software that will effectively fulfill the same task, to ensure that things do not go missing or are not missed or misplaced.

Speaking of Outlook Express is one of the best programs developed by Microsoft, up to date. One of his sons helps the user to program your incredible things in a very organized manner. First, the best use of Outlook Express is to write, to compose and e-mail project helps. This was a very effective tool because many people in business to be more efficient by e-mail. Besides this, using Outlook Express, you can also plan your things, notes, calendar attachments about your use to make, etc., there were no other software that has many advantages associated with it, and because the same reason, has become a great success.

There were some problems with Outlook Express, but you need to restore the Exchange mailbox to separate them. There are possibilities of e-mails and files are corrupted, and pull for the same reason, the people, to keep the backup in the form of OST. In fact, it would be good OST file to PST file because it is a better way to do things.

Talking Mailbox Exchange Recovery is required if the Outlook mailbox is damaged or collapsed for several reasons. Now, for each individual contains the e-mail a large number of very important facts, details and other things that, if they have lost, can lead to very different problems. This is the reason why people pay much attention to the restoration of mailboxes to Exchange.

There are a variety of software available on the Internet, that would work for you. The only thing you need is to get through a search engine and find the software you want. After receiving the software, you must install the file. Once the installation file that you downloaded, you must complete the program on your computer and run it. Once you repair Exchange mailbox would be conducted in person and all files and data would be restored.

Keep one thing in mind that the software that you use must come from a reliable source. Otherwise, you run a risk of virus infiltration into the computer, and causes more damage and caused more problems.

EDB to PST is one of the hot issues that people face every day and then this article was written to describe the Rapid Recovery Convert EDB to PST software such as Microsoft Exchange e-mail recovery.
Exchange mailbox recovery and repair

Available link for download

Exchange 2010 How to monitor Exchange Health

There are several ways to monitor Exchange Server

In precedent article I mentioned powershell script for that purpose on Exchange 2013 server.

http://www.alessandromazzanti.com/2015/06/exchange-2013-how-to-monitor-it-with.html

1. you can at first remotely execute this commands

Test-Servicehealth
Test-ServiceHealth SERVERNAME
Test-ServiceHealth br-ex2010-mb | ft Role,RequiredServicesRunning -auto

Get-ExchangeServer | Test-ServiceHealth | ft Role,RequiredServicesRunning -auto

Get-MailboxDatabase
Get-MailboxDatabase -Status | ft name,last* -auto

Get-MailboxDatabaseCopyStatus | fl name, contentindexstate

(Get-DatabaseAvailabilityGroup) | ForEach {$_.Servers | ForEach {Get-MailboxDatabaseCopyStatus -Server $_}}

Test-MapiConnectivity - server SERVERNAME

Test-MailFlow between two databases/servers

2. Generate Health Report for an Exchange Server 2016/2013/2010 Environment

This PowerShell script performs a series of health checks on Exchange Server 2010 and 2013 Database Availability Groups and then outputs the results to screen or HTML email.

https://gallery.technet.microsoft.com/office/Generate-Health-Report-for-19f5fe5f

3. Here they are full Microsoft List scripts:

https://gallery.technet.microsoft.com/site/search?query=exchange%202010%20health%20check&f%5B2%5D.Value=exchange%202010%20health%20check&f%5B2%5D.Type=SearchText&f%5B0%5D.Value=Exchange&f%5B0%5D.Type=RootCategory&f%5B0%5D.Text=Exchange&f%5B1%5D.Value=Exchange2010&f%5B1%5D.Type=SubCategory&f%5B1%5D.Text=Exchange%202010&ac=5

4. Exchange 2010 Health Check

The purpose of this PowerShell script is to send a report on the health of various areas of the Microsoft Exchange 2010 environment. This script should work with PowerShell 2.0 and later.This script is designed so that it can be run in an automated fashion from a Scheduled Task.

https://gallery.technet.microsoft.com/Exchange-2010-Health-Check-647cd668

<---------->

Consider that these scripts can be scheduled to monitor continuously

005

[update -1]

Test-ReplicationHealth servername

Get-ClientAccessServer | Test-MRSHealth | Fl check,Passed,Identity,IsValid
Get-ClientAccessServer | Test-MRSHealth

Interesting article:

http://www.computerperformance.co.uk/exchange2010/exchange_2010_powershell.htm

[update 2]

http://exchangeserverpro.com/powershell-script-exchange-server-health-check-report/

scheduled task syntax
-command

"C:_Script_MonitoringTest-ExchangeServerHealth_1_0.ps1 -SendEmail -ReportMode -Log"

c:WindowsSystem32WindowsPowerShellv1.0powershell.exe

My scheduled task settings for this script are:

•Run whether user is logged on or not

•Run with highest privileges

•Action: Start a program

•Program: powershell.exe

•Arguments:

-command “C:ScriptsExchangeServerHealthTest-ExchangeServerHealth.ps1 -Log -SendEmail”

<-------->

Available link for download

Exchange 2010 A storage transient failure has occurred during content conversion

On Exchange Server on traking log and mail not delivered we saw this error:

A storage transient failure has occurred during content conversion.

How To Check Exchange Rollup Version

Exchange Server Updates: build numbers and release dates

Exchange 2010 SP3 CU2 will solve problem.

To apply a workaround you can see this article

http://enterpriseit.co/microsoft-exchange/transport-bug-exch-2010-win-2012-550-4-4-7-queue-expired/

Otherwise solution it was to apply CU 2 at least following this procedure:

Execute Exchange Powershell as administrator
Launch this syntax:

msiexec /update Exchange2010-KBxxxxx-x64-en.msp

Available link for download

Exchange 2007 10 “ 451 4 7 0 Timeout Queues Timeout”

During last years we faced to a very strange problem along Exchange queues that got stacked with a rarely and particular error:

“ 451 4.7.0 Timeout”

To better undestand where it was problem we enabled verbose logging on each Exchange server Hub Transport that faced problems to send intrasite and externally emails:

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoViUlPY2YsDMm3OvGPatnb-O7jXvmQA27xni651MdVmg3hbVAFWnv8CxZbUle77QJ4e-WW7agZfxyJETOh-V2urrvPPduAw3YqWAAkhnenJIRHPIPImHo3-LrITkgmYIsxlTnd22vAN4S/s1600/1.jpg

There was “ 451 4.7.0 Timeout” as you can see.

Then we executed ping command with a particular parameter to understand if there was some packed dropped during connection:

And ping computer_name or IP_address -f -l 1472 was unsuccessfully. (http://support2.microsoft.com/kb/159211/en-us )

So, following this article, we understood that it was a networking problem and we opened a major case to MPLS provider and we solved after their intervention.

https://social.technet.microsoft.com/Forums/en-US/6197ce1e-2ba0-46d4-a3d4-3799d6c4ee9c/470-timout-waiting-for-client-input-with-big-emails-on-some-domains?forum=exchangesvrsecuremessaginglegacy

[update 2016.06.07]

Here they are articles about MTU and ping parameter and how to enable verbose logging on exchange server about send/receive connectors

How to Troubleshoot Black Hole Router Issues

SMTP Routing in Exchange 2010 (Part 4)

Available link for download

Friday, March 24, 2017

Exchange Get VirtualDirectory cmdlets take a long time to run in Exchange Server

Saturday, March 18, 2017

Exchange 2007 10 How export to pst single mailbox or all mailboxes with single command or powershell command

Sunday, March 5, 2017

Exchange Your Administrator has made a change and requires you to restart Outlook

Thursday, February 16, 2017

Exchange Server 2007 Service Pack 3

Monday, February 13, 2017

Exchange 2010 How to create report about biggest mailboxes exportied to csv

Exchange 2003 Fixing “backOfficeStorage” MBX is not accessible Error When Opening OWA Folders

Sunday, February 12, 2017

Exchange Microsoft Exchange PST Capture 2 0

Thursday, February 9, 2017

Exchange 201x How to enable Mailbox logging

Wednesday, January 25, 2017

Exchange 2010 How to identify GD DC used and change it

Monday, January 16, 2017

Exchange Scoped Send Connector meaning and how to manually change Routing weight overriding Ad Sites costs

Monday, December 26, 2016

Exchange mailbox recovery and repair

Friday, December 16, 2016

Exchange 2010 How to monitor Exchange Health

Monday, November 21, 2016

Exchange 2010 A storage transient failure has occurred during content conversion

Sunday, October 9, 2016

Exchange 2007 10 “ 451 4 7 0 Timeout Queues Timeout”