exchange 2007 implementations

8/13/2019 Exchange 2007 Implementations

1/15

Introduction

It is nearly a year after the release of Exchange 2007 and many of us now have complete

Exchange 2007 implementations. I guess that means we are looking for something new todo! If this is the case then you wont e disappointed as very soon we will e presented

with the new challenge of moving our existing Exchange 2007 systems onto "indows#erver 200$.

%ale &liststhe various supported scenarios for Exchange and '# versions.

Exchange Version

Server OS Supported for Installation

Exchange 200(

"indows 2000 #erver #)*

"indows #erver 200( +,ll #) levels and -2

Exchange 2007 -%/ "indows #erver 200( #)& #)2 +inc -2

Exchange 2007 #)&

"indows #erver 200( #)& #)2 +inc -2

"indows #erver 200$ -%/

Table 1:Exchange1'# versions supported for install

%he first thing to note is that Exchange 2007 -%/ is not supported on "indows #erver

200$. %o install Exchange 2007 on #erver 200$ you must run Exchange 2007 #)&. %his

service pack as many of you may know is a little different from previous service packsin that it is a complete installation of Exchange. Effectively #)& is -%/ with the #)&

code slipstreamed into it. aving estalished that Exchange 2007 #)& is re3uired to

install on #erver 200$ what other considerations are there4

)roaly the iggest consideration is ,ctive 5irectory. Table 2sets out the different5omain 6ontroller versions supported y different versions of Exchange.

Exchange Version

Domain ontroller OS Supported

Exchange 200(

"indows 2000 #erver #)*

"indows #erver 200( +,ll #) levels and -2


Exchange 2007 -%/



2/15


Exchange 2007 #)&



Table 2: %he Exchange15omain 6ontroller support matrix

'ne new ,ctive 5irectory feature of "indows #erver 200$ which I havent mentioned is

-ead 'nly 5omain 6ontrollers +-'56 +and loal 6atalog servers. %hese are serverswhich do not hold a writale copy of the ,5 and also do not hold account passwords.

%hey are most likely to e used in ranch office scenarios to prevent security reaches

either intentional or accidental. #o how do these -'56s affect Exchange4 #imply putExchange doesnt use them! "hen left to automatically associate with a domain

controller +or gloal catalog server Exchange will ignore the -'56 or -'6. %he

important thing for administrators to rememer is not to manually set Exchange to workwith a -'56 as things simply will not work correctly.

'ne other area that will e welcome to administrators is that with the release of Exchange

2007 #)& the Exchange /anagement 6onsole will finally e supported on "indows

8ista and for that matter on #erver 200$ as well.

9efore moving on to how we upgrade I think it is worth clarifying that Exchange 2007#)& will not install on "indows #erver 200$ #erver 6ore. #erver 6ore for those who

havent heard is a cut down version of "indows #erver 200$ which only presents a

command line interface. It has een stripped down to run various server roles includingamongst others 5omain 6ontroller 56) 5:# ;ile and )rint. owever ecause a lot

of functionality has een stripped out to ensure a small footprint and less need for

patching important components such as the .:et ;ramework are not present to supportExchange.

!ote:

,s I mentioned we are currently working with eta code. It is ecause of this that the


3/15

Even when you have a clustered mailox server you cannot perform a rolling upgrade y

upgrading one node of the cluster failing over and then doing the other node.

%he only way is to perform a migration! In other words you must do a clean install of"indows #erver 200$ on a new server and then migrate your data. /ailoxes can e

moved using the /ove=/ailox cmdlet and pulic folder data must e replicated.

%his has caused a fair amount of discontent on various online forums ut it is the only

way!

Installation

aving looked at all the ackground lets get started with the installation. %he first thing

to cover is preparing your "indows #erver 200$ machine for Exchange 2007. %here are

a unch of prere3uisites which must e met as listed elow>

.:et ;ramework v2.0 or (.0 )ower#hell -%/

//6 (.0 +installed y default

II# 7 +8arious components needed y different roles

;or a much more detailed look at the re3uirements for each Exchange server role

see Exchange 2007 #ystem -e3uirements.

;or now we are going to install an Exchange 2007 #)& server in a new domain and new

organisation. "e will install the 6,# % and /ailox roles. In order to install the

prere3uisites we will run the following commands one after the other at a command

prompt>

ServerManagerCmd -i RSAT-ADDS

ServerManagerCmd -i PowerShell

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lg!-Mgmt-Console

ServerManagerCmd -i Web-"asi-A#th

ServerManagerCmd -i Web-Digest-A#th

ServerManagerCmd -i Web-Windows-A#th
http://technet.microsoft.com/en-us/library/aa996719.aspxhttp://technet.microsoft.com/en-us/library/aa996719.aspx


4/15

ServerManagerCmd -i Web-D!n-Com$ression

,fter the first command +-#,%=,55# you will need to reoot as shown in "igure 1#

"igure 1: Installing ,ctive 5irectory /anagement %ools and eing prompted to reoot

,fter the reoot I used a simple atch file to run the other commands in se3uence. )art

of the output from the commands is shown in "igure 2.


5/15

"igure 2: )art of the output from the prere3uisite installation

;or more detailed information aout the "indows #erver 200$ roles1features re3uired for

the other Exchange 2007 roles +Edge %ransport #erver and


6/15

aving successfully completed the installation of prere3uisites it is time to install

Exchange. #tart setup and click ?Install /icrosoft Exchange #erver 2007 #)&@ as shown

in "igure $#

"igure $:#tarting #etup of Exchange #erver 2007 #)&

:ext run through the usual setup steps as shown in "igures % & 11#


7/15

"igure %:%he #)& #etup introduction screen

"igure ':,ccepting the license agreement


8/15

"igure (:'pting into the /icrosoft Error -eporting scheme

"igure ):#electing a typical install which installs 6,# % /ailox roles and the

management tools


9/15

"igure *:#etting the new Exchange 'rganisation name

"igure +:'pting not to create pulic folders for legacy clients


10/15

"igure 1,:Exchange -eadiness checks in progress


11/15

"igure 11:%he not for production use warning efore install aout using a (2 it version

of Exchange 2007

aving completed the steps in "igures $-11 installation egins. owever it is at thispoint that an error occurs as shown in "igure 12# It would appear that for whatever

reason the registry key ?AB/C#';%",-EC/icrosoftC"indowsC"indows Error-eportingC6onsent@ does not exist!


12/15

"igure 12:%he registry key doesnt exist error message

!ote:

It is highly unlikely that this prolem will still exist once the products ship.

%o rectify this prolem locate the relevant area in the registry and create the re3uired keyas shown in "igure 1$#

"igure 1$:%he newly created registry key

aving resolved the prolem with the registry key you are left with no other option than

to exit setup. 'n doing this you will e prompted to reoot which you should do.


13/15

"hen the server is acked up restart setup which will start in Exchange /aintenance

/ode as shown in "igure 1%#

"igure 1%:Exchange setup restarting in /aintenance /ode

,t this point step through the remaining setup screens as shown in "igures 1'-1)#

"igure 1':#electing the relevant roles for installation


14/15

"igure 1(:,gain making the choice not to create pulic folders for legacy clients

"igure 1):#etup completed!


15/15

'nce setup completes you will have a working Exchange 2007 #)& install on "indows

#erver 200$ as shown in "igure 1*#

"igure 1*:Exchange 2007 #)& installed on "indows #erver 200$

9efore completing this article I thought it might e interesting to show the registry key

that we created earlier. ,s can e seen in "igure 1+ it is now populated with various

values.

"igure 1+:%he values in the registry key created to solve the installation error

exchange 2007 implementations

Documents