In the updated version of our Screencast we address these requirements by: Configuring Split-Brain DNS or Pin-Point DNS zones, Modifying the Exchange 2010 internal URL, Requesting and installing a GoDaddy UCC that doesn’t use our Internal Server’s name.
In this step-by-step video, we demonstrate how to replace the default Single Domain, Exchange 2010 self-signed certificate (or an expired one) with a self-signed multiple domain (UCC) certificate. In step1 of the Screencast, we check the existing certificates on our Exchange 2010 CAS and generate a new self-signed, Exchange 2010 Multiple Domain certificate: Step 1…
In Part 1, we focus our attention on the required health checks and preparation of Active Directory and Exchange 2007 organization. You will see a typical Exchange 2010 SP2 installation on a member server running Windows Server 2008 R2 SP1
In the following Step-by-Step video tutorial, we demonstrate how to enable, configure and use Single Item recovery in Exchange 2010. As you will see, once the Purges and Versions subfolders come into play, we get the so called Immutability in Exchange 2010.
In this Screencast, we will show you how to renew an existing Exchange 2010 SSL certificate. We are using a GoDaddy Multiple Domain (UCC) certificate, but the instructions are exactly the same when renewing a single domain SSL certificate. Some people prefer the graphical user interface – Exchange Management Console, while other specialists favor the command line – Exchange Management Shell. We address both approaches in our Screencasts, when generating the CSR (Certificate Signing Request).
Setting Outlook Web App as the default page in Exchange 2010 CAS server makes life easier for end users. It saves them the effort to type the precise OWA address, and of course the error messages when they mistype it or forget to use secure socket layer (SSL) connection. In the following Step-by-Step video tutorial, we demonstrate how to configure OWA in Exchange 2010 CAS server as the default web page. The Exchange 2010 server is running on Windows Server 2008 R2, and we are dealing with IIS7.5.
a standard Exchange server is an attractive target. In case of a security breach it might allow an attacker access to mailboxes and Active Directory data. Here comes into play the Edge server as a lean, locked-down standalone version of Exchange server. The data, synchronized one way – from the internal AD into the local instance of AD LDS (Active Directory Lightweight Directory Service) is hashed, which makes it of little use to an attacker. In addition, the EDGE server is running a truncated version of Exchange Management tools. As you will see, the EMC (Exchange Management Console) is showing data just for the local Edge server and has quite a limited functionality. The same way EMS (Exchange Management Shell) supports a limited set of cmdlets.
In the following Step-by-Step video tutorial, we demonstrate the installation and initial synchronization of Exchange 2010 SP1 Edge Transport server on Windows 2008 R2 OS.
In the following Screencast, we discuss the different types of UPN and demonstrate their use on local and remote clients. We also demonstrate how to bulk modify the explicit UPN in Exchange Management shell to match the e-mail address of the accounts.