For the latest information, please see http://www.microsoft.com/windowsserversystem/solutions/branch/default.mspx. The Branch Office Infrastructure Solution (BOIS) provides detailed guidance to help large organizations and enterprises streamline branch office infrastructures. The goal of this streamlining effort is to minimize the total cost of ownership (TCO) and provide the most efficient and effective management, while still providing the required user experience. This Overview is the BOIS starting point for that effort and is intended to provide business and technical decision makers with the information required to determine if the BOIS guidance is appropriate for meeting the needs of their organizations. The following figure shows the information covered in this BOIS Overview document.  Figure 1. BOIS Overview document contents This chapter, the Introduction to the BOIS project and solution guidance, provides a high-level overview and background information about branch office infrastructure solutions and the purpose of the BOIS guidance. The following figure shows the information covered in this chapter.  Figure 2. Chapter 1: Introduction On This PageExecutive OverviewStreamlining a branch office infrastructure is basically a matter of consolidating services and applications, both by centralizing them (if possible) and physically co-locating them (if centralization is not possible). Streamlining branch offices can result in substantial benefits for companies of all sizes, especially large organizations and enterprises. Streamlining branch offices facilitates the efficient use of servers and can provide the following improvements: | • | Better utilization of server capacity. | | • | More efficient systems administration and management. | | • | Faster and more complete recovery of data in the event of a disaster. | | • | Higher degree of standardization and automation. |
The BOIS deliverables provide conceptual information to facilitate the definition and deployment of a streamlined branch office infrastructure solution that provides a comprehensive set of core IT infrastructure services based on the Microsoft® Windows® operating system. The BOIS deliverables also include prescriptive guidance and best practices for implementing a complete and lab-validated single-server solution for the branch office using automated and configurable deployment tools. TerminologyThe BOIS guidance uses some terms and concepts that are specific to this solution. They include the following: | • | Streamline. To design and construct an efficient and effective infrastructure. For the branch office infrastructure, this means simplifying the design in a way that makes the most efficient and effective use of the resources of an organization, reduces TCO and management overhead, and facilitates future growth and management of branch offices. | | • | Branch office. A site that provides specific support for one or more business functions of an organization and uses an IT infrastructure that is partly or completely provided by and managed from a hub site. Also known as a branch site, remote site, or remote office. | | • | Hub site. A central site of an organization that provides the primary IT infrastructure for a specific geographic region or an entire organization, including IT management and support for the branch offices that use this IT infrastructure. Also known as a central site. | | • | Branch office infrastructure. All core business applications and services required to provide the specific business functionality for which the branch office is responsible. These applications and services typically provide directory services, name resolution, and messaging and collaboration support, as well as support for centralization and consolidation applications and services. | | • | Branch office server. A server in the branch office that runs one or more branch office infrastructure applications and services. | | • | Consolidation. The process of reducing the number of servers in an organization. This is generally accomplished in one of the following ways: | • | Centralizing a branch office service or application in the hub site, with each central server providing support for multiple branch offices. | | • | Co-location or isolation of services and applications on a reduced number of servers, potentially a single physical server. |
| | • | Co-location. Installing and running multiple services and applications on a single instance of an operating system in a way that enables them to co-exist with each other on a single server. | | • | Isolation. Running a service or application in a separate partition of the server or co-hosting the service or application in a virtual machine, which runs on the host operating system either with one or more other virtual machines or one or more services or applications running natively (not in a virtual machine) on the host operating system. | | • | Virtualization. The process of running a virtual machine on a physical server. This process can include capturing an image of the physical computer and transferring it intact to a virtual machine, or creating a virtual machine and rebuilding the application server in a separate, clean build. Although the operating system running on the physical computer (known as the host operating system) is Microsoft Windows Server™ 2003, each virtual machine runs its own operating system (known as the guest operating system), such as Windows Server 2003, Windows 2000 Server, or for short-term solutions, Windows NT® 4.0. |
BackgroundThe BOIS guidance is designed to address the needs of enterprises and other large organizations that need to streamline branch office infrastructure. It is based on the following: | • | Assumptions about the organization, its requirements, and its capabilities. | | • | The knowledge and skills required in the IT organization. | | • | The most appropriate software for the branch office infrastructure. |
AssumptionsThe assumptions made for this solution include the following: | • | The organization is investigating the potential for streamlining the branch office infrastructure, but has not yet decided how to accomplish this. | | • | Network connectivity improvements and other upgrades that might be required to streamline branch offices are possible. | | • | The cross-site and cross-team efforts required to streamline a branch office infrastructure can be coordinated and carried out in a way that meets the requirements of each site and team. | | • | Branch office infrastructure services, as covered in this guide, are limited to those provided in Microsoft Windows Server 2003 and Windows Server System™ products, including the following: | • | Microsoft Active Directory® directory service in Windows Server 2003 | | • | Microsoft Domain Name System (DNS) in Windows Server 2003 | | • | Microsoft Windows Internet Naming Service (WINS) in Windows Server 2003 | | • | Microsoft Dynamic Host Configuration Protocol (DHCP) in Windows Server 2003 | | • | File services in Windows Server 2003 | | • | Print services in Windows Server 2003 | | • | Microsoft Exchange Server 2003 | | • | Microsoft Internet Security and Acceleration (ISA) Server 2004 Web caching (excluding firewall, proxy, and Virtual Private Network (VPN)) | | • | Microsoft Virtual Server 2005 | | • | Microsoft Operations Manager (MOM) 2005 | | • | Microsoft Systems Management Server (SMS) 2003 | | • | Microsoft Windows Server Update Services (WSUS) (previously known as SUS 2.0) | | • | Microsoft Baseline Security Analyzer (MBSA) 1.1.1 | | • | Windows Server 2003, Automated Deployment Services (ADS) 1.0 |
|
Additionally, it is assumed that the following is explicitly out of scope for this solution: | • | Network architecture and design, including the firewall or other perimeter security devices. | | • | Design and development of a complete hub site infrastructure. This solution builds instead on the infrastructure design and development covered in Microsoft Windows Server System Reference Architecture (WSSRA), previously known as Microsoft Solution Architecture (MSA) 2.0. For more information about WSSRA, see Windows Server System Reference Architecture at http://go.microsoft.com/fwlink/?LinkId=47216. | | • | Migration of servers. The streamlining process generally requires deploying new or reconfigured branch servers, and migration is not common in this situation. | | • | Deploying any servers except those using Windows Server 2003-based and Windows XP technologies, as covered later in this chapter. | | • | Building the platforms (the underlying hardware and software) for the branch servers, although design and deployment of services on branch servers is covered. Platforms are out of scope for this solution because other documentation provides detailed guidance about deploying server platforms, including the WSSRA guidance referenced previously in this section and the Microsoft Windows Server 2003 Deployment Kit at http://go.microsoft.com/fwlink/?LinkId=46594. | | • | Decommissioning or repurposing existing branch servers. This is because organizations typically have their own decommissioning procedures. | | • | Consolidating databases or storage devices, including storage area networks (SANs), potentially used in branch offices. This is because such devices are generally vendor-specific or already addressed by other consolidation efforts. | | • | Implementation and use of client-side components, including the user interface (UI) and client-side logic, except where it affects the design, deployment, or management of server-side components. |
Knowledge and Skills PrerequisitesThe primary audience for this guidance is the experienced IT professional who is responsible for managing one or more of the technologies currently deployed as part of a branch office infrastructure. The branch office infrastructure consists of many services and applications, so it is unlikely that an individual IT professional will have all of the skill sets required to design and deploy a complete branch office infrastructure solution. However, the design and deployment teams must have members who together understand all core technologies required in a branch office infrastructure, especially those related to the following: | • | Windows Server 2003 operating system. | | • | Windows XP operating system. | | • | N-Tier client/server architecture. | | • | Networking and connectivity. | | • | Service operations. | | • | Reliability, availability, security, performance, compatibility, and other hardware and software management concepts. | | • | The infrastructure services and technologies covered in this solution (as specified in the following section). | | • | Deployment concepts and processes. | | • | Software distribution. | | • | Update management. | | • | Backup and recovery. | | • | Automation tools. | | • | Virtual machine concepts and processes. |
The knowledge and experience requirements will vary based on the most appropriate solution for your organization, but the IT professionals responsible for designing and deploying a branch office infrastructure solution generally must have a good working knowledge of all of the services and technologies required to implement a Windows-based branch office infrastructure (as covered in the Assumptions section of this chapter). Branch Office SoftwareMost organizations have fairly heterogeneous environments. As a result, they must generally expend considerable effort toward standardizing their infrastructures and minimizing the number of models and versions in these infrastructures. Many organizations have recently migrated to the latest versions of Windows operating systems or are planning such a migration in the near future. Therefore, the BOIS guidance is based on Windows Server 2003 with Service Pack 1 and Windows XP Professional with Service Pack 2. FeedbackPlease direct questions and comments about this guide to BOISfdbk@microsoft.com. Please direct general questions and comments about this type of guidance to cisfdbk@microsoft.com.
| |