>> --> In this posting I'll cover the set up of Exchange 2007 SP1 on Windows Server 2008. I will lay out which variations of Exchange are supported on which OS version and also which domain controller edition they're able to use. I will detail the supported ways to maneuver from Exchange 2007 on Window Server 2003, to Exchange 2007 on Windows Server 2008 and last of all I'll cover the prerequisites essential, just before showing the real install.Note:
At this time, neither Windows Server 2008 nor Exchange Server 2007 SP1 have released to production. As I'm consequently working with beta code, sure elements of what follows (particularly the screenshots,
Windows 7 Starter, might possibly alter earlier than the last model.Introduction It's virtually a year immediately after the release of Exchange 2007 and many of us now have finish Exchange 2007 implementations. I guess which means we are on the lookout for a thing new to undertake! If this is the situation then you definately wont be disappointed, as incredibly soon we will be introduced with all the new problem of shifting our current Exchange 2007 methods onto Windows Server 2008. Table 1 lists the several supported situations for Exchange and OS variations.Exchange Version Server OS Supported for Installation Exchange 2003Windows 2000 Server SP4Windows Server 2003 (All SP levels and R2) Exchange 2007 RTMWindows Server 2003 SP1 + SP2 (inc R2) Exchange 2007 SP1Windows Server 2003 SP1 + SP2 (inc R2)Windows Server 2008 RTMTable one: Exchange/OS versions supported for installThe first thing to be aware is that Exchange 2007 RTM is not supported on Windows Server 2008. To install Exchange 2007 on Server 2008 you must run Exchange 2007 SP1. This service pack,
Office 2007 Professional Plus Key, as many of you may perhaps know, is a little different from previous service packs in that it is actually a complete set up of Exchange. Effectively SP1 is RTM using the SP1 code slipstreamed into it. Having established that Exchange 2007 SP1 is required to set up on Server 2008,
Windows 7 Home Premium Product Key, what other considerations are there?Probably the biggest consideration is Active Directory. Table 2 sets out the different Domain Controller variations supported by different versions of Exchange.Exchange Version Domain Controller OS Supported Exchange 2003Windows 2000 Server SP4Windows Server 2003 (All SP levels and R2) Windows Server 2008 RTMExchange 2007 RTMWindows Server 2003 SP1 + SP2 (inc R2)Windows Server 2008 RTMExchange 2007 SP1Windows Server 2003 SP1 + SP2 (inc R2)Windows Server 2008 RTMTable 2: The Exchange/Domain Controller support matrixOne new Active Directory feature of Windows Server 2008 which I havent mentioned is Read Only Domain Controllers (RODC) (and Global Catalog servers). These are servers which do not hold a writable copy of the AD as well as do not hold account passwords. They are most likely to be used in branch office scenarios to prevent security breaches either intentional or accidental. So how do these RODCs affect Exchange? Simply put, Exchange doesnt use them! When left to automatically associate with a domain controller (or global catalog server) Exchange will ignore the RODC or ROGC. The important thing for administrators to remember is not to manually set Exchange to work with a RODC as things simply will not work correctly.One other area that will likely be welcome to administrators is that with the release of Exchange 2007 SP1, the Exchange Management Console will as a final point be supported on Windows Vista, and for that matter on Server 2008 as well.Earlier than shifting on to how we upgrade, I think it truly is worth clarifying that Exchange 2007 SP1 will not set up on Windows Server 2008 Server Core. Server Core, for those who havent heard, is a cut down model of Windows Server 2008 which only presents a command line interface. It has been stripped down to run varied server roles including amongst others Domain Controller, DHCP, DNS, File and Print. However, because a lot of functionality has been stripped out to ensure a small footprint and less need for patching, important components such as the .Net Framework are not present to support Exchange.Notice:
As I mentioned we're currently doing work with beta code. It is because of this that the Unified Messaging role does not currently set up on Server 2008. This is going to be rectified ahead of release.The upgrade pathSo how do you actually get from Exchange 2007 running on Windows Server 2003 to Exchange 2007 SP1 running on Windows Server 2008?Unfortunately, although understandably given the massive architecture changes involved, you cannot simply upgrade Exchange 2007 to Exchange 2007 SP1 and then upgrade the OS to Windows Server 2008. This simply breaks Exchange completely!Even when you have a clustered mailbox server, you cannot perform a rolling upgrade by upgrading one node of the cluster failing over and then doing the other node. The only way is to perform a migration! In other words you must do a clean install of Windows Server 2008 on a new server and then migrate your data. Mailboxes can be moved using the Move-Mailbox cmdlet and public folder data must be replicated. This has caused a fair amount of discontent on varied online forums but it happens to be the only way,
Office Standard 2010!InstallationHaving looked at all the background, lets get started with the installation. The first thing to cover is preparing your Windows Server 2008 machine for Exchange 2007. There are a bunch of prerequisites which must be met as listed below:.Net Framework v2.0 or 3.0 PowerShell RTM MMC 3.0 (installed by default) IIS 7 (A range of components necessary by different roles) For a much more detailed look at the requirements for each Exchange server role see Exchange 2007 System Requirements.For now we are going to install an Exchange 2007 SP1 server in a new domain and new organisation. We will set up the CAS, HT and Mailbox roles. In order to set up the prerequisites we are going to run the following commands one once the other at a command prompt:ServerManagerCmd -i RSAT-ADDSServerManagerCmd -i PowerShellServerManagerCmd -i Web-ServerServerManagerCmd -i Web-ISAPI-ExtServerManagerCmd -i Web-MetabaseServerManagerCmd -i Web-Lgcy-Mgmt-ConsoleServerManagerCmd -i Web-Basic-AuthServerManagerCmd -i Web-Digest-AuthServerManagerCmd -i Web-Windows-AuthServerManagerCmd -i Web-Dyn-CompressionAfter the first command (RSAT-ADDS) you will need to reboot as shown in Figure one.
Figure 1: Installing Active Directory Management Tools and being prompted to rebootAfter the reboot, I used a simple batch file to run the other commands in sequence. Part of the output from the commands is shown in Figure 2.
Figure 2: Part of the output from the prerequisite installationFor more detailed information about the Windows Server 2008 roles/features required for the other Exchange 2007 roles (Edge Transport Server and Unified Messaging Server) see How to Install Exchange 2007 SP1 Prerequisites on Windows Server 2008.Having successfully completed the installation of prerequisites, it can be time to set up Exchange. Start setup and click Install Microsoft Exchange Server 2007 SP1 as shown in Figure 3.
Figure 3: Starting Setup of Exchange Server 2007 SP1Next run through the usual setup steps as shown in Figures 4 11.
Figure 4: The SP1 Setup introduction screen
Figure 5: Accepting the license agreement
Figure 6: Opting into the Microsoft Error Reporting scheme
Figure 7: Selecting a typical set up which installs CAS, HT, Mailbox roles and the management tools
Figure 8: Setting the brand new Exchange Organisation name
Figure 9: Opting not to create public folders for legacy clients
Figure 10: Exchange Readiness checks in progress
Figure 11: The not for production use warning before install about using a 32 bit edition of Exchange 2007Having completed the steps in Figures 3-11 installation begins. However, it will be at this point that an error occurs as shown in Figure 12. It would appear that for whatever reason, the registry key HKLMSOFTWAREMicrosoftWindowsWindows Error ReportingConsent does not exist!
Figure 12: The registry key doesnt exist error messageNote:
It is highly unlikely that this problem will still exist once the products ship.To rectify this problem locate the relevant area in the registry and create the required key as shown in Figure 13.
Figure 13: The newly created registry keyHaving resolved the problem with all the registry key you are left with no other option than to exit setup. On doing this you is going to be prompted to reboot,
Microsoft Office 2007, which you should do. When the server is backed up, restart setup which will start in Exchange Maintenance Mode as shown in Figure 14.
Figure 14: Exchange setup restarting in Maintenance ModeAt this point, step through the remaining setup screens as shown in Figures 15-17.
Figure 15: Selecting the relevant roles for installation
Figure 16: Again making the choice not to create public folders for legacy clients
Figure 17: Setup completed!Once setup completes you will have a functioning Exchange 2007 SP1 install on Windows Server 2008 as shown in Figure 18.
Figure 18: Exchange 2007 SP1 installed on Windows Server 2008Before completing this article I thought it might be interesting to show the registry key that we created earlier. As can be seen in Figure 19, it happens to be now populated with various values.
Figure 19: The values in the registry key created to solve the installation errorSummary As you can see from the steps above, the install process to put Exchange 2007 on Windows Server 2008 is basically extremely simple. At this time there is definitely the odd glitch but there is no doubt these are going to be ironed out just before Release to Production. I feel the only thing that has the potential to cause a delay in deployment are the usual worries about deploying a brand new OS and the fact that if you already have Exchange 2007 on Server 2003 you will have to perform a migration which requires extra hardware.
Office Standard 2010 Installing Exchange 2007 on W
Threaded Mode