1. Deploying Vista and 2007 Office System with BDD 2007
Slide Title: Title Slide
Keywords: Title Slide
Key Message: Title Slide
Slide Builds: 0
Slide Script:
Hello and welcome to this Microsoft TechNet session on Deploying Windows Vista and 2007 Office System with Business Desktop Deployment My name is {insert name}. Business Desktop Deployment, or BDD, has changed the face of scaled desktop deployments, providing true end-to-end guidance and automation for all required desktop deployment processes.
Slide Transition: During this session, we’ll explore how BDD 2007 enables Light Touch and Zero Touch deployment of Windows Vista and the 2007 Microsoft Office system to the desktop.
Slide Comment:
Additional Information:
Deploying Vista and 2007 Office System with BDD 2007

2. Business Desktop Deployment New deployment tools/retired tools
What Will We Cover?
Business Desktop Deployment
New deployment tools/retired tools
Deployment of Windows Vista
Deployment of 2007 Microsoft Office System
Slide Title: What Will We Cover
Keywords: What Will We Cover
Key Message: What we will cover
Slide Builds: 3
Slide Script:
We will look at how the deployment toolset has changed for operating systems and for Office. Both are now language-neutral and designed with deployment in mind. However, some of the tools that you are accustomed to using have become obsolete.
[BUILD1] We will look specifically at how a Windows Vista deployment will be accomplished. We will see how the new WIM image format works and how to design a light touch or zero touch deployment of the new operating system.
[BUILD2] Then we will focus on 2007 Microsoft Office and how Office deployment will change with this new version.
[BUILD3] Finally, we will tour and use the new Business Desktop Deployment 2007 Solution Accelerator. The newest version of this tool is more useable and includes helpful wizards and checklists to help you step through the potentially complex process of planning and executing a major deployment.
Slide Transition: As with most TechNet sessions, some prior experience of Microsoft technologies or similar technologies is always helpful. Here’s a brief overview of what would be helpful, but not essential, for this session.
Slide Comment:
Additional Information:

3. Level 200 Helpful Experience
Experience deploying desktop operating systems
Experience with Systems Management Server
Experience deploying Microsoft Office
Slide Title: Helpful Experience
Keywords: Helpful Experience
Key Message: Helpful Experience
Slide Builds: 3
Slide Script:
As we go through today's session, you will hear various Microsoft acronyms and terminology. While we will explain all new terms related to today's session, there are some general terms from the industry or from other versions of Microsoft products that we may not spend time on. To help you out, we have listed the areas that it may be helpful to be familiar with, either prior to this session or to reference afterwards.
[BUILD1] It will be helpful to have some experience deploying a desktop operating system. Even if your experience has been with a high-touch, manual process, it will help you to understand the pains and how Microsoft solutions will reduce the cost of deployment.
[BUILD2] We will be talking extensively about Systems Management Server 2003 and the next release, System Center Configuration Manager Although not essential, it will be helpful if you have some familiarity with SMS.
[BUILD3] We will be talking about the changes in Office deployment for Office 2007, so it will be helpful if you have done some administrative installation of Office, such as using administrative install points created using SETUP.EXE /A.
Slide Transition: To cover the topics mentioned and keep the session flow going, we have divided the session up into the following agenda items.
Slide Comment:
Additional Information:
Level 200

4. Applying the Business Desktop Deployment 2007
Agenda
Applying the Business Desktop Deployment 2007
Understanding Windows Vista Deployment Technologies
Deploying 2007 Microsoft Office System
Slide Title: Agenda: Applying Business Desktop Deployment 2007
Keywords:
Key Message: Agenda
Slide Builds: 0
Slide Script:
What do we want to do with BDD? What capabilities are present? How we use those capabilities?
Slide Transition: What does the BDD contain?
Slide Comment:
Additional Information: 4

5. BDD 2007 Solution Accelerator
End-to-end guidance, best practices, and tools for efficient planning, building, and deploying Windows and Microsoft Office
Based on real-world experience and industry best practices
Increase automation
Decrease costs
Slide Title: BDD 2007 Solution Accelerator
Keywords: BDD 2007, Desktop Deployment, Vista, Office 2007
Key Message: BDD 2007 is made up of best practices and tools for deploying Windows and Office.
Slide Builds: 1
Slide Script:
BDD 2007 is the new version of the Business Desktop Accelerator, which is a kit of best practices and tools for deploying both Windows and Office. It is based on real-world experience from Microsoft partners, Microsoft Consulting Services, and users in the field. Microsoft has taken all of this experience and put it together in the BDD. It identifies the pain points and manual processes of a typical deployment, and offers better ways of deploying.
The overall goal of the BDD is to decrease the costs of deployment. The best way to do this is to reduce touch and relieve the IT department of performing repetitive tasks during a deployment.
[BUILD1]
BDD 2007 breaks the process down into several portions and enables you to identify a team for each portion. Each team can deal with a discrete task that is integrated with the rest of the project. BDD 2007 updates this process for Windows Vista and Office 2007.
Slide Transition: We’ll see how to deploy the 2007 Office System using SMS in the next demonstration.
Slide Comment:
Additional Information:
Manual Deployment
$500 - $1000 per PC
Light Touch
~ $350 per PC
Zero Touch Less than $100 per PC 5

6. BDD Computer Imaging Process
BDD server
Windows Vista
Applications
Drivers
Gather source
files
Configure
build
BDD Workbench MMC
Windows System Image Manager
Slide Title: BDD Computer Imaging Process
Keywords: BDD 2007, Computer Imaging
Key Message: The imaging process as defined by BDD requires a BDD server and an imaged workstation.
Slide Builds: 6
Slide Script:
The first few steps take place on the BDD server. Then you apply the image to your reference computer. Here is the general process.
[BUILD1]
First, gather the necessary source files. Of course, this will include Windows Vista. In addition, collect all the necessary drivers for your environment. If you are using SMS, perform a hardware inventory to create a report of the hardware that will require drivers. Applications, such as Microsoft Office, that you have elected to include in the base image should also be collected at this point.
[BUILD2]
Use the BDD Workbench MMC that we just employed in the previous demonstration to configure the build.
[BUILD3]
Now the BDD Workbench MMC can be used to build the Lab CD.
[BUILD4]
Next, configure the build on a lab computer. Start with a blank computer, not an upgraded one. Install Vista in the desired configuration.
[BUILD5]
The System Center Configuration Manager Task Sequencer, which is built into BDD, will guide you through the configuration, application installation, and sysprep of your image.
[BUILD6]
BDD will then direct you to capture the image using the Lab CD and the included Windows PE. A WIM will be created containing your new base image.
Slide Transition: Alternately, some organizations may just choose to deploy the Vista image as it is shipped.
Slide Comment:
Additional Information:
Build lab CD
(Windows PE)
BDD Workbench MMC
PEIMG (behind the scenes)
Windows PE 2.0
SETUP.EXE
IMAGEX (WIMGAPI.DLL)
Lab CD
Install
Windows Vista
Reference computer
SCCM 2007 task sequencer
Applications (maybe), settings
Sysprep
Windows Vista
Execute
task sequence
Lab CD
Capture image
Windows PE 2.0
IMAGEX (WIMGAPI.DLL) 6

7. BDD Computer Imaging Process
Gather source
files
Install
Windows Vista
Configure
build
Execute
task sequence
Capture image
Build Lab CD
(Windows PE)
Windows Vista offers more options
HAL-independent images
Offline servicing (drivers and security updates)
Provided as a Sysprep image (staged)
Some may choose a shorter route
No applications on image
Light touch only
Slide Title: BDD Computer Imaging Process
Keywords: BDD 2007, Light Touch, Imaging
Key Message: If you do not have complex requirements for your deployment, you can use a simplified imaging process.
Slide Builds: 1
Slide Script:
Since the image is HAL-independent and drivers and security updates can be added as additional components while the image is offline, Vista is ready to be deployed. If you calculate that the amount of time that you would spend customizing the image is not worth the resulting convenience at the desktop, you can use a much shorter imaging process.
[BUILD1]
Simply inject the new source files and drivers into the image, create an unattend.xml file using Windows System Image Manager, and move on to deployment.
This process will be much quicker in the lab, but it will require additional steps at the desktop installing applications. It is also not compatible with SMS OSD, so it would not work for a zero touch deployment.
Slide Transition: Let’s see how this new BDD Light Touch Deployment works.
Slide Comment:
Additional Information:
Gather source
files
Configure
Unattend.xml 7

8. Applying the Business Desktop Deployment 2007
Agenda
Applying the Business Desktop Deployment 2007
Understanding Windows Vista Deployment Technologies
Deploying 2007 Microsoft Office System
Slide Title: Agenda: Using the new Vista deployment features.
Keywords: Agenda
Key Message: Agenda
Slide Builds: 2
Slide Script:
First we will introduce the many changes to deployment included in the new Vista architecture. Vista is delivered in a new file format that exposes new techniques and features for deployment.
[BUILD1] Then we will turn our attention to deploying Office We will look at how deploying Office 2007 is different from previous Office deployments. For instance, the new version of Office is language-neutral. This will simplify deploying in a multiple language environment.
[BUILD2] Last, we will look at the new version of Business Desktop Deployment, BDD This new version of BDD is designed to take into account the new features of Office 2007 and Vista.
Slide Transition: Let’s start by talking about the top ten things you will need to deal with when deploying Windows Vista.
Slide Comment:
Additional Information: 8

9. Vista Deployment Impacts: Top 10
Large images >2GB
Users not local admins
OS componentized
SETUP.EXE emphasized
XML-powered configuration
HAL-independent image
Win PE
WIM format
Language-neutral
BDD 2007
Notepad
Unattend.txt
Sysprep.inf
Winbom.ini
Unattend.xml
Slide Title: Vista Deployment Impacts: Top 10
Keywords: Vista, WIM, Deployment, Win PE
Key Message: Several part of the deployment process will change with Windows Vista.
Slide Builds: 10
Slide Script:
Administrators will need to learn a few new procedures as they prepare for Windows Vista deployment.
First, we need get used to very large desktop images.
[BUILD1]
The days of burning off an image to a CD is over -- the images will only fit onto DVDs since the images will typically be 2 gigabytes or more. This shouldn’t affect you too much, other than the additional disk space and network bandwidth requirements. If you are using physical media for your images, you will either need DVD drives on the desktops or you can start using portable USB drives with their rapidly expanding capacity.
You will also need to examine your desktop environment for Windows Vista requirements, especially if you have partitioned your drives. The Windows Vista operating system may no longer fit into the partitions you’ve created for your Windows 2000 or Windows XP desktops.
[BUILD2]
There are a variety of security changes in Windows Vista that you’ll need to be aware of when deploying the new operating system to the desktop. With file system and registry redirection, a user who does not have full administrator rights on the desktop will not be able to write directly to system files or directly change registry settings. Programs that attempt to make these changes will be redirected to a virtual space within the user’s profile. This means that Windows Vista will run applications using standard user rights when the same application may have failed under Windows XP. So with Windows Vista, you have the real ability to run all your users with standard user rights, without local administrator access.
User Account Control protects your users if they are still running with full administrator rights by running with standard user rights and then prompting them whenever an action requires the use of their administrator privileges. For the most part, the term “Power User” is eliminated from Windows Vista with UAC. In Windows XP, the idea was that a user running as a power user had the functionality of an administrator with the system protection benefits of running the user as a standard user. In reality, there were so few features disabled that the power user profile was almost identical to the administrator profile. Windows Vista still offers a user profile called power user, but that should no longer be the profile you use. Keep your focus on implementing the standard user profile, and take advantage of file and registry redirection to maintain the functionality they need.
WIM File Installation
SETUP.EXE
Language-neutral
Any amount of language packs (on Pro and Ultimate)
English Language Pack not required
Process Guidance
Deployment Wizards
Tools
Editable offline
Non-destructive Installation
Windows PE 9

10. Migration Tools Sysprep Setup BCDEdit Ximage
Windows System Image Manager
PEIMG
WDS
PNPUTIL
PKGMGR
OCSetup
BCDEdit
Application Compatibility Toolkit
USMT 3.0
BitLocker
SMS2003 OS Deployment FP
WSUS
System Center Essentials
System Center Configuration Manager 2007
Slide Title: Migration Tools
Keywords: Sysprep, WIM, WDS, BCDEdit, USMT, Vista
Key Message: Become familiar with these migration tools before planning your next OS migration.
Slide Builds: 1
Slide Script:
Here is a quick look at some of the tools that could come into play during your migration. Some of them are not dramatically changed from previous versions, while others are brand-new, offering new functionality. We will cover many of these in greater detail in the rest of this session.
SYSPREP does not change in function, although some of the wording will change.
SETUP replaces the features that you are familiar with from winnt32.
IMAGEX is the tool used for managing and mounting images.
Windows System Image Manager is the tool used for editing the unattend.xml files that now define most of the image deployment.
PEIMG is the command-line utility used for adding and removing optional components from and adding optional drivers to Windows PE.
Windows Deployment Services is the next generation of RIS. As we move to image-based deployment, WDS provides image management capabilities to Remote Installation Services.
PNPUTIL is an online utility used for adding drivers to the image.
PKGMGR is the utility that allows you to add and remove feature components to a Windows Vista installation.
OCSETUP works with PKGMGR.
[BUILD1]
BCDEDIT edits the boot configuration data.
Application Compatibility Toolkit 5.0 is a life cycle management tool for your applications. It assists you in identifying and managing your application portfolio, and reducing the cost and time involved in resolving application compatibility issues. It will help you quickly deploy Windows Vista and Windows XP with Service Pack 2 operating systems without losing functionality of your existing applications.
User State Migration Tool 3.0 captures desktop and application settings, as well as user accounts and user files, and then migrates them to a new Windows installation. USMT can help you improve and simplify your migration process. You can use it for both side-by-side and wipe-and-load migrations. 13

11. Retired Migration Tools
Remote Installation Services (RIS)
Setup Manager and unattend.txt
WINNT.EXE and WINNT32.EXE
MS-DOS, including boot floppies
Windows Deployment Service
Unattend.XML
SETUP.EXE and WIM images
Windows PE
Slide Title: Retired Migration Tools
Keywords: Windows Deployment Services, WIM, DOS, RIS, unattend.txt
Key Message: RIS, unattend.txt, WINNT, and DOS boot disks are not used in the Windows Vista environment.
Slide Builds: 4
Slide Script:
A lot of the deployment tools that are familiar to the administrator are no longer a part of the deployment process.
[BUILD1]
Remote Installation Services (RIS) is replaced by Windows Deployment Services (WDS). However, WDS includes RIS legacy support. Although RIPREP and RISETUP do not work with Windows Vista, you can still use these commands with your pre-existing images. As opposed to RIS, WDS includes native support for Windows PE as a boot operating system. WDS unifies on a single image format, taking advantage of the new WIM file format.
There is also an extensible and better-performing PXE server component. Finally, there is a new client menu for selecting boot operating systems.
[BUILD2]
As we mentioned earlier, we will no longer use Setup Manager and text files manually edited with Notepad to control installations. That phase of a deployment is replaced by Windows System Image Manager and the unattend.xml file.
[BUILD3]
WINNT.EXE and WINNT32.EXE are no longer the installation executables. These have both been replaced by SETUP.exe and the WIM images. In Windows XP, we used SYSOCMGR to install optional components to the computer. It required the inffile.inf and, potentially, an answer file. Due to the component architecture, we will now use OCSETUP with the name of the component that you want to activate. PKGMGR can be used to add components to an offline image. 15

12. demonstration Using the BDD Workbench Demo
Slide Title: Demonstration: Deploying Office System with Windows Vista Using BDD
Keywords: Demonstration
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will create a new operating system package using BDD workbench. We will use the BDD workbench gathering process to collect all of the applications, drivers, and additional packages for a build. Then we will create and deploy the build, making it available for users.
Slide Transition: We have seen how to get the Office files into the right network directory and how to use the Config.xml file.
Slide Comment:
Additional Information:
Using the BDD Workbench
Create a New Operating System Package
Add an Application
Add Language Packs and Drivers 17

13. Applying the Business Desktop Deployment 2007
Agenda
Applying the Business Desktop Deployment 2007
Understanding Windows Vista Deployment Technologies
Deploying 2007 Microsoft Office System
Slide Title: Agenda: Deploying Office 2007
Keywords: Agenda
Key Message: Agenda
Slide Builds: 0
Slide Script:
We have seen a lot of dramatic changes in the world of operating system deployments. Now we will turn our attention to productivity software and deployment of the new Office 2007 system.
Slide Transition: Here are most notable changes in the deployment of Office 2007.
Slide Comment:
Additional Information: 18

14. 2007 Office Deployment Impacts: Top 10
Business Desktop Deployment Solution Accelerator
New user interface
New file format
Local installed source No more Administrative Install points
All products installed from single share
Language-neutral
Apply updates during install
Office Customization Tool
New Migration Tools
Office Resource Kit Process Guidance
BDD 2007
Slide Title: 2007 Office Deployment Impacts: Top 10
Keywords: Office 2007, deployment, LIS, File Format.
Key Message: Be prepared to migrate to a new interface and file format.
Slide Builds: 10
Slide Script:
Let’s look at the top ten changes to Office that will affect your deployment.
[BUILD 1]
First, there is a new user interface. It cannot be altered to look like the old one. Although Office 2007 is quite intuitive, you will need to expect some user training to adapt your user base to the new interface.
In previous releases of Microsoft Office applications, people used a system of menus, toolbars, task panes, and dialog boxes to get their work done. This system worked well when the applications had a limited number of commands. Now that the programs do so much more, the menus-and-toolbars system does not work as well. Too many program features are too hard for many users to find. For this reason, the overriding design goal for the new user interface is to make it easier for people to find and use the full range of features these applications provide. In addition, we wanted to preserve an uncluttered workspace that reduces distraction for users so that they can spend more time and energy focused on their work. With these goals in mind, we developed a results-oriented approach that makes it much easier to produce great results using the 2007 Microsoft Office applications.
The traditional menus and toolbars have been replaced by the Ribbon—a new device that presents commands organized into a set of tabs. The tabs on the Ribbon display the commands that are most relevant for each of the task areas in Microsoft Word 2007, Microsoft PowerPoint 2007, Microsoft Excel 2007, or Microsoft Access For example, Word 2007 has tabs for writing, inserting, page layout, working with references, doing mailings, and reviewing documents. Excel 2007 has a similar set of tabs that make sense for spreadsheet work: creating worksheets, inserting objects like charts and graphics, page layout, working with formulas, managing data, and reviewing. These tabs simplify access to application features because they organize the commands in a way that corresponds directly to the tasks people perform in these applications.
[BUILD 2]
There is a new file format for Office 2007 that provides several new functionalities. It is a fully documented XML schema inside of a compressed zip file. The XML format will open up the accessibility of documents in a heterogeneous environment, be more compact, and easier to search through and sort. This format is dramatically different from the current binary Office file format. Microsoft will be providing tools to help you through the transition. Add-ons will be available for Office XP and 2003 that will allow them to read and write to the new file format.
SETUP.EXE /ADMIN
No longer create transform files
Use Office Customization Tool to create Patch (MSP) files
Installation automatically locates applicable MSP file
Step by step processes
Identify unavailable features
Office Migration Planning Manager
Scans and identifies files to convert
Fully Documented XML
Compressed ZIP file
Slipstream service packs, or…
Install as part of deployment.
Matches Language to OS languages
English not required
No longer requires different install points for each flavor
Setup validates upgrades dynamically
Installation Source copied locally
No more Administrative Install Points (SETUP.EXE /A)
Completely redesigned Ribbon interface
Expect to train users 19

15. demonstration Adding 2007 Office System Source Files Demo
Slide Title: Demonstration: Adding 2007 Office System Source Files
Keywords: Demonstration
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will add the source files from the 2007 Microsoft Office System installation media to BDD.
Slide Transition: The new version of BDD focuses on known pain points for the administrator.
Slide Comment:
Additional Information:
Adding 2007 Office System
Source Files
Load Application Source Files

16. Migration Tools Office File Conversion Tool Office Customization Tool
Patch Folder
Office Customization Tool
Office 2003 and XP can both read and write Office 2007 files with File Converter
Slide Title: Migration Tools
Keywords: Office 2007, Migration Planner, OMPM, File Converters
Key Message: Office Migration Tools will allow Office 2007 to smoothly interoperate in your organization.
Slide Builds: 3
Slide Script:
We already mentioned the new Office Customization Tool. It is started with SETUP.EXE /ADMIN. The resulting MSP files will specify what patches need to be applied with a particular installation. Unless there are multiple MSP files for an Office configuration, the installation will look in the patches folder and automatically select the MSP file that pertains to it. If there are multiple MSPs that apply, install using the /ADMINFILE switch, and define which MS Patch file to use.
[BUILD1]
Office Migration Planning Manager will scan files and identify which ones need to be converted. The Office Migration Planning Manager scans disks and directories for legacy Office files. Once the scan is complete, the XML log files can be compressed into CAB files on the local computer. Use an SMS file collection job to retrieve the CAB or XML files and store them in a central location. With the included batch files “CreateDB” and “ImportScans,” OMPM will create a database to store the scans. You can then use OMPM to create reports of the scans.
[BUILD2]
Office File Conversion Tool is a command-line program used in conjunction with the Office Migration Planning Manager. It is a tool for bulk file conversion. Those files identified by OMPM that require conversion can then be run through a bulk file conversion with the Office File Conversion Tool. The tool invokes Office and converts the files to the new Office 2007 format.
[BUILD3]
Office File Converters can be installed on existing computers running Office 2003 and XP. It is a simple MSI installation that can be deployed using SMS to those computers that still run previous Office versions. The Office File Converters will allow workers using older versions of Office to interoperate with Office 2007 files. For versions prior to Office 2003, a stand-alone file conversion tool will be available.
Slide Transition: Existing Configuration Management tools could also help your Office 2007 deployment.
Slide Comment:
Additional Information:
2007 Microsoft Office System Migration Guidance: Microsoft Office Migration Planning Manager
Custom Configurations
Office 2007
Office XP& 2003
Software Updates
MS Patch File
Office Migration Planning Manager
Office 2007 File Converters 23

17. Office and Configuration Management
Windows Server Update Services
Slide Title: Office and Configuration Management
Keywords: Office 2007, SMS 2003, System Center
Key Message: Configuration Management programs, particularly if they have software deployment functionality, can be a part of your deployment.
Slide Builds: 0
Slide Script:
A lot of the technologies we covered for Vista deployment can also be employed for your Office deployment.
Among these are SMS, Windows Server Update Services, and any third-party configuration management tools that you may already use. When System Center Configuration Manager 2007 becomes available, it will include several features that would apply to an Office 2007 deployment.
System Center Essentials is a management tool that will soon be released in the System Center product line. Microsoft is developing System Center Essentials 2007 (SCE 2007) as a proactive and unified management solution that enables IT professionals in midsize organizations to more efficiently secure, update, monitor, and troubleshoot their IT environments. To help you directly address your pain points, SCE 2007 provides proactive monitoring, troubleshooting, and asset tracking to keep your IT environment secure and up-to-date. It is intended to be a unified solution with a single console for managing your servers, clients, hardware, software, and IT services, and provide efficient execution of complex management tasks, like troubleshooting end-user issues, monitoring, and server and client software deployment.
Slide Transition: In addition to operating systems, the Business Desktop Deployment Solution Accelerator covers the deployment of Office.
Slide Comment:
Additional Information:
Third-Party Tools
SMS 2003
SCCE 2007
System Center Essentials 24

