1. OEM Preinstallation of Windows XP Service Pack 2
John Straumann
Partner Technology Specialist
Microsoft Canada

2. Agenda SP 2 Value for System Builders
Introduction to the OEM Preinstallation Kit
Overview of the Preinstallation Process
How to Obtain the OEM Preinstallation Kit and Windows XP Service Pack 2
Installing the OPK Tools
How To Integrate Windows XP Service Pack 2 into an existing OPK Tools Share
Running the System Preparation Tool
What’s New in OEM Preinstallation with Windows XP Service Pack 2?
This is just a quick overview of what the next 1.5 hours or so will include. We will introduce the OPK and then give an overview of the process. Then, we’ll walk through actually installing the tools and build a configuration set. You can then do a preinstallation or just do a demo of the Windows Preinstallation Environment.
You’ll notice that much of the information on the subsequent slides is similar to Windows XP preinstallation! Make this point whenever possible that if a SB or Reseller is currently using the OPK Tools to preinstall Windows XP, the move to now preinstall Server 2003 is a very easy one. If he/she is not shipping XP or not using the Tools to do so, the info contained herein will be of much value for preinstalling both versions of the Operating System.

3. SP2 Value for System Builders
The release of SP2 creates an opportunity for you to conduct security audits with your customs
Upgrade existing systems to SP2
Upgrade older PCs to new ones with Windows XP SP2
Upgrade small business networks to Windows Small Business Server 2003 with Windows Update Services installed
Windows Security Center dramatically underlines the need for AV software for your customers
This is a revenue opportunity for you
When your customers have SP2, they’re less likely to require support
Can increase your customer satisfaction
Increase your credibility as reliable source of security solutions
Gives them the opportunity to get in front of customers again, sell other servers or software

4. OEM Preinstallation Kit Benefits
Flexible methodology
Enables you to choose compact disc-based, network-based, or peer-to-peer preinstallation methods
Customization
Enables you to add shortcuts and branding information to the operating system
Hardware flexibility
Enables you to preinstall drivers for devices that do not have built-in support in the operating system
Application preinstallation
Allows you to preinstall software programs during the installation of Windows XP.
Audit capability
Enables you to test preinstalled computers without interrupting the preinstallation process
Easy to use and
saves build time
Wizard-like interface makes the OPK easy to setup and use and will save time compared to manual installations and adding apps/drivers.
This slide should be familiar…the same one is seen in nearly all OPK Presentations.

5. Common OEM Preinstallation Kit Terms
Definition
Technician computer
The computer on which you install the OEM Setup Manager tool
Configuration Set
A set of instructions and answer files that contains the preinstallation configuration settings
Destination Computer
The computer on which you preinstall Windows XP using the Windows Preinstallation Environment
Image
A “picture” or an exact duplicate of the original file and folder structure of a preinstalled Windows XP machine
Master computer
The computer that contains a master installation
Master installation
A customized installation of Windows XP
Preinstallation
The process of loading Windows XP onto new computers
End User
The recipient of the computer that is manufactured by the OEM System Builder
These terms are organized alphabetically…it may be more appropriate to change them around. Feel free to do so if you desire.
The terms will become clearer as the presentation continues, especially when a System Builder sees the “Overview of the Preinstallation Process” slide two slides from now.
Imaging from a master computer can be a lot faster than using the OPK on a “per machine” basis. “HAL” must be the same. Sysprep BMSD build mass storage drivers

6. Overview of the Preinstallation Process
Install OPK Tools
Stage or prepare applications
Build configuration set
Copy Winbom.ini to floppy disk, custom CD or USB flash
Technician Computer
Start the computer with the Windows XP OPK CD
Insert Winbom.ini floppy disk at startup
Master Computer
Reseal the computer, or run Audit or Factory mode to modify and then reseal
Tools: 2000, XP Home (only allows 5 connections) or Pro, 2003
Winbom: floppy, root of HD (if already partitioned), USB, CD (custom burn). Must be in root
Build an image of the installation and store it on the technician computer, if desired
Destination
Computers
Deploy image from the technician computer onto the destination computer(s)

