Spoofing has long been one of the biggest issues with email, and with the move to cloud services in the last few years it has become an ever hotter topic. Although a number of features designed to combat spoofing exist, many of which have been discussed on the blog, no perfect solution is available.
Preservation policies were introduced almost a year ago as part of the Compliance Center in Office 365 (which you might also know as the Protection center, or as Security & Compliance Center after the latest rebranding). In a nutshell, they allow you to preserve content across (almost) all Office 365 workloads. They also provide support for true immutability of the data, such that even the company administrators cannot override.
With the release of Exchange Server 2016 it’s time for on-premises customers to consider their upgrade options. Which means that it’s also a good time to review their Exchange storage strategy.
The best way to learn about Exchange Server is to get hands-on with the product. And the best way to get hands-on without risking a production environment is to build your own test lab.
The following blog post is a trimmed-down excerpt from the eBook "Exchange Server Troubleshooting Companion":
One of the primary talking points of my Storage Configuration Options for Exchange session at IT Dev Connections was around JBOD with Exchange, and what that definition means to various people.
A career-defining moment for many IT professionals is the day that their customer requests some data to be restored from backup, and the backup is found to be not working. Or even worse, the backup doesn’t even exist.
It’s not a situation you ever want to find yourself in, and to help you to avoid it I’m going to tell you about the common (but easily remedied) mistakes that can lead to such an unfortunate position.
The following blog post is a trimmed-down excerpt from the eBook "Exchange Server Troubleshooting Companion":
Mailbox corruption is not a new problem for Exchange Administrators, Support Engineers, and Consultants. Causes of corruption can vary and include:
Exchange Server 2016 has arrived and has been lauded as one of the most reliable releases of Exchange yet. In many ways, it’s an evolution of the core technologies built into Exchange Server 2010 – but the way it’s put together has been revolutionized, making deployment choices much more straightforward.
Over the past two weeks, Microsoft has made a range of announcements around updates and new releases of Office, Office 365 and Exchange. The fact that Microsoft announces updates is hardly surprising. By now you should be used to the never-ending cascade of new features that are constantly dropped onto the market. A good way to keep track of what’s to come is the Office 365 Roadmap website.
Earlier this week, Tony Redmond wrote about Jeffrey Snover – also known as the godfather of PowerShell – being promoted to Technical Fellow at Microsoft; one of the highest achievable ranks.
Given that Jeffrey is considered to be the founding father of PowerShell, that does not really come as a surprise, as PowerShell has changed the way we work and interact with systems. And this does not only apply to large-scale environments or cloud solutions like Office 365.