Category: Uncategorized

Installing Exchange Server 2010 Beta1-part2

This is the second part of the Installing exchange 2010 article. If you have missed first part,I suggest you to read Exchange 2010 pre-requests and system requirements post. In this post I suppose to describe how to install exchange 2010 on the windows 2008 server.

Exchange 2010 setup process added some improvements to install exchange in different languages. You will see bunch of language folders in exchange 2010 source file folder. When we run setup.exe the setup will identify the current language of the operating system and display initial screen and introduction page by current language. In the second step we have to select download language file or use English as a default language.

Please bear in mind once the operating system has been install, you must be install all pre-requisites as mentioned in previous post. After that good to run Microsoft update for any additional update that might be needed. Then restart the server before install exchange 2010.

After setting up everything properly we should able to install exchange 2010.i am not going to guide how to prepare active directory in here. For more information regarding that please refer Prepare Active Directory and Domains TechNet article. Ok I think everything is clear. Let’s back to work.

Now we are ready to install Exchange 2010, you can use either GUI or command line to install. In this article I’ll use the GUI.

I lunch the Setup.exe in the extracted folder. Now you can see Exchange 2010 splash screen.

clip_image002

You can see exchange 2010 Splash screen is very similar to Exchange 2007 one and it’s detect required pre-requisites and those are grayed. So we can proceed to next step.

Click Install Microsoft Exchange link on the Splash screen. Then you will see copying setup files.

clip_image004

After completed the file processing step, Setup appears introduction page.

clip_image006

Click next, then you see language selection page

clip_image008

Currently I don’t have any additional language pack, so I’ll continue English as a Default language pack. Then you see language pack confirmation screen. Click next and continue.

Then license agreement page appears

clip_image010

Accept it and click next. After that error reporting page appears. Select as your choose and click next.

Then Exchange installation type page appears

clip_image012

Click custom and next. Then custom role selection page appears

clip_image014

If you see carefully custom exchange server installation, you will see there is no Clustered mail box server component. Because exchanges 2010 have new feature called incremental Deployment. you can configure high availability option after install exchange 2010.also there is a another feature called Database High availability Group(DAG).if you use DAS it’s created failover clustering for you, no need to create windows failover clustering manually. It makes configuring High availability easy.

Select Mailbox server role, Client access server role, Hub transport server roles. Management tools will select automatically.

Then Exchange organization page appears. Give organization name as a Demolab.

clip_image016

Then client settings page appears

clip_image018

If your organizations have client’s outlook 2003 or earlier versions you must select yes. Because Outlook 2003 and earlier version use public folders to access system data such as Free/Busy. Outlook 2007 and later versions use CAS server to access system data.

Then Exchange Customer Experience Improvement Program appears and joins as your wish.

Then readiness check page appears.

clip_image020

All readiness checks must be successfully passed as below.

clip_image021

AT this point setup is ready for exchange 2010 installation. So I click on the Install button. Then installation screen appears.

clip_image023

After installation Uncheck the Finalize installation using the Exchange Management Console checkbox, and click Finish completing setup. Then reboot the server.

  

Now Exchange 2010 installation has completed.

Windows 7 Release documents available to download

    This document provides very important information for you prior to deploying windows 7 in your infrastructure. This release document including known issues that might you need in the deployment.

    This document will update continuously, so you must check this document updates periodically.

      »There are two documents for windows 7«

  •     Release Note-Important Issues in Windows 7
  •     Things to Know About Windows 7

Resources

Release Documents for Windows 7

Installing Exchange Server 2010 Beta1 -part1

In this post I am going to cover first part of how to install exchange 2010 beta1.This series contain two parts of Exchange 2010 pre-requests and system requirements and Installing exchange 2010 step by step.

Important: Exchange 2010 Beta1 is running on beta period, so please take notice don’t install on production environment.

Some points you should keep in mind, When you going to build test lab.

  • Exchange 2010 supports only X64, (you will never see 32bit version ever.)
  • Exchange 2010 never supports on Windows 2003 and run only on Windows 2008, However it supports Windows 2003 domain controllers.
  • Exchange 2010 management tools can be install on Windows vista x64, Windows 2008 X64.Windows 7 doesn’t release yet and it will supports most probably.
  • Make sure your Global catalog servers and domain controllers are up to date (Windows 2003 SP2 and Windows 2008 SP2).
  • Exchange 2010 beta1 doesn’t support Windows 2008 R2 later builds except build 7000.That might be change Exchange 2010 RTM.
  • For security reasons and performance issues, doesn’t recommend installing exchange 2010 on domain controllers.

Exchange 2010 System Requirements

-Network and Directory servers-

