Posts

No Calendar delegation but still receiving invites

Ever experienced the fact that a user is still receiving calendar invites from a calendar where the user doesn’t have any permission to it anymore? At a customer I had an issue where user A was a delegate member of user B, and user A was set to receive copies of calendar related messages. That was all fine until user A didn’t want to be related anymore to the calendar of user B, at any possible way. Not hard to accomplish I was thinking. But after removing the delegated rights the frustration started.

User A was still getting copies of calendar related messages from user B. After a double check with PowerShell I noticed that user A still had view permissions on the calendar of user B. But after removing the view permission, the problem wasn’t resolved. I was thinking that Exchange was confused and if I added the delegated rights again to remove it right away, Exchange would correct it self. But no…

All the actions above I’ve executed by clicking in the GUI as well as configuring it in PowerShell. But it didn’t make a difference. I’ve also checked if user B had any inbox rules that was explaining this behavior, but sadly not.

A colleague of mine tipped me the name off an application (MFCMAPI) that can look deeper than the GUI and PowerShell for any “stranded” rule in the information store. This was a life saver because after using this, user A never received copies of calendar related messages from user B ever again. See below a step by step guide of how to use MFCMAPI:

First download MFCMAPI as it isn’t a default Windows application!


After starting MFCMAPI, navigate to “Session” and click on logon. Login with credentials of user B or administrator credentials that has full mailbox access to the mailbox of user B.


After logging in, navigate to “QuickStart” and click on “Inbox Rules”.


Search for a rule where the “PR_RULE_PROVIDER” is “Schedule + EMS Interface” and delete it.

 

After this let user B clear the delegate list and restart outlook before user B is filling the delegate list with members again. Except user A of course!
You can also login to OWA and do it by yourself with the administrator credentials with full access rights on the mailbox of user B.

I hope this is a life saver as it was for me. Cheers!

Exchange 2013 and the logging issue..

If you run a Microsoft Exchange 2013 environment you may have noticed that the disk space will fill up with logging data.

Microsoft told us that this is by design. But what if you don’t want to enable all this logging? It also cost you performance… right?
This is what I did to disable the logging and win some disk space and performance back.

Read more

Is an experienced IT specialist in the area of migration, implementation and re-design of and upgrading networks. Has in-depth knowledge of Microsoft Server, Terminal Services, Exchange, Citrix, DNS, Active Directory and VPN connections. Also has wide experience with the complete design of servers, including operating systems, middleware and applications. And of course, experience with managing databases such as MS SQL and designing virtual environments with VMware/ESX.

Core qualities
Ambitious, hands-on, enthusiastic, responsible, cheerful

Hobbies
Anything and everything to do with cars, hi-fi and aquaria

Job description
Senior Systems Engineer

Set homefolder permissions with PowerShell

imageToday one of my collegues asked me to write a script that performs two actions for all users of a certain Organizational Unit:

  1. Ensure that each user has modify permissions on their homefolder
  2. Make each user visible in the Exchange Address List.

Sounds like a PowerShell job right?

I reused my function to set NTFS Permissions by SID:

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

Exchange 2010: Loadbalancing Relay Connector

Exchange Logo

On an Exchange 2010 environment I needed to allow smtp relaying for specified hosts. The procedure for doing this is explained clearly in the Exchange 2010 documentation.

So I created a relay connector on all servers with the HT role and since we are using Virtual Loadbalancing appliances from LoadBalancer.org to loadbalance the HT and CAS roles I wanted the relay connectors to be loadbalanced as well.

So how do we configure this?

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

Exchange Move Mailbox Experiences Part 5

imageAnother interesting Move Mailbox error and in this case I am really unsure how this would be possible!

Let’s look at the Move Mailbox log:

1-10-2011 11:49:18 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.

  Top of Information Store
  John Doe
  
  archive.pst
  IPM.Document.PSTFile
  38621879
  01/19/2006 14:30:57
  01/19/2006 14:30:19
  Message (size 36.83 MB (38,621,879 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell.
Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)

This error occurs because of a size constraint just like the one in the previous part.

imageBut the strange part is that it seems to be a PST file (type IPM.Document.PSTFile) located in the Root folder of the Exchange mailbox (which is not possible AFAIK).

 

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

Exchange Move Mailbox Experiences Part 4

The previous part (part 3) addressed Mailbox Size but did you know that even Message Size (or rather Item size) can prevent a successful move as well?

Here’s an example move mailbox log:

2-10-2011 3:18:58 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.

  verzonden nov 2004-aug 2005
  Jane Doe
  
  Foto's afscheid John Doe 10 februari jl.
  IPM.Note
  76121694
  02/15/2005 15:28:06
  02/15/2005 15:28:06
  Message (size 72.6 MB (76,121,694 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell.
Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)
Diagnostic context:

As you can see in the log this mailbox there is one item with a size of 72 MegaBytes.

Let’s see this in Outlook:

image

It gets even worse when we open the Message:

image

It was addresses to several internal recipients and as you know Exchange 2010 no longer supports Single Instance Storage

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

Exchange Move Mailbox Experiences Part 3

In Part 2 I showed some details about Mailbox Rule corruptions that can disturb Mailbox Moves.

For this part the topic is Mailbox size, which can be an important factor in deciding which mailboxes you want to move first.

In my case the mailbox size was important because we agreed to move smaller mailboxes during the day but larger mailboxes only outside working hours.

For Exchange 2010 mailboxes it’s very easy to obtain the size using PowerShell.

Example:

Get-Mailbox "rweijnen" | Get-MailboxStatistics | select DisplayName, ItemCount, TotalItemSize
DisplayName ItemCount TotalItemSize
Remko Weijnen 313 34.87 MB (36,564,183 bytes

But how can we get the Mailbox Size for Exchange 2003 mailboxes?

 

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

The case of the mailbox validation error

Today I noticed a strange warning when opening a mailbox:

WARNING: The object domain.local/Productie/Users/SomeOU/LoaderA0001 has been corrupted, and it's in an inconsistent state. The following validation errors happened:
WARNING: Property expression "LoaderA0001" isn't valid. Valid values are: Strings that includes '@', where '@' cannot be the last character

 

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

Exchange Move Mailbox Experiences Part 2

In part 1 we saw that a corrupted rule made the Mailbox Move fail.

I wanted to know if I had really a corrupted mailbox or maybe even corruption in the store or another problem.

So in this part I will describe how to break down the Mailbox Move Log.

First go to the Failed Move Request and select Properties:

image

 

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.

Exchange Move Mailbox Experiences Part 1

Exchange Logo

I am currently working on a migration project from Exchange 2003 to Exchange 2010.

Most Exchange migration projects use Mailbox Moves to move the mailbox data to the new Exchange environment.

imageBut there are some things I observed during Mailbox Moves (from Exchange 2003 to 2010) that are worth mentioning.

Read more

Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.