Prevent Cryptolocker Ransomware

UPDATED!

Increasingly this subject have an extreme importance, especially in business and where the data is more sensitive.

 

For those who are unaware, this type of ransomware (after the user access any site and/or click on an executable file that is usually sent by email) encrypts all data that the user has access, including mapped drives. After this encryption the user is prompted to pay a certain amount (usually 500 euros/dollars) to have access to the decryption key. There is no solution! Only prevention.

 

In this Post I will show you nine ways of prevention!

Migrate Exchange 2007-2010 Public Folders to Exchange 2013

 

In this Post I wil show you how to migrate Public folders from an earlier Exchange to Exchange 2013 (The process is the same in Exchange 2007 and 2010). It will not work with Exchange 2003.

First of all, the requirements:

• The user that will do the migration must belong to Organization Management and Recipient Management groups (Active Directory);
• All the mailboxes must already be in Exchange 2013 (All Mailboxes migrated). I will not cover in this Post how to migrate Mailboxes;
• The Public Folders migration must be planned (because there is a downtime);
• Before the migration, do a Full Backup of the legacy Exchange Server and Public Folders.

 The Migration process:

1. Download the migration Scripts;
2. Prepare the Migration;
3. Generate the CSV files;
4. Create the Public Folders Mailboxes in Exchange 2013;
5. Start the Migration;
6. Lock the Public Folders to Finalize the migration (requires downtime);
7. Finalize the Migration;
8. Unlock and Test the Public Folders.

Side Notes:

• Can not exist Public Folders in Exchange 2013 before the migration;
• All DNS Records must "point" to Exchange 2013 (like webmail, autodiscover, etc.);
• For some reason, if there are any Mailbox in Exchange Legacy, the public folder will be pointing to the Exchange Legacy;
• If there are Public Folders already created in Exchange 2013, all Migrated Mailboxes will automatically be pointing to the Exchange 2013 Public Folder instead of Exchange Legacy.

 

Ok, now that we have all the requirements, let's start!