Yesterday I was prepping a little for an upcoming conference that a colleague (Ben Miller Cloud Security Dude) and I will be speaking at, I thought I’d share a very short article on how office 365 Advanced threat protection works. For now, I’ll just cover pretty basic stuff like attachments. I’ll go into more detail later and cover address re-writing and other topics.
So here is an email trace I just performed.
So a message comes in and I have ‘dynamic delivery’ set (I’ll cover this in more detail in another article), but basically means that exchange online will deliver the message immediately BUT the attachment will only become available AFTER it tests it in a ‘sandbox’. How does Microsoft do that? They spin up a virtual machine and run the attachment there and then detonate (Microsoft term) it or sends it on to meet up with the message after a series of other steps (e.g. address rewrite).
So the user receiving the email will get this when they first get an email and click on the attachment before testing is done.
The process only takes a few minutes.
Microsoft is in the process of rolling out a new migration experience that will greatly simplify your journey to Office 365 and Exchange Online.
This new experience will help any customer running at least one Exchange 2010, 2013 and/or 2016 server on-premises to migrate to the cloud seamlessly. When you initiate the migration, we evaluate what you have configured already in Exchange Online and we walk you through the Hybrid Configuration Wizard to evaluate the on-premises environment. Once all the information on your current state is collected, we ask a couple of questions about your desired state (things like how fast you want to move to Exchange Online and whether you require advanced features). The hybrid wizard then walks you through the configuration needed to migrate your users to Exchange Online.
Based on your current configuration and the options selected while running the hybrid wizard, you will be taken down one of the following paths. Continue reading “Express Hybrid Migration!”
We are happy to announce the availability of public folder migration from Exchange Server 2013/2016 on-premises to Exchange Online! Many of our customers asked us for this, and the full documentation is now here. To ensure that any version-specific instructions are addressed appropriately, we have two articles to point you to:
While all of the information is located in the documentation, the key requirements are:
- Exchange Server 2013 CU15 (or later), Exchange Server 2016 CU4 (or later)
- Exchange on-premises hybrid configured with Exchange Online
If you have any additional questions, let us know in comments below. Enjoy!
On April 11, 2017, Exchange Server 2007 will reach End of Life. If you haven’t already begun your migration from Exchange 2007 to Office 365 or Exchange 2016, you need to start planning now.
End of life means that Microsoft will no longer provide the following for Exchange 2007:
- Free or paid assisted support (including custom support agreements)
- Bug fixes for issues that are discovered and that may impact the stability and usability of the server
- Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches
- Time zone updates
Your installation of Exchange 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible.
To learn about your options for migrating from Exchange 2007 to Office 365 or a newer version of Exchange Server, check out Exchange 2007 End of Life Roadmap.
If you have other Office 2007 servers or clients, such as SharePoint Server 2007, PerformancePoint Server 2007, Office Communications Server, Project Server 2007, or Office 2007 client applications, check out Resources to help you upgrade from Office 2007 servers and clients for information about their end of life dates and upgrade options.
It is possible to export one or all messages from one specific or all queues on an Exchange Server. This post describes how to do it for Exchange 2010, but the process is quite similar on Exchange 2013.
To do the export of messages, you can use the Export-Message cmdlet, which is part of Exchange. If you want to resubmit the exported mails (now .eml files), then put them into the replay directory on another Exchange server.
Continue reading “How to Export Messages from a Mail Queue on Exchange”
The issue is well-known, but I never got around to share it myself and just recently saw it once again at a customer, who experienced the problem.
This blog post will cover how to install and the Exchange Rollup Update successfully without getting the “Ended prematurely” error.
Continue reading “Setup Wizard for Exchange Update Rollup ended prematurely”
Continue reading “Migrate From Gmail to Office 365”