A. As I mentioned in a previous FAQ, you need to ensure that you upgrade your front-end Exchange 2003 servers before the back-end servers because an Exchange 2003 Outlook Web Access (OWA) implementation can't access an Exchange 2007 mailbox server. Once the front-end servers are replaced with Exchange 2007, you can replace the mailbox servers. Below, I walk through the process of adding Exchange 2007 into a simple Exchange 2003 environment. You need to ensure that your Exchange organization is set to native mode (i.e., no Exchange 5.5 servers). Also before starting the installation, ensure that IIS is installed:
1. Start the Control Panel Add or Remove Programs applet.
2. Click Add/Remove Windows Components.
3. In the Components list, select the Application Server check box.
4. Click Details.
5. Select Internet Information Services (IIS), then click Details.
6. Select Internet Information Services Manager and World Wide Web Service (for Mailbox Server and Client Access Server roles). Exchange 2007 no longer requires the IIS SMTP and NNTP services to be installed because it has its own built in SMTP server. Plus, MAPI is used for messages transported among Exchange 2007 servers within the organization.
7. Click Next.
8. Click Finish when IIS is installed.
A .NET update is also required. See the Microsoft Web page "Microsoft .NET Framework Update Required" (http://technet.microsoft.com/en-us/library/729d1648-ff17-43f9-a1cf-4285a82d4917.aspx). Run this update. A msdaps.dll update is also required, and you can download it from "Update for Windows Server 2003 x64 Edition (KB918980)" at http://go.microsoft.com/fwlink/?linkid=74467. The msdaps.dll requires a server reboot.
If you want to run the Exchange setup as a schema admin and Exchange admin, you can continue with the installation, and the domain/forest will be prepared for you automatically; otherwise, you must prepare in advance.
To begin the Exchange 2007 installation, perform the following:
1. Run the setup.exe file on the Exchange media, and the summary screen will have links to set up the prerequisites for Exchange 2007, which are .NET Framework 2.0, Microsoft Management Console (MMC) 3.0, and PowerShell.
2. Once the prerequisites are installed, click the Install Microsoft Exchange link.
3. The Exchange Server 2007 setup routine will initialize and perform checks on the server. The Exchange Server 2007 Setup wizard will appear. Click Next.
4. Accept the license agreement, and click Next.
5. The option to send errors to Microsoft is displayed. If you enable this option, the system will send errors to Microsoft automatically. Make a selection, and click Next.
6. Select the type of Exchange installation you want. Typical includes the management tools and the hub transport, client access, and mailbox server roles (in a non-clustered manner). Custom allows selection of the roles to be installed with the options to cluster. For now, select Typical. Also on this screen, you can select where to install the Exchange binaries, which by default are installed in the C:\Program Files\Microsoft\Exchange Server folder. If you select Custom, a dialog box will appear, allowing you to select roles and options.
7. The installation will detect that Exchange 2003 already exists in the forest and prompt you to select the Exchange 2000/2003 server that a routing group connector will be configured to. By default, Exchange 2007 makes only one connection to the Exchange 2003 servers; all Exchange 2007 servers will exist in a single routing group because Exchange 2007 uses AD sites instead or Exchange routing groups. Click Next.
8. The readiness checks will run and fail, and a list of the errors and the solutions will appear. For example, the schema hasn't been updated. Click Recommended Action to see steps to resolve.
9. Once there are no problems, you can click the Install button.
10. The system displays installation progress. Once it's complete, click Next. Notice that you can press Ctrl+C to get a copy of this screen and all the other screens, giving you a text-based version of the information.
You might see very long delays at this point, if the schema hasn't been prepared. Once complete, click Finish to complete installation through the Exchange Management Console. To set the product key, select Server Configuration in the navigation pane and click Enter Product Key from the Actions pane. Once the key is checked, click Finish. At the bottom of the display, you'll see the PowerShell command that was used to perform the product key application.
Summary: 1 item(s). 1 succeeded, 0 failed.
Elapsed time: 00:00:00
Warning: The product key has been validated and the product id has been
successfully created. Note: This change will not be complete until the
store has been restarted.
Exchange Management Shell command completed:
set-exchangeserver -Identity 'CN=DALSXC02,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Elapsed Time: 00:00:00
You can now follow the steps to run Performance Analyzer and go to Microsoft Update to get updates for Exchange.
During the installation, Exchange 2007 creates an internally generated certificate to the local Web server, overwriting any previous configuration for SSL. If you want to use a provided certification, you'll need to re-select it through the IIS admin tool.
Your next steps include replicating free/busy/OAB information, and you can do this easily from the Exchange 2003 System Manager snap-in, adding the Exchange 2007 server as a replica, or you can automate this process as described in the Microsoft article "How to Remove the Last Legacy Exchange Server from an Organization" (http://technet.microsoft.com/en-us/library/bb288905.aspx). Once finished, you can move the Offline Address Book (OAB) generation to an Exchange 2007 server. To enable RPC over HTTP, see "How to Enable Outlook Anywhere" (http://technet.microsoft.com/en-us/library/bb123889.aspx).
Some other good reading includes "How to Remove the Last Legacy Exchange Server from an Organization" (http://technet.microsoft.com/en-us/library/bb288905.aspx) and "How to Transition from Single Forest to Single Forest" (http://technet.microsoft.com/en-us/library/aa997617.aspx).