Microsoft Exchange 2010 end of mainstream support ended 1/13/14

If you are still running Exchange 2010 you now have limited support options, without an extended support contract. Microsoft will still provide security updates to it until 1/14/2020 and may provide other updates for 2010 SP3, but no guarantees on those, and only those with an Extended Hotfix Support contract are entitled to them officially.  “Mainstream” support ended on 1/13/2014, see Microsoft Support Lifecycle details on Exchange 2010 here. Pay support is still provided, but if you come across a bug/issue don’t expect a hotfix for it. The content in TechNet and other forums will still be available and is pretty solid after 5 years.

So if you’re organization is still on Exchange 2010 you need to be looking at migrating to Exchange 2013 or Office 365 ASAP!

From: and see the Lifecycle support FAQ here.

Exchange Support

Posted in Uncategorized | Leave a comment

Remove older Exchange 2013 and IIS Log Files with this one-liner

By default Exchange 2013 logs A LOT of data in the “…\Exchange Server\V15\Logging” folder. In larger environments GBs of data can be logged under the MANY subfolders under this folder.  IIS also logs data and has since the IIS 1.0, but nowhere near as much.

A recent post on the Exchange 2013 Information Sharing Facebook group brought up this issue and a blog post on a PowerShell to script to address it. So if you want to do this via PowerShell see that post.

But the method I use is a one-liner Scheduled Task using FORFILES CLI.

Here’s the one-liner: FORFILES /p “C:\Program Files\Microsoft\Exchange Server\V15\Logging” /s /m *.* /c “cmd /c Del @path” /d -7

But you will probably want to run this daily, so follow the steps below on EACH Exchange server to remove older logs on a regular basis.

  1. Create a scheduled task with the following settings
  2. General: Runs as administrator, or an account that has delete access to the files
  3. General: Select “Run whether user is logged on or not”
  4. Trigger: Daily or how often you want it to remove older files
  5. Action: Start a program
  6. Program/script: FORFILES
    • No path needed, this EXE was included 1st in Windows Vista and is included in Windows Server 2008 and higher 
  7. Arguments: /p “C:\Program Files\Microsoft\Exchange Server\V15\Logging” /s /m *.* /c “cmd /c Del @path” /d -7
  • If you don’t have Exchange 2013 installed in the default path, change the path above to where your E15 Logging folder is
  • Change the “-7″ to control how many days to keep, “-7″ = 7 days

If you also want to delete IIS logs, create a 2nd Task to delete IIS logs, by default they are saved in “C:\inetpub\logs\LogFiles”

Here’s what the scheduled task looks like in Windows 2012 R2:

Posted in Exchange, Technical | Tagged | 1 Comment

Exchange 2013 CU7, 2010 SP3 UR8, 2007 SP3 UR15 released & Known Issues

12/30 Updated: Added a known issue with 2013 CU7 EDGE and two known issues from CU5 & CU6 that still exist in CU7.
12/12 Update: Exchange SP3 UR8 v2 (14.03.0224.002) released, Download here
12/10 Update #2: Exchange 2010 SP3 UR8 pulled due to MAPI RPC bug. Do NOT install UR8 v1 on Exchange 2008.
12/10 Update: 1st known issue added, for 2010 UR8

Microsoft released the latest round of updates today. As always, many updates were included and this round included security update for MS14-075, which can be downloaded for 2013 SP1/CU5 & 2013 CU6 if you just want to apply this security update and not 2013 CU7 now. This latest round was delayed due to some issues found with the install process, see Tony Redmond’s post on this here and a short post on the EHLO blog here for more info.

Microsoft Exchange Team EHLO Blog Post: Exchange releases: December 2014
Tony Redmond’s: Exchange 2013 CU7 debuts along with security fixes and updates for Exchange 2010 and Exchange 2007

2013 CU7                     Download | KB2986485
2010 SP3 UR8           Download v2 | KB2986475
2007 SP3 UR15         Download | KB2996150

Microsoft Exchange Team EHLO Blog Post: Exchange releases: December 2014

Key updates:

  • 2013: Support for Public Folder Hierarchies with up to 250,000 folders
  • 2013: Improved OAB distribution in larger environments
  • 2013: Important updates to backup
  • 2013: AD Schema update
  • 2013: Updates to backup code

If your organization is still using Public Folder and coexisting with Exchange 2007 or 2010 make sure you read this EHLO Blog post: On-Premises Legacy Public Folder Coexistence for Exchange 2013 Cumulative Update 7 and Beyond

