1. Windows Vista and Office 2007 Deployment 101 - Best Practices, Tools and Tips
Rodrigo Mier y Concha
Windows Client Technology Specialist
Microsoft Canada Co.

2. Top Deployment Challenges
Overall Cost and Complexity
Application Compatibility
Hardware Compatibility
User State Migration
On-going Maintenance
Tip of the Day!
Stay for the Optimized Desktop session (next one) to find out about the Partners Go to Market Opportunities to win Bigger Deals with these technologies!
Key Messages
Customer challenges and deployment blockers
Presenter Script
We conducted a survey of several of our customers, partners, independent software vendors (ISVs), and our own account teams. This is a sampling result from that survey, showing the issues that came through loud and clear.
Major challenges to deployment include:
The first is application compatibility. This is consistently the biggest issue that we hear across the board. “I have these old applications, and I want to migrate them and make sure that they work on the new operating environment. I also want to move settings and user-specific information across without losing anything.” This is a huge challenge with line-of-business (LOB) applications, particularly those that do not have source code.
Next is the cost and complexity of the deployment. It costs a lot, causes disruption, and is error prone. There are too many moving parts and it requires too many people with specialized skills.
Many customers feel that they do not have the right infrastructure, people, and tools needed to do this effectively. They have to pick and choose tools and build custom solutions.
And, finally, there is a lack of good best practices and implementation guides to help customers through the process. Customers are looking for something that is consistent, repeatable, and scalable.
We then took these challenges and boiled them down to specific things that we could do in Windows Vista to address them. Based on this, we came up with a list of goals for Windows Vista deployment.
Presenter Guidance
Ask the customer how they are addressing desktop deployments today or how their last desktop deployment project was accomplished:
How do they or did they address application compatibility concerns?
How do they or did they reduce deployment costs and timelines, or do they rely on a completely manual process (also known as a “heroic deployment”)?
Do they include back-end and infrastructure upgrades as a prerequisite when scoping desktop deployments?
What is their current technology level: do they have the back end and infrastructure to enable an automated deployment solution?
Do they have a standardized and documented deployment process?
If so, how does it work? (You can usually glean the efficiency of the process by comments made by the participants.)
How automated is their environment?
Do they currently package applications for mass deployments?
Do they have a management tool in place (for example, Microsoft Systems Management Server [SMS], Tivoli)? If so, are they using it?
Do they have scripts to assist with automation?
Additional Presenter Information
This leads directly into the next several slides, which discuss automation and standardization.

3. 12/7/ :08 PM
Infrastructure Optimization and Windows Vista Enabled Best Practices can significantly reduce PC deployment costs
Basic
Standardized
Rationalized
IT Labor
$1,320 per PC
$580 per PC
$230 per PC
Desktop standardization = $110 per PC
Centrally managed PC config. = $190 per PC
Best Practices
Basic Standardized Rationalized
IT costs (IT labor costs per PC per year, excluding software and hardware costs)
$1,320 $580 $230
Service levels (number of service desk calls per PC
per year)
Business agility (weeks to deploy new application)
caption with what numbers represent
how much you can save per pc per year
qualities o the columns
then the best paractices
Comprehensive PC security = $130 per PC
“For organizations with a diverse mix of hardware and a "thin" image strategy, Windows Vista will make it possible for them to attain a best practice of using a single image.“
– Al Gillen, Research VP, IDC
“UAC will make it possible for users to run applications that require administrative rights while operating under Standard User rights. Not having this ability in Windows XP makes implementing this best practice difficult, and the often-required workarounds increase complexity – Al Gillen, Research VP, IDC
Source: Optimizing Infrastructure, IDC 2006, Sponsored by Microsoft 3
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

4. Agenda Deployment Lifecycle overview Step 1 – Planning
Step 2 – Building
Step 3 – Implementation
Next Steps

