Some Notes on the Machines

At least initially, one must:

1. Load up adsiedit.msc,
2. Find a user object,
3. Get its properties,
4. Click on anything in the list,
5. Press P on the keyboard,
6. Scroll to proxyAddresses and edit it,
7. Set the primary address as SMTP:email@domain.com (note the caps in the prefix),
8. Set all alias(es) as smtp:email2@domain.com (note the lowercase prefix!).

In some environments, a new tab appears in ADUC which means you don’t have to go back to ADSI Edit, but this is not always the case.

This command does it for everything Sent after 9/22/2016 and before 9/27/2016. You’ll then have to export it from the temporary_storage_mailbox, and import it into original_mailbox.

This is all one command line in Exchange PowerShell, set as multiple lines for easy reading. The SearchQuery is especially arcane; there is a lot of incorrect syntax out there for it, the below worked today (2016-09-27) on Exchange 2010 fully updated.

Search-Mailbox -Identity original_mailbox@domain.com 
-TargetMailbox temporary_storage_mailbox@domain.com 
-TargetFolder "Rescued_From_Dumpster" 
-SearchQuery {Sent:>22-Sep-2016 AND Sent:<27-Sep-2016}
-SearchDumpsterOnly

Here are instructions for adding the domain admin you are using, to the appropriate Exchange roles:

https://technet.microsoft.com/en-us/library/dd638143

And the role changes you need, are listed here:

http://notes.ponderworthy.com/copy-an-exchange-online-mailbox-to-another-in-powershell

This is otherwise entitled “How to install Exchange 2010 service packs and roll-ups without risk of bootlooping the server”, by Mike Hunsinger.

The method below has worked perfectly on several servers and has not caused a recovery situation. That said, assure there’s good backups and perform these procedures word-for-word as these Exchange updates have been known to bootloop and bluescreen servers, particularly SBS servers when not cleanly installed.

You will need this web page or one of a few like it, to determine the current patch level of the Exchange in front of you.

The key is to determine the current Exchange SP level, then based on the current version, plan your updates like this: First, install the highest-level rollup for the current SP. Then install the next SP by version. Followed by that SP’s highest-level rollup, then the next SP.

Here’s an example:

Your 2010 Exchange Server is using SP1 RU 3 (Roll-Up3). You intend to upgrade this system to SP3 RU14 (Latest version of Exchange).

Here’s the order in which you should install the updates based on this exchanges current version:

1. Update Rollup 8 for Exchange Server 2010 SP1 (Highest version of SP1)
2. Exchange Server 2010 SP2
3. Update Rollup 8 for Exchange Server 2010 SP2 (Highest version of SP2)
4. Exchange Server 2010 SP3
5. Update Rollup 14 for Exchange Server 2010 SP3 (Highest version of SP3)

Notes we’ve found are important:

• Assure the server’s OS itself is running the latest service pack for Windows Server.

• Exchange SP’s must be downloaded from the web and installed using an exe. Roll-Ups must only be installed via Windows Update.

• Using this pattern of installs and installing Roll-Ups using only Windows Update, will prevent having to perform the lengthy staging process where the mailbox databases are manually converted between versions using CMD.

• Completely review the prerequisites for each Rollup and SP before installing it. There are corroborative softwares such as .net and sql client or certain hotfixes that may need to be installed prior to a given service pack or roll-up.

• During the Service Pack updates, you will see a long checklist the server is moving down while performing the upgrades. If the server errors on one of the checklist items and asks if you wish to continue or roll-back. ROLL IT BACK. Resolve the issue noted and try the update again. You want all 10 lights green when it hits the bottom of the checklist. Errors here are usually the result of insufficient permissions someplace in the server. The errors are usually easy to trace down online.

• Between every update listed. Launch the ECM. Assure the mailboxes are all listed. Then run the builtin Exchange testing. If Exchange says it’s passed, move onto the next update. If Exchange fails any factors, they must be eliminated before continuing.

• Allow up to 1 hour for the server to reboot following an Exchange SP Upgrade. It’s advisable that ILO be activated prior to installing the upgrades described in this document, so you can keep an eye on the server while it reboots.

Here’s a great resource:

http://blog.powershell.no/2010/09/20/managing-calendar-permissions-in-exchange-server-2010/

Lots of options available for control in PowerShell, both per-user and across the enterprise:

http://o365info.com/manage-clutter-by-using-powershell-office-365/

One uses help/about to get a Build Number, and then one looks up the build number on this page:

http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-build-numbers.aspx

If Android won’t send to on-prem Exchange, try setting the LAN-local domain as the default domain in Organization Configuration, Hub Transport, Accepted Domains.

We now have the Office 365 Support and Recovery Assistant for client software support, and also the Microsoft Office 365 Client Performance Analyzer Office 365 Client Performance Analyzer for network performance issues.

Here is a way:

https://technet.microsoft.com/en-us/library/bb124754