There were some changes with the backup code\API in the 2013 CU7 update, therefore it is highly recommended that you do a full backup after installing CU7. In addition, you should test your backup AND recovery procedures and programs to ensure they are still working as expected after applying CU7. The changes affect the ESE database engine that can cause restores to fail.

Note: For those organizations running Exchange in a Hybrid configuration with Exchange Online (EXO)/Office 365 or using Exchange Online Archiving (EOA) you are required to deploy the most current updates.

This blog post will be updated to include links to other blogs and KBs as they come out about these releases. I will also add a Known Issues section once I have some items to add.

For Known Issues on 2013 CU6 see this blog post:

Known Issues

For 2013 CU7

  • Unable to install 2013 Edge role on a domain joined server
  • Microsoft Exchange Health Manager service stops
    • For more details and resolution see KB3017629
    • This issue 1st appeared in CU5
  • Safety Net hold time settings are not synced to Exchange Server 2013 Edge
    • For more details and workaround see KB3019650
    • This issue 1st appeared in CU6

For 2010 SP3 UR8

None have come to my attention yet for 2007 or 2013 updates… For Known Issues with the previous round of updates see:

Posted in Exchange, Technical | Tagged , | 4 Comments

My first week with Office 365 Clutter


Review of the new Office 365 OWA Clutter feature by Paul.

Originally posted on Paul's Down-Home Page:

Immediately after Microsoft announced that Clutter was available, I enabled it in all my personal tenants and started training it. As you may recall, you can train Clutter in two ways: implicitly (as it sees how you interact with mail from particular senders, such as by ignoring it or deleting it without reading it) or explicitly (by moving messages into or out of the Clutter folder). Because I’m fairly impatient, I set about explicit training by moving messages to the Clutter folder. I’ve done this with all of the clients I use: Outlook for Mac, OWA, Outlook 2013, the iOS mail app, and Outlook Mobile. Whenever possible I move the message while leaving it unread, so as not to make Clutter think I’m interested.

The upshot: it works reasonably well, but it seems to have trouble learning about messages from some sources. For example, both Strava and Twitter alerts remain…

View original 329 more words

Posted in Uncategorized | Leave a comment

DMARC Workaround for @yahoo & @aol sending to DL with external recipients

Back in April Yahoo changed their DMARC policy to reject, AOL followed suit a few weeks later. This effectively broke, causing NDRs for many external recipients, mailing list\DLs that contained external recipients and that also allowed external recipients, from @aol or @yahoo, to send email to it.  When a user at one of these domains sends an e-mail to the DL any external recipient on many different email providers (yahoo, aol, gmail, msn, hotmail, comcast, and more) would not receive the message and an NDR would be generated for these recipients. For more details on the issue see:

After trying several other things I’ve come up with the partial workaround below. The easiest work around is to enable moderation on the DL and then when an aol or users sends e-mail to the DL you manually resend it for them, from your mailbox or DL if permissions are setup to allow this. But in this case the email will come from your mailbox or group, requires manual intervention, and delays mail until someone approves or re-sends the e-mail send to the DL.

One comment, on the original post, suggested changing the mailing address to goto a mailbox then setup an mailbox rule to Forward all messages to the DL. While this does work, it also introduces the issue that the all messages comes from this ‘relay’ mailbox. So when users reply it goes to the mailbox, which then sends out the email to the DL. Therefore, user generated spam starts to occur when a thread gets a lot of traffic. Everyone that replies, using Reply or Reply All, generates an email to all recipients.

So the workaround below partially solves this issue, but only for e-mail sent from non-yahoo or aol users.

  1. Create a new mailbox that will Forward\Relay all messages to the DL
    • Name the mailbox so it looks similar to the DL name, like “External DL Users Relay”
    • This will get around the DMARC issue where it looks like Exchange is spoofing the sending domain of or, which causes the receiveing servers to reject the message.
    • You will probably want to set a short term retention policy on this mailbox, since all messages sent to it will be kept in the Inbox, in addition to being forwarded.
  2. Login to the mailbox, via OWA, and setup an Inbox Rule that forwards ALL messages to the DL that contains the users who should receive the message
    • By default the Forwarding action rule does not show up in OWA 2010/2013,  you have to click More Options… to show it.
  3. Create a transport rule to selectively redirect messages to the “relay” mailbox created in step 1
    1. Conditions
      1.  [when the message header contains specific rules]
        1. Message Header: Received
        2. Words: “” & “”
          • This should be two entries, without quotes, in the list
      2. [when the message header matches text patterns]
        1. Message Header: To
        2. Text patterns: <SMTP address of DL>
          • Enter the SMTP of the existing DL that you are trying to fix this issue for
    2. Actions
      1. [redirect the message to addresses] : <Select the mailbox created in step #1>
      2. Optional: [prepend message subject with string] : “RELAYED: ”
        • This is to help the uses realize the message has been relayed to work around the NDR issue.
      3. Optional: [append disclaimer text and fallback to action if unable to apply.]
        • What you put here is up to you, but I changed it to ‘prepend’, so this warning goes at the top of the message, and used this:
          This message was forwarded from a or sender. If you reply, the reply will go to all members. Please change the TO on your reply to the person’s who sent the original e-mail, if you want to reply just to them.
          DMARC Rule

