Exchange Server 2019 offers a way to configure a global or server-side email signature. Although it is more often referred to as “disclaimer” feature, it is often used to configure automatic HTML signatures. Why is this better than email signatures set up by users? By applying organization-wide email signatures on Exchange Server 2019, you can make sure that email correspondence is unified, branding is always in place and that nobody automatically adds inspirational quotes to every email sent. This method also has some drawbacks, but I show how to fix those limitations at the end of the article.
Whenever an employee leaves a company, admins need to follow a certain procedure. In Office 365, depending on the company’s best practices, you need to disable user’s ability to sign in, or simply delete a user entirely. Those are some standard activities you could probably perform while sleeping. The tricky part is that you might need to preserve the former employees’ mailbox contents without the need to pay for the former employee’s license in Office 365. Below, I present a few different ways to achieve just that.
Recreating an Outlook profile is a quick fix in many situations. In the video below I show how to recreate Outlook profiles for a single user and for an entire company. But first, what is an Outlook profile?
Outlook profile contains all the information about your Outlook configuration. You might be using Outlook for years without knowing of the profile existence, but it is how Outlook knows how to connect to your mailbox. The best part of Outlook profiles is that resetting them is an easy and quick method of fixing some common problems with the email client. The video tutorial below shows the easiest method to create a new Outlook profile.
There are three options to choose from to add different signatures to user mailbox and shared mailbox emails. The first method is to create two separate signatures in Outlook, the second requires mail flow rules on the server side and the third involves the use of CodeTwo Email Signatures for Office 365.
On the Internet, you can find tons of guides, which explain how to migrate from an IMAP server to Office 365. Most of them cover the topic from the native perspective, so to contrast this, I am going to show you how to perform IMAP migration to Office 365 by using a third party tool – CodeTwo Office 365 Migration.
Windows Event logs is one of the first tools an admin uses to analyze problems and to see where does an issue come from. But it is not the only way you can use logged events. In this article, I will show you how to use PowerShell and Get-EventLog to perform some Event Log magic. But first, a few words about the logs in general.
Office 356 is where most organizations head for today. “Most” as there are still companies that prefer or need to stay on-premises whatever the reason is. If you have already moved to Office 365 and want to get back to the on-premises environment keep reading to see what your options are.
Data migration isn’t one of those tasks faced by the companies on a daily basis. And the full migration of email data will probably take place no often than once every couple of years. However, there is a high chance that sooner or later you will begin to look around for a way to migrate your mailboxes. And when the time comes, many questions will arise: Should you migrate to a new Exchange on-prem or Office 365? What types of data should be migrated? Can you migrate only selected data? And most of all: how to migrate your email data?
In this article, I’ll try to answer some of these questions. And I’ll also toss around some of the pros and cons of taking advantage of third-party companies offering Exchange migration services vs. using a migration tool by yourself or by your IT team.
The General Data Protection Regulation (GDPR) introduces many changes in the way companies handle data. And although the regulations are the same for every company, the way each organization handles their data security is hardly similar. In this article, I will show you how you can get closer to a complete GDPR compliance by blocking possible data leaks in your Exchange Server.
Emails are one of the most potent channels for data leaks – sometimes, an honest mistake can cause an email with personal data to leave an organization and end up in an unauthorized mailbox. Such a data breach is unacceptable and a disclaimer asking to “delete the email if it is not intended for this email address” is not enough under the regulations introduced by GDPR. Thankfully, you can ensure a much higher data security level of your Exchange Server, using CodeTwo Exchange Rules Pro.