7. How do System Builders Receive the OPK?
The OPK is included FREE with each multi-pack (3-pack or 30-pack) of Windows XP Service Pack 2 that is purchased from System Builder Channel Distributors
The OPK is not made available for download
Authorized Distributors for every Region can be found by visiting the System Builder website:
On OEM site if they sign the redistribution agreement and then they can do whatever they want to do after downloading the SP 2 files.
Can use the OPK SP1 CD to install SP 2.

8. How Do System Builders Receive Windows XP Service Pack 2?
Windows XP Service Pack 2 Integrated CD is available when purchasing System Builder software from an Authorized Distributor
Service Pack 2 standalone executable will be available for download in all languages from MS OEM System Builder website

9. Installing the OPK Tools
Here we will autorun the WinPE CD and install the OPKTools.
NOTE: This graphic no longer shows XP so that is how it’s distinguishable from the initial version of the OPK installer from XP RTM.

10. How To Integrate SP2 Into An Existing Windows OPKTools Share – Step by Step
Obtain full XPSP2.EXE Standalone update file
Create folder on C:\ called XPPro for Windows XP Professional and XPHome for XP Home
Copy entire contents of Windows XP Pro or Home CD into these folders
Open a command prompt and type
XPSP2.EXE /integrate:C:\XPPro
When Service Pack 2 has been completely integrated you will see “Integrated install has completed successfully.”
Now, go to Tools – Manage Products in the Setup Manager tool
Click to Add in New Product files by navigating to C:\XPPro and C:\XPHome
The purpose of this is to allow SBs to begin shipping SP 2 without waiting the 4+ weeks to get the full XP SP 2 CDs from distribution.
At the end of this process, the SBs would have to send out XP SP1 CDs to customers, however they could send out an SP 2 standalone

11. Running the OEM Setup Manager Tool
Start  Windows Preinstallation Kit  Setup Manager
Add Product files in to be deployed
Same Setup Manager tool can deploy Windows XP, Windows Server 2003 in all languages and skus
OEM Setup Manager

12. OEM Preinstallation from CD Using The Corporate Setup Manager
Do System Builders have to use Network-based preinstallation? NO!!!
System Builders can perform preinstallations from a CD using an answer file called WINNT.SIF
Should run the Corporate Version of the Setup Manager tool extracted from DEPLOY.CAB found on the Windows XP Operating System CD.
Winnt.sif contains all the answers that would normally have to be provided by an installer. HAS to go on floppy, doesn’t support USB at all!

13. What’s New In OEM Preinstallation with Service Pack 2?

14. Changes to Unattend.txt Answer File
[IEHardening] Section is NEW!
Entries have been added to the following additional sections:
[Components] Section
DisableSecurityCenterAlerts: Specifies whether to disable alerts from Security Center.
IEHardenAdmin: Applies the Enhanced Security Configuration to members of the Administrators and Power Users groups.
IEHardenUser: Applies the Enhanced Security Configuration to members of the Restricted Users and Guests groups.
WbemCrrl: Specifies whether to install the Windows Management Instrumentation (WMI) event correlation component.
WbemFwrd: Specifies whether to install the Windows Management Instrumentation (WMI) event forwarding components.
WbemMSI: Specifies whether to install the Windows Management Instrumentation (WMI) Windows installer provider.
The next 3 slides are aimed more at enterprise IT departments than SBs…
Your FYI - The unattend.txt is a script used to help OEMs build images for preinstall and for enterprise customers to automate deployments and customizations
Point of the slide: Listed are some of the key additions to the unattend.txt. These changes are designed for enterprise customers, but apply to OEMs as OEMs can custom build images for enterprise customers…so these may apply in that situation. Just mention the changes are there and OEMs should be aware and move on to the next slide

15. Changes to Unattend.txt (Continued)
[Data] Section
AutomaticUpdates: Specifies whether to enable Automatic Updates.
[GuiUnattended] Section
EMSSkipUnattendProcessing: Prevents Windows Setup from processing Unattend.txt or Sysprep.inf during an unattended installation to an EMS server.
[Unattended] Section
DUStopOnError: Specifies whether to stop the Windows Update process when an error is detected.

16. Changes to Sysprep.inf Answer File
[IEHardening] section (New!)
Entries have been added to the following section:
[GuiUnattended] section
EMSSkipUnattendProcessing: Prevents Windows Setup from processing Unattend.txt or Sysprep.inf during an unattended installation to an EMS server.
Your FYI Sysprep is used to seal the OS image in a build process.
Same as with the other slide, same scenario…move on to next slide

17. Goal and Strategy for Interim WinPE
Goal: Develop a version of WinPE that provides additional support requested by partners to allow deployment within factories thus reducing the cost and time factors.
Strategy: Deliver an interim release version of WinPE to allow testing and adoption within the factory prior to Longhorn OS and OPK releases

18. Interim Windows Preinstallation Environment
Windows PE is a minimal Windows system that provides limited services based on the Windows XP Professional and the Windows Server™ 2003 kernels
Provides the minimal set of features required to run Windows Setup, access and install operating systems from the network, script basic repetitive tasks, and validate hardware
Includes features and capabilities that eliminate dependencies on MS-DOS-based tools (such as test and diagnostics tools), and provides an infrastructure within Windows PE to install images and perform required tasks in the factory
Past, Win PE had 2 reasons to exist:
Get access to network
Gives us ability to read/write NTFS

19. Windows Preinstallation Environment
Windows XP Pro
WinPE
Complete OS Solution
Customizable Boot
Environment
Full Drivers
NTFS
WinPE is a scaled down version
Of Windows XP. It replaced
MSDOS in deployment and
diagnostic scenarios.
Forced reboot
Every 24 hours of uptime.
Full APIs
Full networking
Mass storage device support
16/32-bit program support
Integrated Development
Programming Frameworks
Kerberos
Distributed File Service STS
.NET Framework
MSMQ
Transaction Service
ASP.NET
Smart Card
Windows Media Services
IIS
Active Directory
PKI
VPN
RAS
WMI
Application Services
Limited Drivers
NTFS
Media Services
API subset
TCPIP
Web Services
Hardware (x64,IA64)
File/Print Services
Mass storage device support
Network Access Services
32/64-bit program support
Directory/Security Services

20. Key Features of Interim WinPE
Hardware Independence
APIs and Scripting Capabilities
Network Access
Windows 32 bit and 64 bit Device Access
NTFS Management
Hardware Diagnostics Support
Support for PXE Protocols
If network or mass storage unsupported, Win PE is useless! Have made it easy to add in additional hardware drivers.

21. WMI Support for HW Tests and Diagnostics
Ability to add WMI base support to iWinPE
(Provides access to underlying hardware via WinPE)
Support for over 40+ providers and classes
Ability to load a Win32/64 bit native driver for hardware manipulation and query
Sample scripts will ship with RC and RTM of iWinPE code
Same functionality will exist in Longhorn-based OPK toolset

22. Ability to Add Device Drivers to WinPE
Change build scripts to support additional HW device classes and drivers in base WinPE image
Ability to add additional Win32 drivers outside of “in-box” drivers to existing build of iWinPE
Ex. Video, Audio, Motherboard and CDRW drives
Ability to add drivers after WinPE image is built for test and diagnostic of the latest hardware/drivers avoiding WinPE re-builds
Drvinst.exe /inf: <folder> <target>
parses through an inf and copies files needed for the specific drivers

23. Call to Action for OEM System Builders
Test applications on the systems you build
Evaluate pre-installed applications using Microsoft security guidelines
Give us usability feedback, especially around the new Firewall and the Security Center
Make security a high priority when configuring & customizing new PCs
Help us get the Windows XP installed base updated with SP2

24. Summary
Windows XP Service Pack 2 OEM Deployment can be performed in exactly the same manner as Windows XP Service Pack 1
Updated documentation is included in Windows XP Service Pack 2
Windows Preinstallation Environment has been Updated based on OEM System Builder feedback

25. Product Support Available To System Builders Who Use The OEM Preinstallation Kit
MS OEM System Builder website:
System Builder Free Support Newsgroups
Support for System Builders
OPK Top Issues Page
OPK Frequently Asked Questions Page
Free Support for System Builders using the OPK. The issues are typically responded to ‘Next Business Day’ for both and Newsgroup support although published responses are 72 hour turn-around to deal with weekends, holidays, etc.