I have just noticed an issue with Exchange 2010 based hybrid and AADSync. On-prem AD account has assigned on-prem mailbox as well as remote mailbox (Exchange Online – O365). Yes, it seems to be possible, but only technically, because mailbox functionality is broken from end-user point of view at this point.

According my investigation it was caused by wrong procedure by mailbox creation. SD created remote mailbox , ran AADSync, disabled remote mailbox, forgot to run AADSync and created on-prem mailbox immediately.

So what to do then? We have to ensure only one mailbox either in Exchange Online or Exchange On-prem so based on our needs.

I decided to keep on-prem mailbox, because it was used by affected end-user.

Well, I exported all mailbox data from remote mailbox to PST file. There are a few possibilities how to do it e.g. via Outlook or eDiscovery search. I wanted to expert all available mailbox data including dumpster so I preferred eDiscovery approach (be aware to have mailbox still enabled during that time).

Hi, I had to investigate issue at Citrix side without possibility to install troubleshooting tools like Fiddler or Wireshark and I had success to find NirSoft utilities so collection of small and freeware utilities in portable form, hm I would say really nice thing…

Experience with Exchange 2010 based hybrid and the following remote migration failure (move requests/test cmdlet):

Microsoft.Exchange.Migration.MigrationServerConnectionFailedException: The connection to the serve
r ‘mail.ficility.net’ could not be completed. —> Microsoft.Exchange.MailboxReplicationService.Remote
TransientException: The Mailbox Replication Service could not connect to the remote server because
the remote server encountered an internal error.

The remote server returned an error: (500) Internal Server Error.. –> The content type
text/html of the response message does not match the content type of the binding (application/soap
+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is
implemented properly.

Time to time I needed to check read I/O operations without a Data Collector Set, but I did not want to have the counter list/settings dependent on particular server (i.e. the server below hosts mailbox database MDB01 or MDB05 but not MDB02 and I want to have counters for all of them and I do not mind that some counter will not work).

Well, I saved the settings from the server into HTML file and modify its content for 18 databases.

Changing value: <PARAM NAME=”CounterCount” VALUE=”18″/>

Adding parameters for missing databases (be careful you have to always use unique PARAM NAME):After that I could check the latency by pasting the same counter list on any server.

You can use administrator audit logging in Microsoft Exchange Server to record actions taken by a user or administrator that make changes in your organization. By keeping a log of the changes, you can trace a change to the person who made it. You can also augment your change logs with detailed records of the change as it was implemented, use the records to comply with regulatory requirements and requests for discovery, and so on…. [source].

Yes, yes, the auditing is very useful. But I wanted to show you how could look a cmdlet statistic for a month: