Rob Whaley

How to cleanup the Recoverable Items in the cloud and On-Premises

Rob Whaley [MSFT] — Fri, 12 Jan 2018 14:16:00 GMT

We have recently published two articles to help cleanup recoverable items when a mailbox is placed on In-Place Hold or Litigation Hold or has single item recovery enabled, you'll want to preserve the mailbox data until the hold is removed or single item recovery is disabled. In this case, you need to perform more detailed steps to clean up the Recoverable Items folder.

The detailed steps are located here:

Office 365: Delete items in the Recoverable Items folder of cloud-based mailboxes on hold - Admin Help

On-Premises: Clean up or delete items from the Recoverable Items folder

PAW your way into Office 365 Migrations

Rob Whaley [MSFT] — Fri, 01 Dec 2017 21:37:25 GMT

Hi Readers!
I just posted a new blog on the Exchange Team Blog titled “PAW your way into Office 365 Migrations” Go check it out if you want to learn about Protocol Agnostic Workflow aka PAW and how it will enhance the experience of migrating your data to Office 365.

Source: PAW your way into Office 365 Migrations – You Had Me At EHLO…

Exchange Server 2016 Online Training Courses Now Available! | You Had Me At EHLO…

Rob Whaley [MSFT] — Tue, 03 May 2016 17:58:51 GMT

Exchange Server 2016 Online Training Courses Now Available! | You Had Me At EHLO….

Exchange Management Shell and Mailbox Anchoring

Rob Whaley [MSFT] — Tue, 15 Dec 2015 05:00:42 GMT

Coming to the next CUs for Exchange 2013 and Exchange 2016 there are some changes to how the Exchange Management Shell (EMS) connects to Exchange. In previous versions, we have seen that customers who were reliant on a load balanced solutions for third party apps and scripts may get routed to a non-Exchange 2016 server. This would lead customers to some broken administrative experiences based on the reliance of Exchange 2016 cmdlets and features. Today we will dive deeper into these changes to help the Exchange Administrator understand how these changes will affect their Exchange Organization. Check out the full article at The Exchange Team Blog

Gather MRM Data from Office 365 and / or On-Premises

Rob Whaley [MSFT] — Thu, 29 Oct 2015 20:44:51 GMT

I have created a script will gather the MRM configuration for a given user. It will collect the current MRM Policy and Tags for the Exchange Administrators to be able to troubleshoot MRM issues. If you have MRM woes and need to collect data this script will do it for you.

Office 365: Messages not deleting from my On-line Archive

Rob Whaley [MSFT] — Wed, 18 Mar 2015 21:12:00 GMT

If you have an Exchange On-line Archive tied to a On-Premises Mailbox you may notice that your MRM Polices are not firing like they should. Typically this is due to the fact that you have no imported your MRM Policies and Tags to Office 365 from your On-Premises environment. The way MRM works at a basic level is that each message gets stamped with the appropriate tags that are viewable with MFCMAPI (PR_POLICY_TAG, PR_ARCHIVE_TAG). The Managed Folder Assistant (MFA) is what is responsible for this process. So what happens is when MFA On-Premises runs and moves the messages to the archive mailbox to the Office 365. Now that the message lives in Office 365 it is up to the MFA running in Office 365 to manage the message. If the tag on the message does not reflect a tag that is present in Office 365 the MFA will ignore the message. To make sure that this step in TechNet: Export and import retention tags. Remember you will use Exchange Management Shell to export that MRM Polices and Tags and to import the MRM Polices and Tags to Office 365 you will need Remote PowerShell. Export retention tags from an on-premises Exchange organization

Run this Exchange Management Shell command to change directory to the Scripts subdirectory in your Exchange installation path.
```
Cd "\Scripts"
```
Run the Export-RetentionTags.ps1 script to export retention tags to an XML file.Important: If you're importing or exporting retention tags and retention policies to Exchange Online, you must connect your Windows PowerShell session to Exchange Online. For details, see Connect to Exchange Online using remote PowerShell.
```
Export-RetentionTags.ps1 "c:\docs\ExportedRetentionTags.xml"
```

Import retention tags to an Exchange organization

Run this Shell command to change the directory to the Scripts subdirectory in your Exchange installation path
```
Cd "\Scripts"
```
Run the Import-RetentionTags.ps1 script to import retention tags from a previously exported XML file.Important: If you're importing or exporting retention tags and retention policies to Exchange Online, you must connect your Windows PowerShell session to Exchange Online. For details, see Connect to Exchange Online using remote PowerShell. Note: When running this script against Exchange Online, you may be prompted to confirm that you want to run software from an untrusted publisher. Verify that the name of the publisher appears as CN=Microsoft Corporation, OU=MOPR, O=Microsoft Corporation, L=Redmond, S=Washington, C=US, and then click R to allow the script to be run once or A to always run.
```
Import-RetentionTags.ps1 "c:\docs\ExportedRetentionTags.xml"
```

OWA – “The window couldn’t be opened because your computer is low on memory.”

Rob Whaley [MSFT] — Tue, 07 Oct 2014 06:09:44 GMT

I was on my server and everything seemed fine. Performance was great however I kept getting the error following error every time I went to modify a database or show command logging: “The window couldn’t be opened because your computer is low on memory. Please close some windows and try again.” I was able to go to another machine and all was well so I started searching on this and apparently ieproxy.dll was not registered. I ran the below and it resolved my issue. 1. Open a CMD window 2. Navigate to C:\Program Files\Internet Explorer 3. Run the following command line: regsvr32 ieproxy.dll

Certificate Error installing Exchange 2013 CAS Role

Rob Whaley [MSFT] — Sun, 10 Aug 2014 19:39:45 GMT

Symptom ===================================================================== When installing Exchange 2013 from PowerShell in my lab I ran into an issue and the server failed installing the Client Access Role.

Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup Copying Files... File copy complete. Setup will now collect additional information needed for installation. Languages Management tools Mailbox role: Transport service Mailbox role: Client Access service Mailbox role: Unified Messaging service Mailbox role: Mailbox service Client Access role: Front End Transport service Client Access role: Client Access Front End service Performing Microsoft Exchange Server Prerequisite Check Configuring Prerequisites COMPLETED Prerequisite Analysis COMPLETED Configuring Microsoft Exchange Server Preparing Setup COMPLETED Stopping Services COMPLETED Copying Exchange Files COMPLETED Language Files COMPLETED Restoring Services COMPLETED Language Configuration COMPLETED Exchange Management Tools COMPLETED Mailbox role: Transport service COMPLETED Mailbox role: Client Access service FAILEDThe following error was generated when "$error.Clear(); Install-ExchangeCertificate –WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true) { Install-AuthCertificate -DomainController $RoleDomainController } " was run: "Could not grant Network Service access to the certificate with thumbprint 1C5101B4BE0AF6CBD6A39FD413436E2649B0124 because a cryptographic exception was thrown.".The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the :ExchangeSetupLogs folder. Cd "\Scripts"

Since I was already in PowerShell I went ahead and added the Exchange Snap-In since the Exchange Management Tools were installed and checked for the thumbprint listed above

Windows PowerShell Copyright (C) 2015 Microsoft Corporation. All rights reserved. [PS] C:\PowerShell> Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 [PS] C:\PowerShell> Get-ExchangeCertificateThumbprint Services Subject ---------- -------- ------- 0123456789ABCDEF0123456789ABCDEF01234567 ....S.. CN=ex02 ABCDEF0123456789ABCDEF01234567ABCDEF0123 ....S.. CN=Microsoft Exchange Server Auth Certificate F0123456789ABCDEF0123456789ABCDEF0123456 ....... CN=WMSvc-EX02

As we can see it's not listed so I decided to look at all the certificates loaded on the server. I then opened up MMC and added certificates for the local computer and see 4 certificates, however Exchange is only seeing 3. I am not sure where the certificate for the FQDN came from since the labs was just built today (8-10-14). The other three were supposed to be there after an Exchange Server install. Workaround ===================================================================== I backed up the certificate and removed it and then re-ran the installation and it resolved the issue. Cause ===================================================================== Unknown at this time. I have been able to reproduce the issue but I do not know why the certificate is there (possible lab image issue). Time to try to debug the issue.

Disable Remote PowerShell in Office 365

Rob Whaley [MSFT] — Fri, 11 Jul 2014 07:00:00 GMT

Sometimes there arises a scenario where you may want to disable remote PowerShell access for your users in Office 365. The main reason for doing so would be to prevent rogue admins, users, or even compromised user accounts from being able to do anything malicious with your tenant. By default, all users will have remote PowerShell access to your Office 365 Organization. Now RBAC Policies prevent them from doing a whole lot (if they are non-administrative users). However if an account gets compromised there could be issues. The cmdlet below turns off remote PowerShell for a particular user. You can use this to disable PowerShell for all user’s but remember to do not include the Administrators account or you will not be able to run the Hybrid Configuration Wizard or do any management to the Office 365 Tenant that would require you to use PowerShell and make for a very bad day.

Set-User -Identity -RemotePowerShellEnabled:$False

Office 365 for business public roadmap

Rob Whaley [MSFT] — Thu, 19 Jun 2014 05:17:48 GMT

The Office 365 for business roadmap lists updates that are currently planned for applicable subscribers. Updates are at various stages from being in development to rolling-out to customers to being generally available for applicable customers world-wide. Expand an update to learn more about it and click the learn more link to read more details. To view the Office 365 roadmap click here. Learn more about Office 365 for business service updates here.