18. Integrating Office 2007 into BDD
Several options:
Install Office on Reference Image
Slide Title: Integrating Office 2007 into BDD.
Keywords: Office 2007, BDD, SMS OSD
Key Message: Choose the Office BDD deployment based on your network resources.
Slide Builds: 3
Slide Script:
If you do deploy Office with an operating system, you have some options as to how to deploy it.
You can install Office on the reference image so that it is a part of the deployed image. No further installation steps will be added to each desktop installation.
[BUILD1]
If you are not going to have Office on all the computers, you can pre-stage Office and cache the LIS without installing and then install later.
[BUILD2]
In a Light Touch deployment, you can install Office from a pre-staged LIS on the image or from a network share. This will work with either an upgrade or a refresh.
[BUILD3]
If you are using the SMS 2003 OSD Feature Pack, you can install an Office System Package as a part of the deployment after the operating system has been installed on the desktop.
All of these practices will ultimately achieve the same installation on the desktop. Select the one that is best suited to your deployment capabilities and requirements.
Slide Transition: Now we can demonstrate Office 2007 and the BDD.
Slide Comment:
Additional Information:
webcast: Windows Vista Deployment Tools and Technologies
Prestage (Place LIS in image)
Light Touch
(LIS in image or network share)
SMS OSD (Automate install after OS deployment) 25

19. BDD 2007 Deployment Scenarios
Light Touch
Deployment without management infrastructure
Manually initiated
Uses network share, Windows Deployment Services, CD/DVD, or USB
Refresh, upgrade, replace, new computer
Complete rewrite from BDD 2.5
Zero Touch
Uses SMS 2003 OS Deployment Feature Pack
Scheduled through Systems Management Server (SMS) and completely automated
Centrally monitored with Microsoft Operations Manager (MOM) 2005 Management Pack
Refresh, replace, new computer
Slide Title: BDD 2007 Deployment Scenarios
Keywords: Light Touch, Zero Touch, BDD, SMS OSD
Key Message: Use the lowest touch deployment that is reasonable in your organization.
Slide Builds: 1
Slide Script:
There are two deployment scenarios to choose from in BDD: Light Touch and Zero Touch. Light Touch is the deployment path of choice if there is no management infrastructure such as SMS in place. A light touch deployment is manually initiated and not centrally controlled. The image can be passed over a network share or locally through physical media. As we saw earlier in this session, WDS replaces RIS as the deployment tool for Light Touch deployment. With WDS comes the ability to refresh or upgrade non-destructively. Light touch in BDD 2007 is a complete rewrite from BDD 2.5.
[BUILD 1]
Zero Touch is not as different from BDD 2.5 than Light Touch. It accounts for Windows Vista and all of the new tools that are available with it. Just as in BDD 2.5, Zero Touch deployment leverages the SMS 2003 OS Deployment Feature Pack, an extension of the capabilities of SMS to enable Zero Touch deployment of operating systems. The deployment can be completely automated. In many scenarios, it is unnecessary for a technician to visit the desktop at all. Central monitoring of the deployment is managed through Microsoft Operations Manager.
Slide Transition: Now we can look at the new BDD workbench.
Slide Comment:
Additional Information: 26

20. demonstration Deploying 2007 Office System with
Windows Vista using BDD
Customize the Application Installation
Use the Office Customization Tool
Install Microsoft Office
Slide Title: Demonstration: Deploying 2007 Office System with Windows Vista using BDD
Keywords: Demonstration
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will use BDD 2007 to customize and deploy 2007 Office System. We will import the source into BDD, then customize settings by editing config.xml and running the Office Customization Tool. Finally, we will run the installation on a workstation.
Slide Transition: The imaging process, the act of creating your base image, has changed slightly from BDD 2.5.
Slide Comment:
Additional Information: 27

21. demonstration Deploying 2007 Office System with SMS 2003 Demo
Slide Title: Demonstration: Deploying 2007 Office System with SMS 2003
Keywords: Demonstration
Key Message: Demonstration
Slide Builds: 0
Slide Script:
In this demonstration, we will use SMS 2003 to deploy the customized 2007 Office System application.
Slide Transition: In comparison to the Light Touch process, the Zero Touch process adds SMS and the OS Deployment Feature Pack to the deployment.
Slide Comment:
Additional Information:
Deploying 2007 Office System
with SMS 2003
Create a Package for Microsoft Office
Create an Advertisement 28

