Microsoft Small Business Server 2003 Unleashed - page 37


The installation of SBS 2003 from the SP1 integrated media is not significantly different from the original installation process. Outside inserting more CDs (if the DVD is not used), those who have done several SBS 2003 installations will not find many changes with this media. Those who have not done an SBS installation previously will find the process described in this chapter.

In addition, this chapter covers some basic guidelines for using the setup log files to troubleshoot installation problems. The log files are stored in three main log folders, and the Exchange installation log is stored in the root of C: just like every other Exchange installation. The two main setup log files, eventlog.txt and errorlog.txt, contain the bulk of the setup information needed to identify where problems occurred. The chapter also covered the use of the err.exe tool to translate Microsoft error codes from the log files.

The bottom line for server installation is that getting it right the first time is still critical for the long-term health of an SBS server. Even though the setup process is familiar to those who currently support SBS, going through a few test installs with the new slipstreamed media is still recommended prior to a production deployment.

Best Practice Summary

  • Always install SBS manuallyEven if SBS comes preinstalled on a new server, reinstall the system from scratch to ensure that the server is optimally configured for its environment.

  • Location of data foldersNon-OS data, including Exchange and ISA logs and databases, should be placed on a drive other than C:. Ideally, multiple fault-tolerant disks would be used to store each type of data.

  • Dealing with PPPoEIf the broadband network access is provided through a PPPoE account, use a third-party hardware router/firewall to maintain the PPPoE account connection instead of the external NIC of the SBS server.

  • Be cautious when setting up VPN access into the SBS networkLook at all the security implementations and limitations before deciding to implement VPN into your SBS network. Review the VPN Quarantine features of ISA 2004 to plan the best VPN implementation if you do choose to go this route.

  • Do not configure Automatic Updates to automatically install updates at a scheduled timeUpdates can be configured to download automatically, but the system administrator should only install updates manually.

  • Install SBS three timesBefore you attempt your first production installation of SBS 2003 SP1, run through the installation process three times on a test box or in a virtual environment to become familiar with the installation process.

  • Use err.exe to translate Microsoft hexadecimal error codeserr.exe can help you figure out what the error code means, which can help you track down the possible sources of the problem.

Part III: SBS 2003 Networking



CHAPTER 5 DNS, DHCP, and Active Directory Integration


CHAPTER 6 Internet Information Services


CHAPTER 7 Routing and Remote Access Service, VPN, and Firewalls


CHAPTER 8 Terminal Services

Chapter 5. DNS, DHCP, and Active Directory Integration


  • Review of Active Directory and DNS Integration

  • Configuring DNS for the Internal Network

  • Configuring DNS to Resolve Public Internet Addresses

  • Configuring DHCP for the Internal Network

  • Troubleshooting DNS, DHCP, and Active Directory Issues

The core of every SBS installation is a solid Active Directory infrastructure. Because Active Directory depends heavily on network technologies such as DNS, a successful and healthy SBS implementation must have a correctly configured network. This applies not only to the server but to the workstations as well. This chapter covers the default network configuration of an SBS installation in detail and looks at the problems that can arise when the configurations change.