Migrate from Exchange 2010 to Exchange 2013

In this document we will be able to see all the requirements and steps that we must take to proceed with migrating a Microsoft Exchange environment 2010 to Exchange Server 2013. We must bear in mind that it is a long process and especially depending on the number of servers as well as mailboxes we have or their sizes, It will be a migration that will not require a service stop at any time.

Integrating Lync Server 2010 with OWA

In this document, we'll look at how to integrate instant messaging between Microsoft Lync Server 2010 and Microsoft Exchange Server 2010 SP1 allowing our users to connect from the outside without the Lync client, something that is missing when it previously existed in Office Communications Server, so that our users, once logged into OWA, will be able to use instant messaging from a browser anywhere securely and with any device,

Enabling archiving in Exchange 2010 SP1

One of the important features that Microsoft Exchange SP1 brings us 2010 is the possibility of managing the archiving of our users directly in Exchange and being able to store it remotely wherever we are interested, for example in an archive database located on a secondary disk drive (without good performance, no RAID protection…) in order to maintain user mailboxes in accordance with our requirements; This is interesting for specific users who need to have a high volume of stored mail.

Exporting and Importing Mailboxes or PST Files into Microsoft Exchange 2010 SP1

Prior to Exchange 2010 SP1 we used the Export-Mailbox command (Exchange 2007 and Exchange 2010) o Dive (Exchange 2003) to export our mailboxes to PST's files. Thanks to Exchange SP1 2010 we'll use 'New-MailboxExportRequest’ and it will therefore not be necessary to have any Outlook on premises. We will perform this procedure on an Exchange server 2010 SP1, We will have to indicate which user or group will be in charge of carrying out these imports or exports, so we will have to add the role of 'Mailbox Import Export'. Otherwise, by default members of the 'Organization Management'’ will have such roles.

Restoring an Exchange mailbox 2010 using a Recovery Database and Symantec Backup Exec 2010

I publish this document that my colleague Carlos Fuenteseca passes to me, A crack of an uncle: The storage restore groups that we could see in the old versions of Exchange 2003/2007 have disappeared with the appearance of the new version of Exchange Server 2010. In this document, we will see how to create a recovery database as well as perform a restore of an Exchange mailbox 2010 using Symantec Backup Exec 2010 and a couple of commands from the powerful Exchange server powershell 2010. As I will comment during the document, these restore options are similar with any backup software that supports Exchange Server 2010.

Configuring DAGs in Exchange 2010

One of the new features and advantages that Exchange offers us 2010 is the possibility of having a high availability system in a simple way, being easy to implement, at any time and above all the simplicity of administration. It is based on the implementation of DAG or Database Availability Group, by mounting a replica of the databases between the different Mailbox servers (or on the same computer if we have all the roles on the same server), so this replaces the old Exchange clusters 2007, SCR and CSF; and therefore now we will simply need two servers and not three or more as required in Exchange 2007!

Installing and configuring Microsoft Forefront Protection 2010 for Exchange Server

Microsoft Forefront Protection 2010 for Exchange Server (FPE) is the Edge Protection Server for a Microsoft Exchange organization 2010, where we can manage all the blocking of incoming mail in order to reject unwanted emails either by the condition we configure (Anti SPAM), since it provides us with 5 Anti-Antivirus Definition Engines from Different Manufacturers! We will also avoid anti-malware, We have the possibility of extensive configuration from a console that is easy to manage, We also have an information area that is also quite cool. And manageability with PowerShell, of course! This server must be the one that collects external mail and sends it to our organization, the ideal is to mount it on the server that is in the DMZ totally isolated from our organization and on the server with the Edge Transport function.

How to renew Exchange self-signed certificates 2010

In Exchange 2010 It is well known that in order to communicate securely, each Microsoft Exchange Server service uses a secure connection using certificates; these certificates ensure the IMAP connection (Internet Message Access Protocol), POP (Post Office Protocol), SMTP (Simple Mail Transfer Protocol), IIS (Internet Information Services) and UM (Unified Messaging). And we will take special care to keep them renewed or valid. On Exchange Server 2007 this renewal process was carried out with three commands in PowerShell and now they have implemented the possibility of doing it through a wizard!