22. Configuration Manager
BDD Zero Touch Design
90% similarity to light
touch deployment
Easy migration path
from current BDD 2.5
Zero Touch
Installation and SMS
2003 OSD RTM
Easy migration path to
System Center
Configuration Manager
(SCCM) 2007
Slide Title: BDD Zero Touch Design
Keywords: BDD 2007, Zero Touch Deployment, Drivers
Key Message: Zero Touch has changed slightly in BDD 2007.
Slide Builds: 4
Slide Script:
As a result, there is no wizard for deployment as there is in the Light Touch process. That is replaced by the SMS Operating System Deployment pack functionality. Applications and operating system images are delivered as SMS packages. These installations are kicked off from the server as controlled by an administrator.
[BUILD1]
The Zero Touch process is not dramatically changed from BDD 2.5. As we mentioned earlier, it is much more similar to the light touch process in BDD 2007, as the Light Touch process has adopted much of the zero touch toolset. This will benefit technicians who move between the two processes. If you become familiar with one of the two processes, you will be able to adopt the other much more quickly than in BDD 2.5.
[BUILD2]
If you have already implemented Business Desktop Deployment version 2.5, the similarities mean that it is an easy migration path to the zero touch migration process in BDD 2007.
[BUILD3]
It is also designed to take into account the future release of System Center Configuration Manager 2007, the upcoming version of SMS. By employing BDD 2007 now for zero touch deployment, it will be easier to add the features of SCCM 2007 when it is released.
[BUILD4]
The BDD 2007 Zero Touch deployment does have several enhancements over BDD 2.5. For instance, the SCCM Task sequencer is available now for all zero touch deployments. The new deployment process includes the capability to perform a full computer backup during the migration process as an added protection against lost data or problem migrations.
BDD 2007 also uses a more granular driver management process. In BDD 2.5, drivers were installed by selecting a directory for each computer make and model. Then the entire directory was downloaded. Now the imaged computer will access the driver store and select drivers based on its own Plug and Play IDs. This will take into account the more heterogeneous desktop environment where computers have been customized. It will reduce the amount of problem computers that require personal attention during the migration.
Slide Transition: Let’s summarize this session on Vista and Office deployment.
Slide Comment:
Additional Information:
Enhanced capabilities:
SCCM 2007 task sequencer integration (even with SMS 2003)
Full computer backup
More granular driver injection 29

23. Windows Vista deployment tools
Session Summary
Windows Vista deployment tools
Office 2007 deployment techniques
Business Desktop Deployment 2007
Slide Title: Summary
Keywords:
Key Message: Summary
Slide Builds: 2
Slide Script:
This session covered methods and practices to deploy Windows Vista and Office We noted the new WIM image format and the tools, such as Ximage and Windows Deployment Services, that are designed to work with a new deployment plan that will be easier and more cost-effective. We talked about how deployment will change for Vista.
[BUILD1]
Office 2007 also includes some significant changes that will affect how you deploy it. For instance, the Local Installation Source, or LIS, is now the single core origin for Office installation.
[BUILD2]
Finally, we examined the newest version of Business Desktop Deployment 2007 Solution Accelerator. The newest version includes wizards and applications that will guide you through the deployment of not only operating systems, but also of Microsoft Office.
Slide Transition: To get more information on the products and technologies we have covered today, we have some online resources available that can help.
Slide Comment:
Additional Information:

24. www.microsoft.com/technet/dsk-03 For More Information
Visit TechNet at:
Visit the following site for additional information:
Slide Title: More Information
Keywords: More Information
Key Message: More Information
Slide Builds: 0
Slide Script:
For the most comprehensive technical information on Microsoft products, visit the TechNet Web site at
You can also visit for more information on books, courses, certifications, and other community resources that relate directly to this particular session.
Slide Transition: Several other resources are available from Microsoft.
Slide Comment:
Additional Information: