Wednesday, October 3, 2007

Installing Exchange 2007 SP1: Notes from the field


NOTE: These upgrade notes are for Exchange SP1 Beta 2. Many readers have found this useful in their RTM upgrades. Also please see my latest post that discusses the installation of SP1 RTM. - Jeff

The following are my notes for installing Exchange Server 2007 Service Pack 1 Beta 2. As with most beta software, upgrades may not go as smoothly as they will in the final product. I came across some problems and solutions, which I'll share with you and will hopefully make your upgrade smoother.

I'm not going into a lot of detail on each of these steps, so if you want more info please post your question and I'll do my best to answer.

My setup is a single x64 dual-core host with 4GB RAM. It functions as my Microsoft Exchange 2007 Edge server and runs VMware Workstation 6.01. It runs two VMs, one Windows Server 2003 SP2 x64 Domain Controller and one Exchange 2007 x64 Hub Transport, CAS, Mailbox server running E2K7 Update 4. The Edge server is running Microsoft Forefront Security for Exchange RTM.

The Exchange 2007 SP1 release notes say to update your Edge, Hub Transport and CAS servers before your mailbox servers. It also says that Forefront Security for Exchange RTM is incompatible with Exchange 2007 SP1. You have to use Microsoft Forefront Security
for Exchange Server with Service Pack 1 Beta 2 (FSES SP1 Beta 2). You can download it here.

Note: I was told by Microsoft, "Exchange SP1 Beta 2 requires FSES SP1 Beta 2 (installed before you install the Exchange Service Pack 1 Beta 2)."

So, without further ado, here are my upgrade notes:



BEFORE BEGINNING
  • Took snapshots of DC and EX01 VMs

  • Make a backup of host/Edge server


EDGE SERVER

  • Install ForeFront SP1 Beta 2

  • Follow http://support.microsoft.com/?kbid=929080 to disable ForeFront before installing Exchange 2007 SP1

  • Restart and stop all Exchange services, except ADAM

  • Install. Be patient. Configuring common transport polices took 10 minutes by itself.

  • Install completed successfully

  • Re-enabled Forefront as per KB929080, above

  • Restarted the server, checked event logs, tested email inbound/outbound successfully


HUB TRANSPORT/CAS/MAILBOX SERVER

  • Begin installation

  • Installation failed about halfway through

  • Tried to run again, but got the error, "This installation is forbidden by system policy." Solved using the Local Security Settings tip from Tim Chad at the bottom of this page

  • Restarted installation, but got the error, "The Exchange files are not installed, but the backup settings registry key is present. Only build to build upgrade mode is available."

  • Ran Setup.com /mode:upgrade from the command line to perform an unattended upgrade setup

  • Got the following output:

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be upgraded
Hub Transport Role
Client Access Role
Mailbox Role

Performing Microsoft Exchange Server Prerequisite Check

Hub Transport Role Checks ......................... FAILED
Setup cannot continue with upgrade because 'C:\Program Files\Microsoft\Exchange Server\bin\ExchHelp.chm' is open. Close the file and restart setup.

Client Access Role Checks ......................... FAILED
Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed.

The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the required component, then restart the Setup process.

Setup cannot continue with upgrade because 'C:\Program Files\Microsoft\Exchange Server\bin\ExchHelp.chm' is open. Close the file and restart setup.

Mailbox Role Checks ......................... FAILED
Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed.

The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the required component, then restart the Setup process.

Setup cannot continue with upgrade because 'C:\Program
Files\Microsoft\Exchange Server\bin\ExchHelp.chm' is open. Close the file and restart setup.

The Exchange Server setup operation did not complete.
Visit http://support.microsoft.com and enter the Error ID to find more
information.

Exchange Server setup encountered an error.

  • Set the World Wide Web Publishing Service, IIS Admin Service, and HTTP SSL service to automatic and started (they were disabled)

  • Copy file ExchHelp.chm from \setup\serverroles\common of the setup media into the \Program Files\Microsoft\Exchange Server\Bin directory

  • Re-run Setup.com /mode:upgrade

  • Success! Restart all servers. Test OWA and Outlook inbound/outbound successfully


Good luck with your own upgrade. Now to test the new SP1 features!

Labels: , , , ,


Subscribe to my feed   StumbleUpon Toolbar

Subscribe to The EXPTA {blog} by Email

9 Comments:

At November 29, 2007 6:11 PM , Anonymous Anonymous said...

great post. I had additional exchange services that had been disabled in addition to the 3 services you listed, but you put me on the track to get the RTM SP1 working. Thanks!

 
At November 30, 2007 6:35 AM , Blogger Jeff said...

Glad you found this useful! I created a new post listing my installation notes for Exchange 2007 SP1 RTM. Take a look at http://www.expta.com/2007/11/installation-notes-for-exchange-2007.html

 
At December 1, 2007 6:07 PM , Anonymous Romosapien said...

Awesome post Jeff, saved my hide. :-) However, it really sucks that this was not fixed before making SP1 RTM.

 
At December 5, 2007 6:36 PM , Anonymous billykaka said...

Thanks a lot for posting this information, you saved me from a very painful night

 
At December 11, 2007 2:46 AM , Anonymous Simon said...

Nice post. You may not have seen this, but I'll put it out there. After a trouble upgrade of Powershell, I have managed to get my SP1 update block down to:

Error:
You must be a member of the Exchange Organization Administrators group to upgrade the first Mailbox server role to Exchange Server 2007 Service Pack 1.

My Powershell does not currently interface with Exchange because of the removal/install, but AD shows 'Administrator' (the account being used for the upgrade) as a member of this group.

Thoughts? =p

 
At December 11, 2007 8:00 AM , Blogger Jeff said...

Simon, sounds like you're saying you upgraded PowerShell (to the PowerShell 2.0 CTP?). This is not a requirement for SP1, nor do I think is supported.

Try uninstalling the current version of PowerShell and reinstalling version 1.0 from here and try SP1 again.

If that still doesn't work, you may have to reinstall Exchange 2007 RTM using the /recoverserver switch (get a good backup first). Run Setup.com /M:RecoverServer from the command line. This will pull the Exchange config from AD and reinstall the bits on your server.

Henrik Walther has an
excellent article on using the /recoverserver switch. I recommend you read this thoroughly before beginning.

 
At February 9, 2008 11:31 AM , Anonymous Anonymous said...

Jeff, you are LEGEND for posting this. It just (literally, just...it's installing as i type) saved by hide too! whoooooooo!!

I haven't found this info anywhere else (without spending hours looking)
The Setup.com /mode:upgrade got me back on track.

You da maaannnnn!

Altaf (London, UK)

 
At September 5, 2008 8:04 PM , Anonymous Anonymous said...

Jeff,
I just wanted to clarify, you are actually running Exchange 2007 sp1 on VMWare workstation 6.01?? If so, I've really been wanting to try this. We just recently deployed Exchange 2007 sp1 in new company. Guess whose the administrator? Yours truly! Last time I worked on Exchange - it was 5.5. Just need a box that I can play around with without touching my production box. Any advice is greatly appreciated.

Fred Jumayao
fjumayao@yahoo.com

 
At September 6, 2008 7:54 AM , Blogger Jeff said...

Yes, Exchange 2007 will run on VMware Workstation 6.x in a lab environment.

If your host hardware is x64, you can load up either XP x32 or x64 on the host and VMware will run x64 Windows 2003 or 2008 guests.

If the host is x32 only, you can run the x32 (lab) version of Exchange 2007 so you can test it out.

Good luck!

 

Post a Comment

Thank you for posting a comment! It is my hope that you find the information here useful. Let me know (and others) if this post helped you out or if you have a comment or further information.

Links to this post:

Create a Link

<< Home