5. Enabling The Deployment Cycle
12/7/ :08 PM
Enabling The Deployment Cycle
The Microsoft Deployment Toolkit formerly BDD
Consistent, repeatable methodology and best practices
Using new Windows Vista and 2007 Office deployment tools
THE recommended methodology for desktop deployments
Combined learning from over 5 million desktops deployed!
The technology solution behind DDPS!
Planning
Building
Implementation
Application inventory
Application analysis/testing
Application compatibility mitigation
Migration testing
Migration scripts
Build desktop image from modules
Customize image
Add drivers, languages and applications
Capture image
Prepare for rollout
Install image to desktops
Migration/upgrade
Remote deployments
Tools
Image Based Setup
ImageX
System Image Manager
Sysprep
Tools
Image Based Setup
WDS
SMS 2003 / SCCM 2007
Microsoft Deployment Toolkit
Tools
ACT
USMT
WVHA
VA2.0
OMPM
Windows PE
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

6. Step 1 - Planning Changes in Windows Vista to consider
Microsoft Hardware Assessment
Application Compatibility Toolkit
Microsoft SoftGrid Application Virtualization
Volume Activation 2.0

7. Examples of Changes in Windows Vista Requiring Attention:
User Account Control
Application with platform specific drivers
Registry changes
Firewall
Internet Explorer 7 - Lower Rights IE (LoRIE)
Windows Vista Hardware requirements MHz processor, 512 MB of RAM, 20 GB hard drive with 15 GB of free space
Presenter Script
If we look at applications in a general sense, applications that are high on the technical stack (furthest from the core os functions) have fewer incompatibilities and are the easiest to resolve for Windows Vista compatibility. Applications that are low on the technical stack (closest to the core os functions) have a larger number of incompatibilities and require the more extensive changes for Windows Vista compatibility.
Unlike Windows XP, The Risk Areas for Windows Vista Application Compatibility are in very focused areas and tends to fall into 3 categories. Things that tend to change between releases, Changes required for greater security, and OS Innovation.
Things that change between releases, such as Version checking, has to be addressed with every new release of an operating system. These are legitimate checks to ensure applications are running on the operating system they were designed to run on. These are also the easiest areas to change as these are simple corrections in an application or can be fixed with an operating system shim.
Security Enhancements are now an ongoing necessity of business platforms. With Windows Vista, we have put some great new security features into the operating system. In some applications this may expose the weakness in applications.
Applications that wrote to protected areas of the operating system and persisted information across sessions. Windows Resource Protection features automatically re-directs writes to a virtualized folder to allow applications to continue to run, however, if applications persists data in these locations, that data will no longer be available.
When implementing the more restrictive user account control with applications, If those applications perform administrative task, they will need to be modified to run in an elevated mode.
And Internet Explorer now runs in a Protected mode with lesser rights than in Windows XP. This may cause some web applications to fail when trying to perform administrative level functions
We are also continually working to innovate our operating systems.
In 64-Bit Windows Vista, you should know that
16-bit apps will not run on 64-bit platform
32-bit applications using 32-bit drivers will not function properly Network scanning, firewall, anti-virus apps
Commonly used unpublished APIs and internal data structures
And we have create newer, more secure implementations of our firewall platform which will ensure greater compatibility in the future, however, will affect all Anti Virus and Firewall Applications currently available for Windows XP

8. Compatibility Solutions and Tools
Compatibility tools
Windows Vista Hardware Upgrade Advisor and Windows Vista Hardware Assessment Solution Accelerator
Application Compatibility Toolkit
Office Migration Planning Manager
Bridging technologies to address difficult application compatibility issues
Virtual PC 2007
Terminal Services for hosting applications
Microsoft Softgrid
Presenter Script
There are additional tools to assist with application compatibility for Windows Vista.
The Program Compatibility Wizard walks the customer through setting the compatibility mode for an application
The Program Compatibility Assistant automatically detects when an application needs to run in a compatibility mode and prompts the user to set this up automatically.
The Application Compatibility Toolkit assists Enterprises in identifying their Application Portfolio and helps them manage the application compatibility mitigation process.
Even with these Application Compatibility Tools, there will be some applications that will not run on Windows Vista and they may be applications you are unable to migrate (because of ISV support, lack of internal resources, etc.).
Bridging Technologies can assist with these situations allowing you to temporarily run legacy applications without interrupting your deployment of Windows Vista.
Virtual PC is the Microsoft client-based, virtual machine solution, providing you with an OS migration safety net and a tool for more rapidly deploying Windows Vista. Virtual PC makes it possible for you to simultaneously run multiple Operating Systems on a single PC.
VPC Express - Microsoft's Virtual PC product available to Software Assurance and Ultimate customers
Terminal Services - lets you deliver Windows-based applications, or the Windows desktop itself, to virtually any computing device on your network. Windows Vista clients can connect to these application hosting environments through Remote Desktop to access legacy applications.
Virtual Server/Virtual PC - With a Virtual Server/Virtual PC environment, you can host legacy applications and allow remote connectivity from end users needing access to those applications. In conjunction with Windows Server 2003, Virtual Server 2005 R2 provides a virtualization platform that runs most major x86 operating systems in a guest environment, and is supported by Microsoft as a host for Windows Server operating systems and Windows Server System applications
Microsoft Softgrid

9. Microsoft SoftGrid Application Virtualization Dynamically streaming software as a centrally managed service
Applications are virtualized per instance:
Files (incl System Files)
Registry
Fonts
.ini
COM/DCOM objects
Services
Name Spaces
Applications do not get installed or alter the operating system
Yet Tasks process locally on the host computer

10. DEMO Application Compatibility Toolkit
Instructor Notes:
NOTES: The following notes can be used to support the ACT demo. Its recommended to install ACT locally and capture an ACT report of the local PC prior to the demo. It’s also recommended to guide the audience trough the steps of creating a deploying an ACT agent, and show some reports created by ACT.
ACT 5.0 download
Application Compatibility Toolkit
Microsoft SoftGrid Application Virtualization

11. Microsoft SoftGrid Application Virtualization Dynamically streaming software as a centrally managed service
Life without traditional
Software Installation
Deliver applications to users on-demand –in seconds, to any licensed machine
Reduce user downtime and admin preparation time associated with software installation
Enforce authorization of machines to applications – permissions are centralized, applications are sandboxed
Benefits to IT
Accelerate desktop deployment and take control of the desktop
Minimize application conflicts through application isolation at streaming server
Minimize significant application compatibility testing and scripting, multi-platform packaging, or significant regression testing
Run real time usage reports
Enable device roaming
Enterprises have experienced over 80% reduction in application management costs, 30% reduction in help desk costs, and enables a four-fold increase in user up-time**
What would life be like without traditional software installation.
Today you have to package applications, Make sure they don’t brake other applications, You have to patch them and you have to deploy them and sometime remove them from the system. That is a tedious process.
Softgrid transforms applications into virtual application services that are now available on demand over the network.
You can reduce downtime since now the application is virtualice
You can also enforce authorization and create policies and apply permissions to deploy and distribute those applications.
**Return on Virtualization: Calculating the Economic Impact of the Softricity Desktop Report

12. Activation Options BIOS-bound Pre-install Online Phone Retail OEM
12/7/ :08 PM
Activation Options
BIOS-bound Pre-install
Online
Phone
Retail
OEM
Volume
Multiple Activation Key (MAK)
Key Management Service (KMS)

13. Multiple Activation Key - MAK
One time activation against Microsoft
Two methods of activation using a MAK:
MAK Independent Activation: Each desktop individually connects and activates with Microsoft (online or telephone)
MAK Proxy Activation: One centralized activation request on behalf of multiple desktops with one connection to Microsoft
Reactivation may be required if there is significant change in the underlying hardware
Has an associated upper limit, depending on the license agreement, and can be easily refilled

14. Key Management Service - KMS
Activate using customer hosted service and NOT with Microsoft
Systems must re-activate by connecting to KMS host at least every 180 days
Requires 25+ for Windows Vista
Default activation option for all volume editions of Windows Vista and Windows Server “Longhorn”
Requires no user interaction
Currently available on Windows Vista and Longhorn Server, can run on Windows Server 2003

15. Step 2 - Building Microsoft Deployment Toolkit Windows Imaging Format
ImageX
Windows System Image Manager

16. ImageX & Windows Imaging Format
Building
Windows Imaging
File-based format – hardware independent
Multiple images in one WIM file
Single instanced and compressed – small size
Spanned media support
Modularization
Add/remove optional components – drivers, patches
Language independence
Advantages
Single instance of duplicate files (SHA-1 hashing)
Files compressed through LZX
WIMs can be split and applied from parts
Build desktop image from modules
Customize image
Add drivers, languages and applications
Capture image
Prepare for rollout
Key Messages
ImageX is a command-line tool to capture an image, whereas System Image Manager [SC1] is a graphical user interface (GUI) tool to customize the image.
Presenter Script
Imaging and modularization are two very important innovations in Windows deployment, and the desktop engineering tools correspond to these innovations.
On the imaging side, ImageX works with WIM and WIM files. It is the utility of choice to create management files. With ImageX you can mount and edit WIM files offline and add WIM files and packages into it directly. You can also capture the desktop volume. ImageX desktop versions are always version agnostic, and you can use ImageX to capture Windows XP or Windows 2000 images. It’s command line only, at this point, but it’s a great tool because you can script ImageX in any way that you want and automate all of its capabilities.
On the modularization side is System Image Manager, which is the tool of choice to work with modules. You can use it to add optional components such as languages, service packs, and drivers. You can also use it to create an unattend file in XML, which offers significant benefits, particularly in terms of automating these processes. System Image Manager is a graphical user interface (GUI)–based tool, but at the same time it’s fully scriptable.
With ImageX and System Image Manager, you can script and automate a lot of the capabilities right from the command line. By using all of these tools—WIM, ImageX, and System Image Manager—you have the benefits of being able to create a single worldwide binary, serve the images offline, and reduce the number of images.
Presenter Guidance
Additional Presenter Information
 [SC1]Please confirm
Tools
Vista ImageX
System Image Manager

17. DEMO Deployment Workbench System Image Manager ImageX Key Messages
BDD Windows Vista provides a tool (BDD Workbench) that assists in the creation and capture of a master image.
Presenter Script
The process for creating the golden image for Windows Vista deployments using BDD is very similar to earlier versions. The back-end pieces must be in place before you begin, including a file server to house the source files and the new components offered by BDD Windows Vista.
BDD Workbench is the replacement for BDD 2.5 Config.hta and is a Microsoft Management Console (MMC) 3.0 snap-in. In the BDD Workbench, you’ll be able to configure specific settings in Unattend.xml, the task sequencer, etc.
The SMS v4 task sequencer is included in BDD Windows Vista—no additional SMS license is needed. The tool will be available after the SMS v4 Beta 1 release in the April version of BDD Windows Vista.
BDD Requirements
Windows Vista (windows 2003 server), WAIK tools, Vista DVD
BDD download. fd0e ca6- 1aad6fc54741&displaylang=en&Hash=yvzJoS7HiVd78%2b4LNrpUJrxtIIe H07Yrbb9OI5R0gFrn4Cebya6KHFBpW8R%2btshfbO9UWt988JMzcf%2fU8 3h5Ng%3d%3d
BDD quick start.
Deployment Workbench
System Image Manager
ImageX