Once this setup, when any non-yahoo or aol users sends an email to the DL the message will goto all users as it normally would. When a yahoo or aol users sends an email the DL the Transport rule will redirect the message to the “Relay” mailbox. The Inbox Rule on this mailbox will then fire and forward the message to the DL.

But in the case of  yahoo or aol senders the users in the DL will receive the message from the Relay mailbox. So a Reply or Reply all will not goto the original sender directly but to everyone, via the “Relay” mailbox. Users will have a Mailtip that says “This message was AutoForwarded”, in addition to the prepended message, if you added one.

Example message received from a users:

Relayed Message

But if a user replies to this message it will still goto all users in the DL, via the “Relay” mailbox. So these steps below just limit the amount of “Reply to All” behavior.

Posted in Uncategorized | 2 Comments

The difference between supportability and patching


This came up at the MVP Summit and we, the MVPs, wanted to re-iterate the difference between supportability and patching commitments from Microsoft.

Originally posted on Paul's Down-Home Page:

I’m at the annual MVP Summit this week, and everything we hear and see is pretty much NDA (except for pictures of Flat Tony). However, we just had a really interesting discussion that I think is safe to abstract here.

A couple years ago I wrote a post about what it means to be supported or unsupported. What I wrote then still stands: when Microsoft says something is unsupported, there can be multiple reasons for that label, and you do whatever-it-is at your own risk.

Microsoft’s support policy for Exchange 2013 can be summed up as “N-1″: when they release a new cumulative update (CU) or service pack, that version and the previous version are considered to be supported. So, in the fullness of time, when we get Exchange 2013 CU7, then CU6 and CU7 will be the officially supported versions.

It’s very clear that there’s a lot…

View original 168 more words

Posted in Uncategorized | Leave a comment

Come join the Exchange 2013 information sharing Facebook Group!

This group,, was created over two years ago and has grown to over 4,000 members and over 1,000 post, a year ago it had just over 600 members! The focus of this group is to share information about Exchange 2013, with a bit of leeway given for Exchange 2010 and Office 365 related items.

So what does “information sharing” mean? This mainly includes people sharing blog posts they’ve created, or ones they have come across that they feel are worth sharing. It also includes some basic architecture and functionality questions and discussions. What it DOES NOT include is support or help on issues. Facebook is a poor platform for providing support, in addition on the Microsoft TechNet forums people, like my fellow MVPs get credit for answering questions. These credits help them keep their Microsoft MVP status. So for support type questions goto the Microsoft TechNet forums on Exchange. Therefore, support questions\posts in most cases are deleted, as are any off topic or posts with little to no value. We, the admins of this groups, work hard to keep out the spammers and keep the noise to a minimum. Since this group is very focused there are normally less than a few posts per day in this group.

As you will see the most common poster and fellow group admin (Exchange blogger, writer, etc) is Tony Redmond, who runs two different blogs. Many other Microsoft Exchange MVPs and non-MVPs post links to their articles here also. So if you are looking for some of the latest blog posts and topics on Exchange 2013 check out this Facebook group. If you are a content creators and want to share your Exchange 2013 related content come join the group and feel free to post to it!

Disclaimer: This is an unofficial Microsoft Exchange group. This group is managed by independent Exchange experts. It is NOT an official group by Microsoft and is managed by individuals in their personal time. It is not supported, managed, or moderated by Microsoft in any official capacity. For official support please use TechNet forums or contact Microsoft PSS (Open a tickets from the web).

In the near future we will be activating another Facebook group that will focus on Exchange vNext (version after 2013) and Office 365. Almost all info on vNext is currently under NDA, so nothing to share about it yet. Once this info starts to become public we will then make this other group visible and share it in the current group.

Posted in Exchange, Facebook | Tagged , | Leave a comment