Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Install Windows EBS

Updated: September 22, 2009

Applies To: Windows Essential Business Server

After you prepare your Windows SBS 2003 environment, begin to install Windows EBS. As you install it, you need to complete several tasks that enable Windows EBS to take over roles that are currently performed by Windows SBS 2003. These roles include the following:

  • DHCP

  • DNS

  • Exchange Server

  • Network edge security (for Windows SBS 2003 Premium only. This security is provided by using ISA Server.)

ImportantImportant
You should migrate these roles to the servers running Windows EBS soon after installation. The Guided Configuration and Migration Tasks page on the Windows EBS Management Server provides guidance for migrating these roles. During installation, the Windows EBS Installation Wizard transfers the Active Directory operations master roles from Windows SBS 2003 to Windows EBS. Without these roles, the server running Windows SBS 2003 will restart every hour, beginning seven days after the transfer. You can extend this time to 21 days, providing additional time to migrate your accounts and other services to Windows EBS. To do this, download the software update, Software Update to Support “Join Domain” Migration of Windows Small Business Server 2003 Data and Settings to New Hardware, from the Microsoft Web site.

This document helps you to configure these roles in Windows EBS and to disable them in Windows SBS 2003. This document focuses on the specific configuration tasks that you need to complete to install Windows EBS in a Windows SBS 2003 environment. For general information about installing Windows EBS, see the Windows EBS Installation Guide.

The following diagram illustrates a typical Windows SBS 2003 Premium environment, which uses ISA Server to provide firewall services. Note that the server running Windows SBS 2003 connects your network and your Internet gateway device, and it provides DHCP, DNS, and firewall services. The example IP addresses are typical of a Windows SBS 2003 environment.

Initial configuration of SBS (with ISA Server)

After you install Windows EBS, your environment resembles the following diagram.

5bbe4be5-6be6-47d5-8f39-1c42b88352aa

Note the following:

  • The Windows EBS Security Server enhances network edge security between your network and your Internet gateway device, replacing the Windows SBS 2003 server and its ISA Server component. The Security Server is configured with the IP address settings that were previously configured on your server running Windows SBS 2003. The server running Windows SBS 2003 is configured with new settings. The Security Server is configured as the Internet gateway for your network.

    During Windows EBS installation, you must choose to assign your existing Internet gateway IP address to the Security Server, or to retain that address on your existing server that is running Windows SBS 2003, and assign a different static IP address to the Security Server. Two conditions may result from this decision:

    • If you assign your existing gateway address to the Security Server, then the DNS settings for your network will be incorrect. To correct them, change your DHCP Server service settings to point to the new address of the server running Windows SBS 2003 for DNS.

    • If you assign a new static IP address to the Security Server, the DNS settings will be correct within your network. However, the settings for external connectivity will not be correct, because the existing server running Windows SBS 2003 is no longer the Internet gateway. To correct this, change the gateway IP address in your DHCP Server service settings and in any other applications you may be running, so that they correctly point to the Security Server as the Internet gateway.

  • The Windows EBS Management Server takes over the DHCP role from the server that is running Windows SBS 2003. Then this role is disabled on the server running Windows SBS 2003.

  • The Windows EBS Management Server takes over the DNS role from the server that is running Windows SBS 2003. Then this role is disabled on the server running Windows SBS 2003.

The following diagram illustrates another typical topology for Windows SBS 2003, which does not use ISA Server to provide a firewall, before installing Windows EBS. In this topology, the server running Windows SBS 2003 connects to your local area network and provides DHCP and DNS services. The firewall is provided through a hardware device. The example IP addresses are typical of a Windows SBS 2003 environment.

Initial configuration of SBS (no ISA Server)

While you install and migrate your current network to Windows EBS, your network appears as follows.

Migrating SBS to Essential Business Server

Note the following:

  • The Windows EBS Security Server enhances network edge security between your network and your Internet gateway device, by working with your gateway device. The internal (local area network) IP address of the Security Server is configured with the IP address settings that were previously configured on your gateway device. The hardware device is configured with new settings. The Security Server is configured as the Internet gateway for your network.

  • The Windows EBS Management Server takes over the DHCP role from the server that is running Windows SBS 2003. Then this role is disabled on the server running Windows SBS 2003.

  • The Windows EBS Management Server takes over the DNS role from the server that is running Windows SBS 2003. Then this role is disabled on the server running Windows SBS 2003.

After you finish installing Windows EBS and finish the recommended tasks to migrate and transfer roles and services to your new servers, you must decommission your server that is running Windows SBS 2003, as shown in the following diagram. To do this, perform the procedures listed in Demote and Remove the Server Running Windows SBS 2003 from the Network.

Decommissioning the server for SBS

The following procedures describe how to perform these configuration tasks. The example IP addresses correspond to those in the diagram. Use your own network IP settings when you configure your system.

To join the Windows Essential Business Server Management Server to a Windows Small Business Server 2003 environment
  1. Run the Windows EBS Management Server Installation Wizard. On the Active Directory Domain Selection page, join the Windows EBS Management Server to the Windows SBS 2003 domain. The installation wizard automatically restarts the Windows EBS Management Server to join the designated domain.

  2. After the computer restarts, continue installing with the Windows EBS Management Server Installation Wizard, and click Check Environment to complete the pre-installation checks. If prompted, complete any updates or other configuration tasks described in the wizard.

  3. After finishing the environment checks, continue with the Windows EBS Management Server Installation Wizard. On the page Choose the DHCP Server service page, select the following options:

    1. Select Configure the DHCP Server service in Windows Essential Business Server .

    2. Check Start the DHCP Server service in Windows Essential Business Server .

    3. Click Next.

  4. On the DHCP Settings – 1 of 2 page, type the following settings:

    noteNote
    See the diagrams for examples.

    1. For the Starting IP address, Ending IP address, and Subnet mask values, use the values already set for the DHCP scope of your existing server.

    2. For the Default gateway use the IP address that you will use for the Windows EBS Security Server.

      noteNote
      This must be the same as the internal IP address of the server that is running Windows SBS 2003.

  5. On the DHCP Settings – 2 of 2 page, type the following settings:

    noteNote
    See the diagrams for examples.

    1. Configure the Primary DNS server setting with the IP address of the Windows EBS Management Server.

    2. Configure the Alternate DNS server setting with the IP address of the Windows EBS Messaging Server.

    3. Use the same scope lease duration values for the DHCP service that are configured for Windows SBS 2003.

    4. Use the same values for the DHCP scope exclusion range that are configured for Windows SBS 2003.

  6. Complete the Windows EBS Management Server Installation Wizard.

    noteNote
    When the DHCP service in Windows EBS starts, the server that is running Windows SBS 2003 detects this and automatically turns off the Windows SBS 2003 DHCP Server service.

  7. When the Windows EBS Management Server is installed, do not start installing the Windows EBS Security Server as directed. First, make the following changes on the server that is running Windows SBS 2003:

    1. Run services.msc, select DHCP Server, and then right-click Properties. Change the startup type to Disabled. Click OK.

    2. Change the internal IP address for the server that is running Windows SBS 2003 to its new address (see the diagrams for examples). Make the change by using the Change Server IP Address tool in Windows SBS 2003. For information about how to use this tool, see "To change the IP address of the local network adapter” (http://go.microsoft.com/fwlink/?LinkId=105764).

    3. Run the Windows SBS 2003 Configure E-Mail and Internet Connection wizard (CEICW). For information about how to use the wizard, see "How to configure Internet access in Windows Small Business Server 2003” (http://go.microsoft.com/fwlink/?LinkId=105763).

  8. Move to the Security Server and begin installing Windows EBS.

To install the Windows Essential Business Server Security Server in a Windows Small Business Server Premium environment
  1. Run the Windows EBS Security Server Installation Wizard. On the Mail Gateway Settings page, type the new IP address for the server that is running Windows SBS 2003.

    noteNote
    See the diagram for an example of how to reconfigure your existing server addresses.

  2. On the Security Server Network Integration page, disconnect the external network adapter that is on the server running Windows SBS 2003 from the network, and then perform the required network-integration steps.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.