Installing SQL Server 2008 in Windows cluster 2008 R2

In this document, we'll look at installing a SQL Server cluster 2008 under two Windows Server nodes 2008 R2, we will install both nodes to obtain a SQL Server service in high availability. First of all, you have your Windows cluster 2008 R2 mounted and well configured, to which we will have several disks available for the databases, Logs, backup and MSTDC (We can rely on to create the cluster: HTTP://www.bujarra.com/?p=2290).

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.

Configuring Debian+Apache as an OWA Reverse Proxy in DMZ

If we have an Exchange installation and we want to publish OWA abroad, we should never open the ports directly to our Exchange, for this there are proxies located in the DMZ that will present us with our OWA. In this case we are going to set up a Reverse Proxy with DEBIAN and APACHE. To do this, we start from the fact that we have a debian installed in our DMZ with the port 443 of the WAN pointing at it and allowing the port to pass through 443 from our server to the LAN's Exchange CAS.

Setting up Outlook Anywhere in Microsoft Exchange 2010

In this post we will see how to enable in Microsoft Exchange Server 2010, Outlook Anywhere (formerly called RPC over HTTPS), in order to connect from the outside with our Outlook via HTTPS, an ideal setup for those with mobile devices who use Outlook, we will make a secure connection via SSL to our server or Client Access array, with this we will avoid making VPN connections to open the Outlook. If we do not want to publish our CAS servers directly to the Internet, we will set up a TMG server to make the transfer to us.

Installing and configuring Microsoft Forefront TMG for secure OWA access

In this document, we'll look at one of the most common installations when deploying a Microsoft Exchange Server installation 2010 e ensure your connectivity from the outside through OWA access (or the necessary services) via a TMG host on the DMZ network. We will perform the installation of Microsoft Forefront TMG (Threat Management Gateway) An old ISA Server on a DMZ computer that will only be connected via HTTPS from the Internet, and the server will only connect to the Exchange server with the HUB role (or CAS array).

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.

Deleting the All Rooms Address Book (All Rooms) in Exchange 2010

During Exchange installation 2010, Some default address books are created, one of them is the so-called “All Rooms” (All Rooms in case you have it in English). It's possible, that when you reorganize your address lists you delete this notebook because you are not going to use it and at this moment is when from the OWA we stop being able to see the address lists with the following error:

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!