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).
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.
Those of us who need to upgrade or migrate our previous ISA environments to the new Microsoft product, called Forefront TMG we will need to perform a migration by import/export configuration, since Forefront TMG only works under 64bit systems or Windows 2008 SP2 or R2 and we will not be able to upgrade it from an earlier version of ISA Server, be ISA 2004 or ISA 2006 (since they run on x86). We will also have to manually export the certificates along with their private key to the TMG, since this process simply migrates the configuration.
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.
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).
If we need to install a server without a CD/DVD drive, we can install it using a pen drive or an external USB drive, it is a very simple process but it is usually necessary when we find equipment that comes without CD-ROM or DVD-ROM. In this document you can see the very simple process that will work both for Windows 2008 R2 How to Windows 7.
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.
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.
This article shows a task that we will have to perform in our Microsoft Exchange organization 2007, as the services offered by Exchange use certificates to ensure connectivity, whether internal or external communication. In principle, once we have installed Exchange Server 2007, The certificates you generate for each service will last us a year, so before they expire we will have to renew them, We will detect this with events in the Event Viewer, or directly due to a drop in said service.
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!
Do Tailor-made training
Windows Server – VMware vSphere – Citrix Virtual Apps & Desktops – Centreon
|
We are a consulting firm that cares and pampers
|
 |
|
With quality and added value
|
 |
|
¡Let's work together!
|
 |
