Getting Started Guide
Additional Component Summary
The Solution Accelerator for BDD combines many different technologies into a single, integrated solution for computer deployments. Each technology may require software and hardware obtained from different locations. The following sections summarize the feature teams and help you collect all the required resources for them. This information is consolidated from all feature team guides. For more detailed information, see the corresponding feature team guide. To save time in the Planning and Developing phases of the project, Microsoft recommends that you review these additional requirements and start collecting the necessary components while the project team is getting organized. Almost every feature team needs a lab environment. While you could construct separate labs for each feature team, most organizations create a single lab that shares facilities such as servers, networks, system backup, data repositories (such as Microsoft Visual SourceSafe®) with separate workspaces (computers and network shares) for each feature team. This enables the teams to work separately when necessary and jointly when appropriate. It also enables you to minimize the number of computers and servers required. For more information about building a test lab, see the Test Feature Team Guide and Infrastructure Remediation Feature Team Guide. On This PageComputer Imaging System Feature TeamYou're probably familiar with some of the many imaging tools, but you might not know how you can use them to support desktop deployment. In fact, using them effectively is one of the big challenges. We recommend a specific solution for imaging the operating systems and the core applications that are part of a standard desktop. The solution is modular. It allows you to separately manage each system component. The advantage is that when changes occur—and they will—you don't have to re-engineer the entire process. The solution also provides the tools and scripts to install, configure, and customize the Windows XP platform and incorporate updated service packs. The process is a robust starting point for building systems that are easily and broadly extensible.  The Computer Imaging System process is comprised of:
LabYou should configure the test lab with at least the following items readily available. And, to the extent possible, you should configure the lab to fully represent the production environment. The following describes these items:
SoftwareA sample scenario in which to apply this solution has been provided, using a fictitious organization, Trey. For the Trey example, the following media that shipped with the hardware will be needed:
Hardware-Specific MediaDepending on the type of workstation hardware that is being built, you will need software from the hardware vendor—that was not included on the install media for the build system—in order to make the system fully functional. Some of this software is provided on a CD-ROM or DVD-ROM by the hardware manufacturer, but other pieces of this software must be downloaded from the Internet. Note If you are providing this solution to a customer, you can save considerable time on-site by collecting all of these required files in advance. Note Although Virtual PC 2004 is not technically a hardware platform, its virtualized hardware platform acts like one. No drivers are required for Windows XP Professional to install in a virtual machine, but you can improve performance by installing the latest version of the Microsoft Virtual PC Additions. For Windows XP SP2, use the Additions from Virtual Server 2005, because they have been modified to offer better performance under Windows XP SP2 than those included in Virtual PC. Updated versions will be included in Microsoft Virtual PC 2004 Service Pack 1. This solution ships with example configurations for a fictitious organization, Trey Research. The following files need to be downloaded, extracted, and copied into the build to ensure that all the hardware models defined for the sample organization work correctly. Where possible, the direct URL has been provided to the file. For the latest versions of these files, visit the manufacturer’s Web sites:
Details on the files needed for the hardware devices included as part of the Trey example hardware configurations are included next. Note When you are instructed to copy files to a folder that doesn’t yet exist in the Computer Imaging System, create the folder. Dell OptiPlex GX270Analog Devices ADI 198x Integrated Audio Driver Version 5.12.01.3555
Intel Chipset Software Installation Utility Driver Version 5.00.1012
Intel Gigabit LOM Driver Version 7.0.34.2
Intel Springdale-G Integrated Video Driver Version 6.13.01.3510
Dell OpenManage Client Instrumentation Version 7.1.382
Dell Latitude D600SIGMATEL STAC 9750 AC97 Driver Version 6.14.01.3913
ATI Mobility Radeon 9000 Driver Version 8.03_15973C
Dell QuickSet Version 3.9.4, A27
Intel Mobile Chipset Driver Version 5.00.1012
Note The Intel Mobile Chipset Driver package is an older version of the Intel Chipset Software Installation Utility Driver package downloaded for the Dell OptiPlex GX270. The only difference is that the GX270 package includes one additional set of files for the latest Intel 865 desktop chipset. This download can be skipped, as long as the GX270 package is included. O2Micro O2711EC1 PCMCIA/SmartCard Controller Driver Version 3.0.0.1, A02
Conexant D480 MDC V.92 Modem Driver Version 7.12.9, A14
Alps GlidePoint/StickPointer Driver Version 5.4.102.12
Broadcom 570x Gigabit Integrated Controller Driver Version 6.64.0.0
Intel Pro/Wireless 2100 LAN miniPCI Adapter Driver Version 1.2.3.10
Note The Dell OpenManage Client Instrumentation package was not included here because it was already downloaded to support the Dell OptiPlex GX270. Dell Precision Workstation 670Analog Devices ADI 198x Integrated Audio Driver Version 5.12.01.3555
ATI 128MB PCI Express x16 ATI FireGL V3100
Adaptec CERC SATA1.5/6ch (optional hardware for Dell Precision 670)
Note The CERC controller is not a default option on the Precision 670 workstation. The default configuration calls for a single SATA drive connected to the onboard SATA controller. This configuration is supported by Windows XP Professional x64 Edition without additional drivers. The CERC controller is a common choice, however, and is described as an example of a typical storage driver that requires additional drivers. Follow these steps only if you ordered a CERC controller for your Dell Precision 670. Note For additional information about adding storage drivers to an unattended install, see the Microsoft Knowledge Base article 816299 at: http://support.microsoft.com/default.aspx?scid=kb;en-us;816299 Intel PRO/1000 Network Connections v8.4.21.0,A00
HP Compaq Business Desktop d530 (SMF)ADI SoundMax AC97 Integrated Digital Audio Driver Version 5.12.01.3620 D
Intel Chipset Support for Windows 5.1.0.1008 A
Note The Intel Chipset Support for Windows package downloaded from the HP Web site contains many of the same files previously downloaded for the Dell hardware. However, this download includes updated versions of the 845G.INF, 845G.CAT, ICH4USB.INF, and ICH4USB.CAT files; these should be merged into the Master $OEM$\$OEM$\$$\INF (INF files only) and Master $OEM$\$OEM$\$1\Drivers\IntelINF (INF and CAT files) directories. Intel Extreme Graphics 2 Driver for Windows 2000/XP Version 6.14.10.3924 A
Note The Intel Extreme Graphics 2 Driver for Windows 2000/XP package downloaded from the HP Web site is a more recent version of the Intel Springdale-G Integrated Video Driver. If you have downloaded both and want to use the latest version, be sure to put Drivers\HP\d530\Video ahead of Drivers\Dell\OptGX270\Video in the PNP driver path. Broadcom Drivers for Multiple Operating Systems Version 7.35 A
Note A separate download for the Broadcom Driver for Windows XP (SP26992) is available on the HP site, but there is no easy way to extract the drivers from this download. Also note that this Broadcom driver is newer than the Broadcom 570x Gigabit Integrated Controller Driver downloaded for the Dell Latitude D600. If you have downloaded both and want to use the latest version, be sure to put Drivers\HP\d530\NIC ahead of Drivers\Dell\LatD600\NIC in the PNP driver path. InterVideo WinDVD Player Software for Windows 2000/XP Version 4.0.11.300 A
Insight Management Agent for Clients Version 5.01 B
HP Compaq Tablet PC TC1100Tablet PC ADI Soundmax Audio Driver Version 5.12.01.3920
NVIDIA Video Driver for Windows XP Tablet PC Edition Version 1.00 D
Tablet PC Button Driver Version 1.00 B
Tablet PC Wacom Digitizer Driver Version 1.6.1 A
Agere Systems AC'97 Modem Driver Version 2.1.41.10 (2 Mar 05)
Broadcom BCM440x 10/100 Ethernet Drivers Version 1.00 B
Intel PRO/Wireless 2100 3B Mini PCI Adapter Driver for Windows XP Tablet PC Edition Version 2.00 B
Support Software for Bluetooth by hp Version 1.00 E
Intel Chipset Installation Utility Version 5.00 A
Q Menu Software for Tablet PC Version 2.00 B
Tablet PC TI PCI1620 4in1 CardReader Driver Version 1.01 B
Motion Computing M1400 Tablet PCSigmatel C-Major Audio Version 6.14.1.4200
IntelliSonic DXEC .02 Speech Enhancement (Knowles Acoustics)
Motion Button Driver Version 3002
Intel Chipset Version 5.1.0.1007
Motion Dashboard Version 3.0.3.4
PCTel Modem
Intel 82855-GME Graphics Graphics Driver Version 6.14.10.3762
RealTek NIC Version 5.505.1004.2002
Bluetooth Driver and Utilities Version 1.4.2.10
Toshiba Portege M200 Tablet PCToshiba Rotation Utility for Windows XP Version 3.00.00.03
Toshiba Zooming Utility for Windows XP Version 2.0.0.13t
Toshiba 802.11a/b/g Driver Set (Intel, Cisco, Atheros) for Windows XP Version 1.11
Toshiba Mobile Extension 3 for Windows XP Version 3.59.00.XP
Toshiba Wireless Hotkey Utility for Windows XP/2000 Version 2.0.0.5
ADI WDM Audio Driver for Windows XP/2000 Version 5.12.01.3670
Alps Touchpad Driver for Windows XP Version 6.0.302.3
FREECOM Cable II Cardbus Driver for Windows XP Version 208.2
Toshiba ACPI Common Modules for Windows XP Version 6.01.01.TE
Toshiba Bluetooth Stack for Windows XP Version 3.00.00A
Toshiba Tablet PC Buttons Driver for Windows XP Version 1.0.0.5-RC2
Windows XP Display Driver for nVidia GeForce FX Go5200 Display Adapters Version 6.14.01.4591
Toshiba SD Card Driver Set for Windows XP Version 2.0.4-RC2
Intel Chipset Software Installation Utility for Windows XP/2000/98SE Version 4.30.1006
Toshiba Software Modem Driver for Windows XP/2000 Version 2.1.22
Toshiba Fast Ether LAN Driver for Windows XP/2000 Version 6.4.14
Toshiba Fast Infrared Driver for Windows XP/2000 Version 5.1.2500.0b-RC2
CD-ROM-Based ApplicationsThese are the files you need to copy from the CD-ROMs provided by the hardware manufacturer for each specific model. They must be copied into the build to ensure that all the hardware models defined for the Trey organization will work correctly.
Windows XP Professional Security UpdatesDownload the required Windows security updates from the Microsoft Windows Update Web site at http://v5.windowsupdate.microsoft.com/catalog/en/default.asp. This site allows you to query for and download the updates rather than install them. Once you are connected to the Web site, click the Find Microsoft Windows updates link. Select the appropriate operating system for each source directory that will be updated:
Click the Search button, and then select the Critical Updates and Service Packs links. The resulting list contains updates for components other than Windows XP; only Windows XP updates can be slipstreamed into the Windows source directory. Also, some updates have been superseded; only the latest update needs to be downloaded. As of July 31, 2005, the following updates are required for Windows XP Service Pack 1:
As of July 31, 2005, the following are required for Windows XP SP2:
Download the following updates from http://www.microsoft.com/downloads:
Add the needed updates to the download basket; when all have been selected, download them to a temporary location such as C:\Temp. When the download is complete, copy all the resulting executables into the same folder, Unattend\Source\XPPro\SP1Hotfixes for Windows XP Service Pack 1 or Unattend\Source\XPPro\SP2Hotfixes for Windows XP SP2. Windows XP Professional Critical UpdatesIn addition to the Windows security update hotfixes described in the previous section, additional security updates need to be downloaded for inclusion in the image. These updates are applied during the image build after Windows has been installed. The process for downloading the required updates is the same as the process used for downloading Windows security update hotfixes. Connect to the Microsoft Windows Update Web site at http://v5.windowsupdate.microsoft.com/catalog/en/default.asp. Once you are connected to the Web site, click the Find Microsoft Windows updates link. Select the appropriate operating system:
Click the Search button, and then select the Critical Updates and Service Packs links. Select all the non-Windows updates (those updates not selected before). Also, some updates have been superseded; only the latest update needs to be downloaded. As of July 31, 2005, the following updates are required for Windows XP Service Pack 1:
As of July 31, 2005, the following updates are required for Windows XP SP2:
Add the needed updates to the download basket; when all have been selected, download them to a temporary location such as C:\Temp. When the download is complete, copy all the resulting executables into the same folder; for example, Unattend\Source\XPPro\SP1Hotfixes for Windows XP Service Pack 1 or Unattend\Source\XPPro\SP2Hotfixes for Windows XP SP2. Windows XP Professional Component UpdatesSeveral components included in Windows XP have been upgraded since the release of Windows XP. You are not required to update these as part of the image-creation process, but this is often the best time to do so, because the effort required to integrate these updates into the image is less than the effort required to deploy them at a later time using other software distribution methods. Common Microsoft components that can be added to the image include the following:
User State Migration Feature TeamOne of the most tedious and time-consuming tasks during deployment is identifying data files and settings on users' current desktops, saving them, and then restoring them. You can easily dismiss this task as unnecessary. However, Microsoft’s experience shows that users spend significant amounts of time restoring items such as wallpaper, screen savers, and other customizable features. In addition, most users do not remember how to reapply these settings. Migrating these items can increase user productivity and satisfaction. To address this task, this solution proposes a step-by-step process called User State Migration.  The following list outlines the User State Migration development process:
PersonnelThe developers need access to SMEs for all application data and settings to be migrated. They are typically the same SMEs used in application compatibility testing and in automating installations (application packaging). LabThe lab should have the following:
SoftwareThe USMT team needs USMT 2.6 executables and configuration files. They are available in the solution download. Application Compatibility Feature Team Before you move from your current version of the Microsoft Windows operating system to Windows XP Professional, you must test your applications to ensure that they are compatible with the new operating system. Your organization may have up to several thousand applications installed across distributed networks. Compatibility problems with one or many of these applications can mean costly work stoppages. By testing applications and solving compatibility problems, you save time and money for your organization. Although most applications developed for earlier versions of Windows will probably perform well on the new versions, some applications might behave differently due to new technologies within the new versions. The applications that you need to test to ensure compatibility include:
PersonnelThe developers require access to SMEs for all applications to be tested. They are typically the same SMEs used as resources for the USMT and application packaging tasks. LabThe lab requires target computers. These are computers with the target Windows XP-based image installed in order to test the application’s Windows XP compatibility. SoftwareThe Application Compatibility feature team needs the following applications:
For each application to be tested, the developers need a copy of the application’s installation media and any configuration documentation. The IT department or the SME should be able to provide this. HardwareThe team needs a Windows-based computer to host the Application Compatibility Analyzer and database. OtherThe team needs a deployment mechanism for the Application Compatibility Analyzer. This could be a logon script, Web site, or other deployment mechanism. Supplemental Application Feature Team There may be hundreds or thousands of applications on your company's workstations. Often, each of these applications was installed differently on each workstation, depending upon who performed the installation. This inconsistency across workstations leads to usability and support issues. If an application is packaged, it can be installed on a desktop without user intervention. The person doing the packaging has decided where to install the application and has selected settings or options. The result is an executable file that is consistent across the organization and very simple to install. Double-clicking or typing one line of information is all that is required to launch and run the complete installation. This component describes some of the approaches to packaging applications that you can use with the solution. PersonnelThe developers need access to SMEs for all applications to be packaged. They are typically the same SMEs used in USMT and application compatibility testing. LabThe lab needs:
SoftwareThe Supplemental Application feature team needs:
Infrastructure Remediation Feature Team Understanding your network environment is critical for any project that introduces changes. To plan and prepare to incorporate these changes, you must first understand the current status of your organization's environment, identify other sources of change that may affect this project, perform a risk mitigation approach to the changes, and then incorporate the proposed changes. It has been demonstrated that organizations can solve and possibly avoid most networking problems by creating and maintaining adequate network documentation. Using a networking tool, you can:
SoftwareThe Infrastructure Remediation feature team needs the Access database application, which is available on volume license media. You use Access to create hardware inventory reports against the application compatibility database. This could be the same installation that the Application Compatibility feature team uses. OtherThe team needs access to current network topology diagrams and network device inventory information. Deployment Feature TeamIn large organizations, deployment is a resource-intensive and time-consuming process. This solution details planning steps that streamline the up-front work. It also describes specific deployment steps that greatly simplify installing workstation desktops. Deployment planning and pilot testing should be part of any internally developed process. Processes will differ primarily around the technologies used for the deployment.  The Deployment Process consists of the following four phases:
LabThe Deployment feature team needs:
SoftwareThe team needs the deployment server download (.msi file) that contains the BDD server components. Core Applications Feature Team This module covers how to set up Office 2003 Editions for deployment as part of the base workstation image. Microsoft Office is often a corporate standard application suite. Therefore, many organizations consider it to be an integral part of workstation deployment. The BDD solution treats Office 2003 Editions as a core application to be included in the base workstation image that is used during the corporate deployment of Windows XP. PersonnelThe developers need access to SMEs to understand all areas where core applications and custom Office solutions such as macros and Microsoft Visual Basic® for Applications (VBA) are used. LabThe Core Applications feature team needs:
SoftwareThe team needs:
Operations Readiness Feature Team The Operations Readiness feature team is responsible for a smooth and successful handoff of the deployed solution to the in-place IT operations staff. This is a very important aspect of the overall project because the success of the handoff directly reflects on the success of the deployment project. To ensure this success the activities of the feature teams must be integrated with the ongoing management and operating functions of the IT operations staff. The Operations Readiness feature team can facilitate deployment by completing the following tasks:
The Operations Readiness feature team does not initially require any additional personnel, lab, or software resources for this project. Security Feature Team The Security feature team has a very important role in the overall success of the deployment project. As you are aware, security is a primary concern in all organizations. The goal of the Security feature team is to secure the organization's data. Inadequate security in an organization can result in lost or corrupted data, network downtime, lost productivity, frustrated employees, overworked information technology employees, and possible stolen proprietary information that results in lost revenue. To ensure adequate security measures are in place your security team should:
The Security feature team does not initially require any additional personnel, lab, or software resources for this project.
|
