Scaling the Solution

While the BDD 2007 documentation was written to address the large-scale needs of enterprises, the BDD 2007 technology can scale to both small and medium organizations. Smaller organizations can bypass portions of the BDD 2007 documentation and use a more streamlined process. Additionally, organizations can minimize infrastructure requirements by deploying BDD 2007 without a Microsoft Systems Management Server (SMS) infrastructure.

The sections that follow describe how to use BDD 2007 in small- and medium-sized organizations.

On This Page

Small Organizations Small Organizations
Medium-sized Organizations Medium-sized Organizations

Small Organizations

Small organizations typically have one or two technologists who will perform the tasks required by multiple feature teams. Additionally, small organizations typically deploy smaller numbers of computers, so it is more time-efficient to use a more manual process rather than investing time to completely streamline the deployment process. Small organizations can react more quickly to problems that occur during or after deployment, and therefore do not require as extensive testing beforehand. Because small organizations are personally aware of every computer, they do not need to dedicate as much energy to inventory and management.

Given these factors, small organizations should use the following abbreviated process to create a BDD 2007 infrastructure and deploy Windows:

  • Read the Getting Started Guide.

  • Read the Release Notes.

  • Read this guide, the Plan, Build, and Deploy Guide.

  • Read the Computer Imaging System Feature Team Guide. This guide walks through the process of configuring a deployment infrastructure. Read this guide before beginning to configure the deployment infrastructure to gain an understanding of the server and lab requirements and how the organization might be able to use BDD 2007 with its existing equipment.

  • Optionally, read the Application Compatibility Feature Team Guide. This guide describes how to test applications to ensure they will work properly with the new operating system. Most common applications will work properly, however, if the organization has custom applications or other applications that might not work properly, team members should read this guide and test the applications thoroughly.

  • Optionally, read the Application Management Feature Team Guide. This guide contains information to help automate the deployment of applications. Depending on the number of computers and applications the organization plans to deploy, it may be more efficient to manually install applications after deploying the operating system.

  • If the organization plans to deploy Microsoft Office, read the Office Deployment Guide. Alternatively, if the organization is deploying a small number of computers, teams might choose to skip this guide and manually install Microsoft Office after completing Windows deployment.

  • Read the User State Migration Feature Team Guide existing computers will be replaced. If the teams have not assessed application requirements already, they should take some time to verify that User State Migration feature team correctly transfers all application-specific files and settings. If the organization is deploying computers to new users, this guide is unnecessary.

  • Optionally, read the Security Feature Team Guide. This guide discusses how to both improve the security of client computers and to improve the security of the deployment infrastructure. If the default security settings meet the organization’s needs, teams need not read this guide.

  • Read the Deployment Feature Team Guide and the Lite Touch Installation Guide. These documents describe the actual deployment process.

Medium-sized Organizations

Medium organizations typically have a few technologists who are familiar with most aspects of the organization’s IT infrastructure. Additionally, medium-sized organizations typically deploy smaller numbers of computers than enterprises. Therefore, the deployment requirements for medium-sized organizations are not as extreme as they are for enterprises, however, BDD 2007 can still improve the efficiency of medium-sized organizations.

Given these factors, medium-sized organizations should use the following abbreviated process to create a BDD 2007 infrastructure and deploy Windows

  • Read the Getting Started Guide.

  • Read the Release Notes.

  • Read this guide, the Plan, Build, and Deploy Guide.

  • Read the Infrastructure Remediation Feature Team Guide. It is important that medium-sized organizations track their computer hardware and software, and having an accurate inventory will help the organization plan for upgrade and enable teams to ensure compatibility for all the applications in the organization. For many medium-sized organizations, this part of the process will reveal previously unknown software that individuals or groups within the organization have deployed without IT assistance. Being aware of these applications will enable teams to ensure that the applications function properly after the new operating system deployment. Additionally, this guide will help identify new infrastructure requirements for the deployment servers.

  • Read the Computer Imaging System Feature Team Guide. This guide walks through the process of configuring a deployment infrastructure.

  • Read the Application Compatibility Feature Team Guide. This guide describes how to test applications to ensure that they will work properly with the new operating system. Focus testing efforts on a small audience and on custom applications and industry-specific applications that are least likely to work properly with the new operating system.

  • If the organization plans to deploy Microsoft Office, teams should read the Office Deployment Guide. Alternatively, if the organization is deploying a small number of computers, teams might choose to skip this guide and manually install Microsoft Office after completing Windows deployment.

  • Read the Application Management Feature Team Guide. This guide contains information to help automate the deployment of applications.

  • Read the User State Migration Feature Team Guide if existing computers will be replaced. If the organization is deploying computers to new users or performing in-place upgrades, teams need not read this guide.

  • Read the Security Feature Team Guide. This guide discusses how to both improve the security of client computers and to improve the security of the deployment infrastructure. If the default security settings meet the organization’s needs, teams need not read this guide.

  • Read the Deployment Feature Team Guide. Then, read the Lite Touch Installation Guide to prepare BDD 2007 to deploy client computers. These documents describe the actual deployment process. Alternatively, if the organization plans to deploy a large number of client computers and would rather spend additional time configuring and testing the deployment infrastructure to spend less time deploying client computers, teams should read the Zero Touch Installation Guide instead of the Lite Touch Installation Guide. If the organization chooses Zero Touch installation (ZTI) and uses Microsoft Operations Manager (MOM), teams should also read MOM 2005 Management Pack for Zero Touch Installation.

Download

Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions