Mike Stone, Migrating from Ghost to WIM

Report
Migrating from Ghost to WIM
Mike Stone – Alfred University
LabMan 2012
Topics covered
• The fundamental differences between Ghost
and WIM files
• How to create a WinPE 3.0 Environment
• How to create, append, apply, and manage
WIM files
• Applied automation through WinPE 3.0
Mike Stone - Alfred University - LabMan
2012
Topics NOT covered
• How to build a Windows 7 image
• How to build an unattend.xml sysprep answer
file
• WDS and/or SCCM integration
Mike Stone - Alfred University - LabMan
2012
Where we started from
• Ghost 11 and 11.5
• Dell CFI Imaging
• Manual Lab Updates
Mike Stone - Alfred University - LabMan 2012
The old process
• Receive a “seed” system for each unique piece
of hardware.
• Build a new image
• Build a new Netboot Ghost CD
• Capture the image
• Apply the image via Ghostcast
• Update the image periodically (or not)
Mike Stone - Alfred University - LabMan
2012
Frequent problems encountered
• Ghostcast horribly unreliable.
• NDIS2 drivers scarce, difficult to manage.
• Hardware generalization difficult
Mike Stone - Alfred University - LabMan
2012
Major differences
• Ghost can be disk or partition capture/restore.
WIM is partition-based only.
• Management of WIM files is largely
command-line based.
• Post-capture file, driver, and update
management much easier using WIMs.
• WIM can be a container of multiple image
indexes.
Mike Stone - Alfred University - LabMan
2012
WIM index basics
Index 1
• Core Windows 7 files,
no updates, audit
mode, pre-sysprep
Index 2
• Windows 7 with Office
2010, all updates, user
customization
complete, sysprep’d.
Index 3
• Same as Index 2, but
with PSPP, GIMP, and
Sage installed.
Mike Stone - Alfred University - LabMan
2012
First thing’s first - Prerequisites
• Windows Automated Installation Toolkit
(Windows AIK).
• Familiarity with basic Windows command-line
environment.
Mike Stone - Alfred University - LabMan
2012
Three basic tools of WIM management
with WinPE 3.0
• ImageX: Creates, Appends, Deletes, and
Applies WIM images.
• DISM: Manages existing WIM files – driver
injections, package injections, mounting and
unmounting to access file system, etc.
• Diskpart: Partitioning Utility.
Mike Stone - Alfred University - LabMan
2012
Build your WinPE 3.0 System
http://genesis.alfred.edu
1.
Open Deploy Tools Command Prompt as Administrator
2.
call copype.cmd x86 c:\PE\winpe_x86
3.
copy c:\PE\winpe_x86\winpe.wim c:\PE\winpe_x86\ISO\sources\boot.wim
4.
DISM /Mount-wim /WimFile:c:\PE\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:c:\PE\winpe_x86\mount
5.
DISM /image:c:\PE\winpe_x86\mount /Add-Package /PackagePath:"c:\Program Files\Windows
AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab“
6.
DISM /image:c:\PE\winpe_x86\mount /Add-Package /PackagePath:"c:\Program Files\Windows
AIK\Tools\PETools\x86\WinPE_FPs\winpe-hta.cab“
7.
DISM /image:c:\PE\winpe_x86\mount /Add-Package /PackagePath:"c:\Program Files\Windows
AIK\Tools\PETools\x86\WinPE_FPs\winpe-mdac.cab“
8.
DISM /image:c:\PE\winpe_x86\mount /Add-Package /PackagePath:"c:\Program Files\Windows
AIK\Tools\PETools\x86\WinPE_FPs\winpe-scripting.cab“
9.
DISM /image:c:\PE\winpe_x86\mount /Add-Package /PackagePath:"c:\Program Files\Windows
AIK\Tools\PETools\x86\WinPE_FPs\winpe-wds-tools.cab“
10. copy "c:\Program Files\Windows AIK\Tools\x86\imagex.exe" "c:\PE\winpe_x86\mount\Windows\system32\imagex.exe“
11. DISM.exe /unmount-Wim /MountDir:c:\PE\winpe_x86\mount /Commit
12. oscdimg -n –b c:\PE\winpe_x86\etfsboot.com c:\PE\winpe_x86\ISO c:\PE\winpe_x86\winpe_x86.iso
Mike Stone - Alfred University - LabMan
2012
ImageX
Imagex /capture /check /verify [source] [destination.wim] “[short descriptor]”
“[long descriptor]”
Imagex /append /check /verify [source] [existingwim.wim] “[short
descriptor]” “[long descriptor]”
Imagex /apply /check /verify [wimfile.wim] [indexnumber] [destination]
Mike Stone - Alfred University - LabMan
2012
DISM
Deployment Image Servicing and Management
Dism /mount-wim /wimfile:[wimfile] /index:[index number] /mountdir:[folder
to mount into]
Dism /image:[folder wim is mounted in] /Add-Driver /forceunsigned /recurse
/driver:[folder containing drivers]
Dism /unmount-wim /mountdir:[folder wim is mounted in] /commit (or
/discard)
Mike Stone - Alfred University - LabMan
2012
The Genesis Project
Boot off of WinPE 3.0 (starts netstart.cmd, wget http zip
repository and expands it)
Startup.bat
(checks the serial number in csv file against serial number of machine and starts assigned
workflow)
Workflow.bat
(Refresh)
Wipes and repartitions drive. Pulls in wim via torrent into
hidden partition, then applies to main partition.
Workflow.bat
(Reimage)
Unhides partitions, applies existing WIM in hidden image
partition to main partition.
Cleanup.bat
Resets boot system, hides necessary partitions, copies
appropriate setupcomplete.cmd and mysysprep support
files, reboots.
Sysprep Unbundling
Drivers injected via DISM sets up hardware, MySysPrep2
binds to domain, SetupComplete.cmd, activates office
and prompts for administrative users.
Mike Stone - Alfred University - LabMan
2012
Migrating from Ghost to WIM
Mike Stone – Alfred University
LabMan 2012

similar documents