Outlook performance

Troubleshoot Outlook performance issues – Exchange/Office 365

It is not the first, and it will not be the last client that ask me what to do to fix Outlook performance issues.

Dennis from blogoffice365.com has written an article that mirrors what I usually recommend to my customers.

Here it is Dennis fantastic post. To see the original post click here.

(more…)

Search message tracking logs

Message tracking records the message activity as mail flows through the transport pipeline on Mailbox servers and Edge Transport servers. You can use the Get-MessageTrackingLog cmdlet in the Exchange Management Shell to search for entries in the message tracking log by using specific search criteria. For example:

  • Find out what happened to a message that was sent by a user to a specific recipient.
  • Find out if a transport rule acted on a message.
  • Find out if a message sent from an Internet sender made it into your Exchange organization.
  • Find all messages sent by a specified user during a specified time period.

This example searches the message tracking logs on the local server for all entries from 2/20/2018 8:00 AM to 2/20/2015 5:00 PM for all FAIL events where the message sender was sender@mutega.se

Get-MessageTrackingLog -ResultSize Unlimited -Start “2/20/2018 8:00AM” -End “2/20/2018 5:00PM” -EventId “Fail” -Sender “sender@mutega.se”

This example searches the message tracking logs on the local server for all entries from 2/20/2018 8:00 AM to 2/20/2015 5:00 PM for all emails sent to to@mutega.com where the message sender was sender@mutega.se

Get-MessageTrackingLog -ResultSize Unlimited -Start “2/20/2018 8:00AM” -End “2/20/2018 5:00PM” -EventId “Fail” -Sender “sender@mutega.se” -Recipients “to@mutega.com”

More info (Source article): https://technet.microsoft.com/en-us/library/bb124926%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396

Exchange

Exchange 2010/2013 CU stuck at Languages install

This simple solution can save you a lot of time.

This issue can happen on the upgrade of Microsoft Exchange 2010 and  2013 when you apply a CU. The upgrade gets stuck at Languages, step 9, forever.

It turns out that the solution is very simple, this happens because System Center 2012 Endpoint Protection was installed on the server automatically by the SCCM, and this software uses the “Same Engines” for Languages.

Solution:

  1. Uninstall the Endpoint Protection on the server.

After uninstalling the Endpoint Protection, the Exchange update will continue.

When you do the upgrade of the Exchange CU finish, you can restart the server and install again the Endpoint Protection.

Hope this saves you some time!

porco_tempo.jpg

a-team_A_verylitle