Schema master The latest 32-bit or 64-bit Windows 2003 standard or Enterprise edition or 32-bit or 64-bit Windows 2008 Standard or Enterprise edition OS.
Global catalog server In every active directory site where you suppose to install Exchange 2010 you must place at least one global catalog server and that server must be either 32-bit or 64-bit of Windows 2003 standard or Enterprise or 32-bit or 64-bit Windows 2008 Enterprise or standard edition Os.
Domain Controllers All domain controllers where you deploy exchange 2001 must be at least Windows 2003 Sp2 and Forest functional level must be a windows 2003 functional level

-Hardware-

Hardware requirements are depends on server roles supposed to be installed on those servers.

Component  Requirement

 

Processor Intel processor that support Intel 64 architecture

(formerly known as Intel EM64T)

Memory
server role Minimum per server Maximum per server Recommended
Edge Transport 2GB 16GB 2GB minimum

8GB maximum

Hub Transport 2GB 16GB 2GB minimum

8GB maximum

Client Access 2GB 16GB 8GB minimum
Unified Messaging 4GB 8GB 2GB minimum

8GB maximum

Mailbox 2GB 64GB 2GB for server

2-4MB/mailbox

Disk space – 1.2 GB free disk space on Exchange 2010 installation partition

– Additional 500Mb free space for unified messaging pack.

– 200MB free disk space on system drive

– A hard drive where place message queue and HUB role or

edge server at lease 500MB disk space

Drive DVD-ROM drive, local or network accessible
File format NTFS

-Operating System-

Component Requirement
Operating system for server roles(HUB ,Edge, CAS, mailbox, Unified messaging) Operating system for Management tools
Operating system for Management tools Windows vista SP2 or later

-Exchange 2010 Prerequisites-

Prerequisite CAS HUB MBX UM EDGE Management

Tools

.NET Framework 3.5

X

X

X

X

X

X

Win RM 2.0 (CTP3).

X

X

X

X

X

X

Windows PowerShell V2 CTP3.

X

X

X

X

X

X

MMC Update (KB951725)

X

X

X

X

X

X

ASP.NET AJAX 1.0.

X

X

X

X

   
2007 Office System Converter: Microsoft Filter Pack.    

X

     

This table shows you what features should be installed for each role. Use below cmdlets on powershell in windows server 2008.

Command 

CAS 

HUB 

MBX

UM

EDGE

Mgmt

Tools

ServerManagerCmd -i Web-Server

X

X

X

X

 

 
ServerManagerCmd -i Web-ISAPI-Ext

X

 

 

 

 

 
ServerManagerCmd -i Web-Metabase

X

X

X

X

 

X

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

X

X

X

X

 

X

ServerManagerCmd -i Web-Basic-Auth

X

X

X

X

 

 
ServerManagerCmd -i Web-Digest-Auth

X

 

 

 

   
ServerManagerCmd -i Web-Windows-Auth

X

X

X

X

   
ServerManagerCmd -i Web-Dyn-Compression

X

 

 

 

 

 
ServerManagerCmd -i NET-HTTP-Activation

X

         
ServerManagerCmd -I RPC-over-HTTP-proxy

X

         
ServerManagerCmd -i ADLDS        

X

 
ServerManagerCmd -i RSAT-ADDS

X

X

X

     
ServerManagerCmd -i Failover-Clustering*            
ServerManagerCmd -i Desktop-Experience  

X

 

Note: Mgmt Toole=Management tools

*You have to install failover clustering if those mailbox servers belong to cluster.

Those requirements are most important for successful Exchange 2010 installation and preserve all servers with latest hot fixes and Services packs as well.

Note:-If you are deploying new exchange 2010 organization, and you are preparing active directory and schema using windows 2008 OS based computer, You must first install Active directory management tools on that computer, Use below command in PowerShell.

ServerManagerCmd -i RSAT-ADDS

Related informations

Exchange 2010 Prerequisites

Exchange 2010 System Requirements

Download Microsoft Exchange Server 2010 Beta

Exchange 2007 SP1 update rollup 9 has been released

Microsoft Exchange product team has been release update rollup 9(KB 970162) for exchange 2007 SP1.the release of the rollup via Microsoft update will -happen on July 28.According to Microsoft team blog majority of changes in this rollup are bug fixes.I would like to present some of those fixes.

 

KB 969911 –This bug is affect customers who is using Messaging Record    Management feature and have specified storage limit for managed folder.after move mailbox,the property which marks the folder as a managed is not preserved.

KB 968621 – Information store stop responding during online maintenance or when schedule backup is canceled.

KB 945877 – Performance improvements to esutil when it vitrifies the checksum of transactions logs.

– Supports for Windows 2008 R2 domain controllers.However that doesn’t mean it supports install exchange 2007 on Windows 2008 R2 Os.

KB 968715 – This bug is mostly effects for clients who have deployed CAS-CAS proxying.

 

KB 970162-have more details about this release

 

More Information

Update Rollup 9 for Exchange Server 2007 Service Pack 1 has been released

Description of Update Rollup 9 for Microsoft Exchange Server 2007 Service Pack 1

Navigation