18. Step 3 – Implementation Systems Management Server 2003
Systems Center Configuration Manager 2007
Windows Deployment Services
Microsoft Deployment Toolkit
Lite Touch and Zero Touch Installations
Key Messages
There are a variety of tools to help deploy your master image of Windows Vista.
Presenter Script
There are a variety of tools to support the deployment of your Windows Vista master image:
SMS 2003 will support Windows Vista with an update to the OSD Feature Pack.
WDS is a replacement for RIS and provides Pre-boot Execution Environment (PXE) boot services.
BDD will be updated to support Windows Vista for Lite Touch and Zero Touch Installations.
In SMS v4 there will be a consistent mechanism for operating system deployment of clients and servers.
Presenter Guidance
Additional Presenter Information

19. Microsoft Deployment Toolkit
Lite Touch
Zero Touch with Configuration Manager 2007 or SMS 2003
No management infrastructure
Manually initiated
Wizard driven
Windows XP, Windows Vista, Windows Server 2003, Windows Server 2008
Central scheduling
Central monitoring
Windows XP, Windows Vista, Windows Server 2003, Windows Server 2008
Extensions and enhancements
Leverages core deployment tools:
Windows PE
Windows Deployment Services
ImageX
Provides process and tool guidance

20. Implementation Windows Deployment Services
Delivers “in-box” OS provisioning solution
Leverages new deployment technology
Coexistence with RIS
Delivers customizable platform components
Remote boot capability for WinPE
Plug-in model for Pre-boot Execution Environment (PXE)
Image store and communication protocol
Unifies on single image format
Continues to deploy RIS images from WDS servers
Key Messages
WDS is a replacement for RIS and provides PXE boot services.
Presenter Script
WDS replaces RIS, which cannot deploy Windows Vista. WDS will be available for the Microsoft Windows Server™ 2003 operating system from the Windows Vista client RTM.
Features of WDS include:[SC1] 
Can install Windows Vista, Windows XP, Windows Server 2003, and Windows 2000 images
Uses WinPE as the boot environment on the target PC
WinPE can be customized
WinPE is deployed as a compressed WIM image with RAM disk boot support
Provides image selection through a WinPE-based WDS client
Provides native support for WIM images
Includes new Microsoft PXE server architecture
Provider plug-ins to augment core networking functionality can send a PXE request to another deployment tool, for example SMS
Deploys WinPE to PXE booting client computer
Replaces the Client Installation Wizard
Compressed WIM image with RAM disk boot support (~80 megabytes [MB])
Support for customized versions of WinPE for Windows Server “Longhorn”
Boot support for 32­-bit and 64-bit versions
Supports new computer (bare metal) deployment/computer re-provisioning
Native support for WIM images with a migration path from RIS format
Deploys Windows Vista, Windows XP, Windows Server 2003, and Windows 2000 images
WinPE-based WDS client allows image selection and disk configuration
WDS client can run in fully unattended fashion
Integrated with Active Directory
WDS is platform technology that provides extensibility:
Uses “Provider” logic: plug-ins to augment core networking functionality
WDS PXE service can now handle more than 1,600 requests per second, Boot Information Negotiation Layer (BINL) 700 sustained[SC2] 
Communication protocol for image enumeration
Features of the WDS server include:
Hosted in the SVCHOST.EXE process
Core PXE server allows a network boot of client machines
Uses an image store and communication protocol, which allows the WDS client to obtain UNATTEND.XML file and image information
Trivial File Transfer Protocol Daemon (TFTPD):[SC3] 
Transport protocol used during PXE boot and for WinPE download
Robust management of WDS environment
WIM file spanning single-instance storage
Prerequisites for WDS:
Active Directory
WDS server must be either a member of an Active Directory domain or a domain controller for an Active Directory domain.
Active Directory domain and forest versions are irrelevant.
Dynamic Host Configuration Protocol (DHCP)
WDS requires a working DHCP server with an active scope on the network.
Domain Naming System (DNS)
WDS requires a working DNS server on the network.
Installation media
WDS requires a Windows Automated Installation Kit (AIK) DVD.
Windows NT File System (NTFS) partition on the WDS server
WDS requires an NTFS partition for the image store.
Windows Server 2003 SP1 with RIS installed
RIS must be installed for the update package to run.
Accounts
The installation account must be a member of a local Administrators group in the WDS server.
The user booting PXE client must be a member of the Domain Users group.
Presenter Guidance
Additional Presenter Information
 [SC1]
Also, please confirm that there is sufficient information here for usability by the presenter. This does not map directly to the content on the slide (it is far more detailed and specific, without providing as much general information).
 [SC2]Sense of this last clause? Should this say “versus the 700 that could be sustained by the Boot Information Negotiation Layer (BINL) of RIS?
 [SC3]Please convert this to an introductory sentence
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

21. Zero Touch Installation Workflow SMS 2003 OSD Update
12/7/ :08 PM
Zero Touch Installation Workflow SMS 2003 OSD Update
SMS inventory is used to create a collection. Computers are targeted
for refresh.
Target Machine
Compressed WIM OS image is downloaded and installed 1 5
Image is personalized and boots to full OS with SMS agent 2
Client receives advertisement for OS refresh, saves user state 6
SMS Client Agent Pre-OS
SMS delivers bootable Windows PE image using WIM to existing OS partition 3 7
SMS Advanced Client agent starts up
Boot files are modified, reboots to Windows PE on hard disk, then cleans disk
SMS delivers role based applications and post-OS configuration. User state is restored. 8 4
Bootable
Windows PE
Hard
Disk OS
SMS Server
MOM
Windows PE Ima
Application Delivery
OS Image Delivery
SMS Advanced Client Agent
Windows-Present
Logs all activity
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

22. Deployment Technologies
Why are the deployment technologies important to me?
Lowering your costs
Providing best practices
Benefits in scalability, repeatability
Light and zero touch deployments
Preparing for Windows Server 2008
Preparing for lifecycle management
Significantly better than what we delivered during Windows XP and Windows Server 2003

23. Tips from the Field Start small – build a lab
Deploy Windows Vista in your organization
Demonstrate the business value – load on a BDM/TDM’s PC
Look for the easy wins – mobile workers, PC refresh, ISV applications
Touch the desktop once -> Vista + Office
Use the tools and guidance

24. Partner Resources Microsoft Partner Program Competency
Desktop Deployment Partner Services

25. Windows Desktop Deployment – New Specialization within Advanced Infrastructure Competency
Demonstrates proven skills and deep expertise to Microsoft customers and increases visibility to the marketplace
Provides eligibility to achieve a Advanced Infrastructure Solutions competency
Forms knowledge base for partner readiness programs for Windows Vista and future versions of Windows
Customer references, individual certifications, and deployments of Windows Vista are all part of specialization requirements
More information at:

26. Desktop Deployment Planning Services (DDPS)
12/7/ :08 PM
Desktop Deployment Planning Services (DDPS)
What is DDPS?
Software Assurance (SA) benefit for eligible customers
4-5 day in-depth technical and hands-on training in the latest deployment offerings from Microsoft – BDD expertise!
Microsoft pays DDPS certified partners to deliver customized deployment plans to eligible customers
Opens the door with existing and new customers to have a Core IO conversation while setting the stage for ongoing revenue opportunities
8 US DDPS certified Partners have earned an average of $93,000 in additional revenue from completed DDPS engagements.
Visit or contact for more information
© 2006 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY 27

27. Summary
There is a significant opportunity around Windows Vista deployment
Deploying Windows and Office are now easier than ever
Build relationships, value added services around security, collaboration
Tools, solutions and best practices make it easier for you to provide the service
Take advantage of the programs and certifications
Start application and hardware testing today
Stay for the next session about Partner Business Opportunities with these technologies!