Tuesday, November 24, 2009

Exchange Server 2010: Database Availability Group

By Raphael Barini

Now that Exchange 2010 has been officially released, I wanted to start with what I believe is one of the best features added to Exchange 2010. There may be some people who will miss a few features of Exchange 2007 that were removed; however, DAG is a feature that many administrators have been requesting for years. In order to keep the focus on DAG, let’s take a look and recap through Exchange.

Exchange 2007 was launched with some great features, and introduced the LCR, CCR, SCC and SCR.
If you would like more information on the High Availability features in Exchange 2007, check out this great article written by Exchange MVP Andy Grogan, in our ESE Volume 1, Issue 4.

LCR (Local Continuous Replication), this was mainly used in small businesses who wanted to have a local copy of their Exchange database replicated to another disk on the same server:



SCC (Single Copy Cluster) this one is that I call a traditional Exchange cluster, in which you use a shared storage to host the Exchange database.




CCR (Cluster Continuous Replication) was used to replicate Exchange database between two Exchange servers, allowing for hardware and storage redundancy, but it has one limitation—just 1 active and 1 passive node.

SCR (Standby Continuous Replication) was introduced in Exchange 2007 SP1 to provide the ability to replicate Exchange databases to a disaster recovery location.





How we did in the past?

The concept of a DAG and how it functions is easier learned by someone who hasn’t worked with Exchange clusters previously because it is simple and easy to use in comparison to any other earlier version of Exchange.

In Exchange 2007, an Exchange server was installed as either an Active or Passive cluster node at the time setup.exe was run. Depending on which version of Exchange you installed, you had to create an Exchange virtual server (EVS) which was changed to cluster mailbox server (CMS) in Exchange 2007.

When a user connected to Outlook, the mailbox server name was a clustered resource which moved between any number of nodes on the Exchange cluster. This allowed for no end user configuration changes; instead, all the resources moved between physical servers.

An Exchange database was associated with the clustered resource and when you opened EMC/ESM the only Exchange server name that was shown was the clustered node (let’s call is CMSORG1.) That means database one would always belong to CMSORG1 even when this moved between physical machines.

Without further ado, here comes the DAG…

Now it’s time to forget everything that I mentioned previously about Exchange clustering.

What has been removed?
1) No more EVS/CMS
2) Database is no longer associated to a Server but is an Org Level resource
3) There is no longer a requirement to choose Cluster or Non Cluster at installation.
(An Exchange 2010 server can move in and out of a DAG as needed)
4) The limitation of only hosting the mailbox role on a clustered Exchange server
5) Storage groups have been removed as well from Exchange
What still have the same requirements?
1) Windows and Exchange Enterprise Edition is still required since DAG still uses pieces of Windows Failover Clustering
What is new in Exchange 2010 DAG?
1) Other roles can be installed on the mailbox server when it is a member of a DAG
2) A database name must be unique in the Exchange Organization



DAG can also be extended in multiple Active Directory Sites:


Let’s walk through the installation of Exchange 2010 and then setup DAG. To view the video, please click the link below, then click the full screen icon in the bottom right hand corner:
http://www.enowconsulting.com/video/

I hope you enjoy DAG as much as I do, and many thanks to Microsoft and the Exchange Team for this great new feature.

posted by Enow Inc. at 1:33 PM 0 Comments

Tuesday, November 10, 2009

Installation of Exchange Server 2010 Tutorial

By Ismail Mohammed, Exchange MVP

Since Exchange Server 2010 has been released, I am sure many administrators are eager to get their hands dirty in their Exchange Server 2010 labs. In this article, I will share the prerequisites and guidelines you must meet to ensure a successful Exchange 2010 installation in your lab.

Installation of Exchange 2010 uses the same method as Exchange 2007: the only significant change is the technology support version which needs to be suited for Exchange 2010.
Whenever we are thinking of Exchange 2010/Exchange 2007 installation, there are two major places which we need to focus on-- first one is Active Directory Preparation and the second one is Local Server Preparation.
Active Directory Preparation for Exchange 2010:
· Schema Master : Windows Server 2003 either standard or enterprise edition, recommendation have “windows server 2003 with SP 2,” which can be either 32-bit or 64-bit.
· Global Catalog Master : Windows Server 2003 either standard or enterprise edition, recommendation have “windows server 2003 with SP 2” which can be either 32-bit or 64-bit.
· The Active Directory domain & forest functional level must be Windows Server 2003-native or higher for all domains in the Active Directory forest where you will install Exchange 2010.
· Upgrade Schema - /prepare schema
· Exchange Security Groups & Permission : /PrepareAD
· LegacyExchange Support : /PrepareLegacyExchangePermissions

Existing Exchange 2003 in the Domain:

If you have Exchange 2003 in the organization then ensure that:
· Exchange 2003 has Service Pack 2 Installed
· It should be in the native mode.
Note: Exchange 2010 Beta Upgrade – If you want to upgrade from Exchange 2007, you can’t go with in-place upgrade, and one more thing there is no direct transition from Exchange 2007 to Exchange 2010 Beta . You need to create separate AD Site for Exchange 2010. Exchange 2007 co-existence transition will be supported after the release of Exchange 2007 sp2.

Server-level Specification:
Hardware:
· Processor : Intel 64-bit Processor\ AMD64 Processor (Production)
· Processor supported for 32-bit : Intel Pentium or compatible 800-megahertz (MHz) or faster 32-bit processor
Memory : Depends upon the actual requirement minimum 2 GB plus 2\3.5\4 MB per mailbox and can support up to 64 GB. For more information click here
Mailbox server memory recommendations:
Light = 2 GB plus 2 MB per mailbox
Average = 2 GB plus 3.5 MB per mailbox
Heavy = 2 GB plus 4 MB per mailbox
Source: Microsoft
· Disk Space : 1.2 GB free for the drive where we are installing the Exchange, 500 MB more space if we are installing UM, 200 MB free on the system drive and 500 MB free space for Transport Server role
· Drive : DVD-Rom or Network Access
· Software:Operating System : Windows Server 2008 Standard or Enterprise with SP2 or R2 Edition or just to install the console Vista with latest SP is supported.
· Other Software Requirement : there is other software required and actually it depends upon which roles you are installing and based on that you can select the required one.
My requirement is very simple: a clean installation of Exchange 2010 on windows server 2008 where I will install all the Exchange Server roles except Edge Transport Server Role.
Active Directory Preparation:

· Raising the Domain Function level & Forest Functional Level to Windows Server 2003: Log into to the windows server 2003 domain controller => Administrative Tools => Active Directory Domain and Trusts => Right click the domain name and select “Raise Domain Functional Level” and raise it to “Windows Server 2003”



· Forest Functional Level : Right click “Active Directory Domain and Trusts and select “Raise Forest Functional Level” as Windows Server 2003Server – Level Configuration :

1) Install IIS 7.0 : Inorder to do this, open Server Manager Console => Roles => Add Roles and select “Web Server (IIS)”


Figure2:



Under Role Services Windows select the following component:
· Basic Authentication
· Windows Authentication
· Digest Authentication
· Dynamic Content Compression
· .net extensisbility


Figure 3:


2) Remote Server Administration Tools pack : It is a feature included with Windows Server 2008. You can install the Remote Server Administration Tools pack by using either the Add Features Wizard in Windows Server 2008, or by using a command line to install the feature.Command prompt : ServerManagerCmd -i RSAT-ADDSFrom GUI:
· Open the Server Manager Console
· Click on Features and then Add Features and select Remote Server Administration Tools
· It will ask you to install IIS6 Management Compatibiltiy also select “Add Required Role Service and then click on NEXT


Figure 4:




3) Install HTTP Activation:
· Open the server manager console
· Features => Add Features
· Expand .Net Framework 3.0 Features
· Expand WCF activation and Select “HTTP Activation”

Figure 5:




4) For Unified Messaging Role we need to have "Windows Media Audio Voice Codec" and "windows Media Encoder" this can be installed by installing Desktop-Experience Component via server manager
· Open the server manager console
· Features => Add Features
· Select Desktop Experience




Figure 6:




OR else you can excute the installation of Server Manager Role and Features from the command prompt by running below command:

For Client Access Server Role:

ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth

ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i NET-HTTP-Activation
ServerManagerCmd -I RPC-over-HTTP-proxy

For Hub Transport Server Role:
ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

For Mailbox Server Role:

ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Author

ServerManagerCmd -i Failover-Clustering (for Clustering)

For Unified Messaging Server Role:

ServerManagerCmd -i RSAT-ADDS

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-AuthServerManagerCmd -i Desktop-Experience

For Edge Transport Server Role:

ServerManagerCmd -i ADLDS


5) Install .netframework 3.5 Sp1

6) Install Powershell V2

7) Install Windows Remote Management

8) Install Windows6.0-KB950888

9) Install Windows6.0-KB951725

10) Install 2007 Office System Converter :

11) Run Exchange 2010 setup

Figure 7:



Click on Step 4: Install Microsoft Exchange

12) Next Screen will be Introduction page, click on NEXT

Figure 8:



13) Now you will get "Language File Location" in which you can download the other languages apart from English and size of the pacakge will be 200 MB. By default I had chosen the "english"

Figure 9:



14) Next Screen will be "Language Pack Confirmation" - Click on Next

Figure 10:


15) EULA - Select "I Agree" and Click on Next

16) Error Reporting : It is upto you how you to set the option and click on NEXT

17) Installation Type : Select either Typical or Customize Option based on the required role to be installed. I have selected customized options

Figure 11:










Note : The path of the Exchange Database "C:\Program Files\Microsoft\Exchange Server\V14"

18) Server Role Selection: Depends upon your requirement, I had selected Mailbox, Client Access, Hub Transport & Unified Messaging

Figure 12:


19) Organization : If you have not ran /PrepareAd and you are running the setup from GUI it will ask you to provide Organization Name

Figure 13:









20) Cusotmer Experience Improvement Program : You can select either "Join" or "I don't Want to Join"

21) Readiness Check: In this step, Exchange 2010 will check will the required pre-requisite has been met or not like you have required schema master server, global catalog server, domain controller, schema is updated or not, domain functional level setting, all the software has been installed on this specific server or not. In other words it will do a readiness check on the Active Directory requirement part and Server Level Requirement Part.

Figure 14:



22) Click on Install as per the above figure: It will install Exchange Server Roles and then take a reboot of the server.

Figure 15:








Let's take a look at the Exchange 2010 Options under program files:



If you see the above screen, there are two powershell commands:


i) Exchange Management Shell & ii) Exchange Management Shell (Local Powershell), Console View: Some of the new changes (marked one) -


This is just a glance view:


You can see that database is in the organization level, under recipient configuration we have "mailbox migration."

There is a lot more to come on the way...

Reference:Microsoft Exchange Server 2010 (Beta)

Labels:

posted by Enow Inc. at 7:30 PM 1 Comments

 
 

 


 

 

 

Click below for the ESE
.:ENOW Solutions Engine Pages

Featured Authors
E-Now Andy Grogan
E-Now Jay Gundotra
E-Now Lasse Pettersson
E-Now Hans Willi Kremer
E-Now Norber Klenner
E-Now Raphael Barini
E-Now Jonas Borelius
E-Now Kevin Wilson
E-Now Ismail Mohammed
E-Now Mahmoud Magdy

Previous Posts
Browse Monthly Archives

Suggest a Topic
Hire Us

Subscribe to
Posts [Atom]