WinPE GUI Bootdisk

WinPE GUI Boot Disk

WINPE 3.0—Windows 7

Use command line or build a GUI boot disk, its all here.

Yes, you still have to stand up a Windows 7 or Server 2008 machine and install the WAIK tools. No getting around that. So lets start by building a normal WinPE 3.0 disk with all your needed NIC drivers.

WinPE 3.0

Building a Basic WinPe_x86 disk from WAIK 2008 / Windows 7 server

From the Windows WAIK command line window;

1. copype.cmd x86 c:\winpe_x86

2. copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim

3. copy "C:\Program Files\Windows AIK\Tools\x86\imagex.exe" C:\winpe_x86\ISO

4. delete "bootfix.bin" from boot folder ( for auto boot with CD\DVD)

5. oscdimg -n -bC:\winpe_x86\etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpe_x86.iso

6. Burn .iso image

NOTE: If you want your CD to “Auto Boot” at PC startup go into C:\WinPE_x86\ISO\boot folder and delete the “bootfix.bin” file.

Adding packages to WinPE 3.0

1. MOunt your base image Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount

2. Add hta support C:\winpe_x86> Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\windows aik\Tools\PETools\x86\WinPE_FPs\winpe-hta.cab"

3. Add scripting tool C:\winpe_x86> Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\windows aik\Tools\PETools\x86\WinPE_FPs\winpe-scripting.cab"

4. Add wmi package C:\winpe_x86> Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\windows aik\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab"

5. Verify packages were installed Dism /image:c:\winpe_x86\mount /Get-Packages

6. Commit changes to wim Dism /unmount-Wim /MountDir:C:\winpe_x86\mount /Commit

7. create another iso #2 oscdimg -n -bC:\winpe_x86\etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpe_x862.iso

Adding more scratch space to run programs within WinPE 3.0 GUI ( required for Ladybug)

1. Mount your image Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount

2. Check your image Dism /image:C:\winpe_x86\mount /Get-PESettings

Then make changes

3. Setting the scratch space to 64 MB Dism /image:C:\winpe_x86\mount /set-ScratchSpace:64

4. Check settings to see if it changed to 64mb

5. Commit changes Dism /unmount-Wim /MountDir:C:\winpe_x86\mount /Commit

6. create new iso#3 oscdimg -n -bC:\winpe_x86\etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpe_x863.iso

7. Burn .iso image

Add device drivers

1. Mount your image Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount

2. Add .inf driver to image Dism /image:C:\winpe_x86\mount /Add-Driver /Driver:c:\Drivers\mydriver.inf

If you leave open the end of command it will add all .inf drivers in folder Dism /image:C:\winpe_x86\mount /Add-Driver /Driver:c:\Drivers\

If you add "/recurse" at end it will add any .inf file found in sub folders

If you add "/forceUnsigned" at end it will add 64bit drivers - because 64bit machine have to have signed drivers.

3. Commit your changes Dism /unmount-Wim /MountDir:C:\winpe_x86\mount /Commit

4. create .iso image #4 oscdimg -n -bC:\winpe_x86\etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpe_x864.iso

5. Burn .iso

To remove driver from image it must be located by OEM name and then uninstalled

1. To get info on your added driver Dism /image:C:\winpe_x86\mount /Get-DriverInfo /driver:mydriver.inf

2. To remove Dism /image:C:\winpe_x86\mount /Remove-Driver /driver:oem1.inf

WinPE on UFD

partition the flash drive

diskpart

select disk 1

clean

create partition primary

select partition 1

active

format quick fs=fat32

assign

exit

to place on UFD

xcopy C:\winpe_x86\iso\*.* /e F:\

where C is the letter of your technician computer hard disk, and F is the letter of your UFD.

OK, we have a WinPE 3.0 Basic disk that can be used by command line for imaging, DISM, BCDEDIT and command Prompt, now what do I do?

Well, what do you want? Command line or a Windows type of GUI interface. If you are looking for the latter then start here and build a ladybug disk.

Email me a request so you can download the files needed to build a Ladybug disk from my SFTP server. No charge and your agreement to post who you are and the company you work for on my site. Do not expect same day results. I will send you a username and password for free, for a one time download. Email fcc@fatfitz.com with; name, email address, your title, your company, address, phone number and a website link proving the information given. When you do, it will give me permission to post your name, title and company to my list of users of Ladybug. Besides it makes me look good spreading the word and your name and company posted here.

If you want a full copy of ladybug in an .iso format, email me and we will discuss it.

Let’s build

1. Mount up your WinPE image once more; Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount

2. From the SFTP downloaded files; unzip “Ladybug.zip”, inside there will be 2 folders; “extracted items” and ISO and place them on the root of your C:\ drive.

3. Open ; C:\WinPE_x86\mount\Windows\system32

4. Now Copy over ; C:\extracted items\System32 and copy all files/folders, paste them into C:\WinPE_x86\mount\Windows\system32 ( copy and replace winpe.bmp )

5. Copy imagex.exe from C:\iso to C:\WinPE_x86\mount\Windows\system32

6. Open ; C:\WinPE_x86\mount\Program Files ( there are 2 folders there, Common files and Internet Explorer)

7. Copy all folders from “C:\extracted items\Inside bootwim Program files” to C:\WinPE_x86\mount\Program Files .

8. Open C:\WinPE_x86\ISO

9. Copy all files and folders from “C:\ISO to C:\WinPE_x86\ISO. ( if you have followed all commands above in building a plain WinPE disk imagex.exe is already there)

10. You need to edit the batch files in “BATS” to match your domain or stand alone system, especially the mapping of network drive.

11. Un-mount your image; Dism /unmount-Wim /MountDir:C:\winpe_x86\mount /Commit

12. create ISO ; oscdimg -n -bC:\winpe_x86\etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpe_x865.iso

13. Burn the ISO or boot it up on a Microsoft VPC machine.

Its your first ladybug disk, now what can I do with it and how can I edit it?

Well, a lot, and all by a GUI interface.

You can apply a XP, Vista or Windows 7 image to a workstation, laptop or server.

You can capture a XP, Vista or sysprepped Windows 7 image from a workstation, laptop or server.

You can remote image any computer with USB HDD and Ladybug disk using UltraVNC

You can edit any file or folder on any drive of the host system.

Plus there are info programs and fixmbr programs for XP.

Can use DISM , BCDEDIT , BCDBoot or fix MBR records.

Or you can strip ladybug down to the basic components and edit it just for imaging only, its up to you.

OK, so what are the tricks to edit it?

There are 2 “VistaPE.cfg” files that can be edited to make changes; one is located within the boot.wim\Program files\system32 and the other is in the ISO folder.

DO NOT mix these up as they serve 2 very specific functions.

Alright it is not rocket science here, lets look at the vistape.cfg file within system32 folder.

Mount back up your boot.wim file from steps above and go to the system32 folder and open the “vistape.cfg” file with wordpad.

Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount

Yes, it’s a text file.

Here is a sample;

Network|MAP LOCAL DRIVE TO V|%SystemDrive%\Program Files\BATS\mapdrivelocal.bat||

Network|QUERY-What Drive letter is my USB drive?|%SystemDrive%\Program Files\BATS\listvolume.bat||

Disk Tools|XP/Vista-DISKPART Clean & Format "C" drv|%SystemDrive%\Program Files\BATS\cleanandformat.bat||

Disk Tools|Windows 7-DISKPART Clean & Format drives "S" & "W"|%SystemDrive%\Program files\BATS\cleanandformatwin7.bat||

Disk Tools|XP-APPLY map drv V Image to C DRV|%SystemDrive%\Program Files\BATS\imagexapplyxp.bat||

All you have to do in this file is edit it to match your programs or bat files within the mounted boot.wim. Key to remember is within the boot.wim

Do not forget to un-mount your image after editing.

Now lets take a look at the other vistape.cfg file within the root of the ISO folder. This file controls the Programs Files that are located in the ISO folder. It is also the area to add a program that requires registry entries and services to start. It is a bit more complicated but if you look at what is there and the programs links, you will figure it out easy enough.

I will not go into any more detail in this area because you have to learn some things on your own. LOL.

Windows 7

OK, windows 7 does 2 partitions and I have it all figured out whether you want to capture the system drive or not, I have a batch file to cover it.

Vista and XP

Both XP and Vista use a single partition and I have had no issues using ladybug to capture and apply an image to and from a workstation.

GHOST

I have installed on my copy of Ladybug , ghost 8 client and server into my boot.wim section of program files and a shortcut to it in the boot.wim vistape.cfg file and it works awesome. ( shortcut is still in your downloaded copy)

Remote Imaging within a company

Yes, ultra VNC is loaded in here. So, say a hard drive goes down at a remote site of yours, you throw and image on a USB HDD and a ladybug disk into a package and ship it to the site or have a copy there of both already.

Your user boots up the ladybug disk along with the USB HDD and then using DHCP, or the users input you get IP address, and then using UltraVNC you remote into the ladybug desktop and take over the imaging process from user, reboot after imaged and you have a working computer. If your smart you have ultraVNC on image too, so you can log into it when it comes as well, see where I am going? It works!

I have learned a great deal as well on creating sysprepped images for vista and windows 7. But, because I must keep some things to my self , you will have to figure that out on your own. Its easy, took me about 6 hours to get a working Sysprep.xml file using SIM for my Company.

I go to Intel and Broadcom and download their driver sets and then do a /recurse driver install. It installs all 80 NIC drivers at one shot automatically. Do not forget to install the VMware NIC driver too.

I built all of my companies hardware agnostic Windows 7 sysprepped images in VPC 2007 on a XP box using VM’s and then sysprepped them and used the ISO from Ladybug to capture the VM image while traveling on assignment. It’s too easy anymore.

Check page “Users of Ladybug” for companies currently using my ladybug disk for imaging

My image is currently 265MB and will load easily on a workstation with 512MB of ram, it will not load on a 256MB workstation. Takes about 3.5 minutes to load.

What’s next? Who knows.