Exchange Online: Looping through large numbers of objects, a PowerShell example

Sometimes it is necessary to run a command against a large number of objects.  The simplest way to do this is with a pipe like in this example where litigation hold is enabled for all users: get-mailbox -resultsize unlimited | set-mailbox -litigationholdenabled $true -litigationholdduration 3660   However, as you get into thousands or tens of…

0

External users cannot open encrypted messages

When an external user tries to view the contents of an encrypted message from your organization they see the following error message after trying to enter the one time passcode:  “Sorry, we can’t display your message right now Something went wrong and your encrypted message couldn’t be opened. Please try again by following the instructions…

0

Messaging Records Management & confusion with Litigation Hold

Many customers I speak with are confused by the terminology used with Messaging Records Management (MRM).  Often people assume that if you set a Retention Policy the item will be kept for the number of days specified.  For them this implies the items in question will also be protected for that period of time.  This…

0

Testing Impersonation Permission with EWS Editor

A question that comes up occasionally with support is whether Impersonation is broken within Exchange Online.  This article covers how to test impersonation using the November 2016 edition of EWSEditor. EWSEditor is available from http://ewseditor.codeplex.com.  Once it is downloaded and unzipped you can run ewseditor.exe.  If you don’t have the proper version of .Net installed…

0

Divide Discovery and In-Place hold searches into smaller units

This blog has been in the works for longer than I would like to admit :).  Since starting a few things have changed.  For example when this was first started in the fall the maximum number of mailboxes in a Discovery Search was 5000.  Today it is 10,000.  In time the limit will probably change…

1

How to run SDP on a computer that cannot connect to the Internet

In support we frequently ask that customers run the Support Diagnostics Platform so we can collect a wide range of basic data on a particular server or client.  The catch is that not all servers or clients are able to connect to the internet.  If the machine that is to run the tool cannot connect…

0

12800 Event solutions

12800 events indicate you are running out of memory.  For example: Event Type: Error Event Source: MSExchangeIS Event Category: Content Engine  Event ID: 12800 Date: 1/27/2012 Time: 9:47:14 AM User: N/A Computer: Contoso1 Description: Message processing failed because there is not enough available memory (8007000E-80000000).    There are three basic courses that troubleshooting can follow here:…

0

Dumping Cluster logs in response to an event

Recently I was working with a customer that experienced database moves in their DAG.  The “failovers” were always at odd hours when there were no admins available.  By the time the admins came in and tried to dump the cluster logs the data was gone.  (Basically the cluster logs are spread across three files.  Each of those…

0

OWAEnabled filter returns unexpected results

I recently had a customer that was running: get-casmailbox -filter {OWAEnabled -eq $false} In the output they saw numerous rows displayed where OWAEnabled was actually listed as $true.   They found that if they run the command below they get the correct result: get-casmailbox | where-object {$_.owaenabled -eq $false}   So why the difference?  The…

0

How high item counts can influence 623 events

In my earlier blog about 623 events I mentioned there are a great many possible causes.  Twice in the last 1.5 months I have seen a situation where high item counts were the major contributing factor for 623 events. In both cases the dumps were collected and they revealed that the store was busy working…

1