Winpe 3.0 - Win7 Guide In Progress

As requested by one of our members I compiled this guide. This is my First Guide
and It is a work in Progress. I have plans to cover the registry as well.

Note: I will be re posting to my new Website With lots of room for Images

Project Q&A

Why Use Windows 7 For this Build?
• Support for Virtual Hard Disk.
• Easy mounting for VHD via Disk Management.
• Access to your local Drives while on WinPE mode.

Why Use a VHD instead of ISO?
• All files get saved to VHD while on PE Mode.
• Applications Get Installed Correctly (Via EXE)
• Once you complete your Build you can capture an Image and create your ISO.

Why use Index 2 of the Windows 7 Boot.wim?
• Contains most drivers.
• Has all the Optional Components.

Components Loaded
1. WinPE-HTA-Package
2. WinPE-MDAC-Package
3. WinPE-Scripting-Package
4. WinPE-SRT-Package **
5. WinPE-WMI-Packages
6. WinPE-WDS-Tools-Package
7. WinPE-Setup-Package
8. WinPE-Setup-Client-Package
9. WinPE-Setup-Server-Package
10. WinPE-LegacySetup-Package


System Requirements

• Windows 7 RC1 X86 loaded on Host PC and Installation Media
• Microsoft Windows AIK (Windows 7 Deployment tools)
• GImagex

Note:Make sure your copy of Windows 7 RC1 was downloaded from
Microsoft. Leaked version may have viruses and trojans



The Build


Project Structure

Let’s keep all our working files on One Place.

Directory Structure on Root of Local HD

 Directory1.png   91.24KB   240 downloads


Files we need to create for the Windows System32 Folder.

Winpeshl.ini

[LaunchApp]AppPath = %SYSTEMDRIVE%\Windows\System32\vpeldr.exe

Vistape.cfg

[main]screen=1024x768defaultshell=BS Explorer[shortcut]Desktop|My Computer|X:\Program Files\CubicExplorer\CubicExplorer.exe||Desktop|Infra Recorder|%SystemDrive%\Program Files\InfraRecorder\InfraRecorder.exe||Desktop|Mozilla FireFox|X:\Program Files\FireFox\FirefoxPortable.exe||Desktop|GimageX|X:\Program Files\GImagex\X86\gimagex.exe||Desktop|GimageX|X:\Program Files\DependencyWalker\depends.exe||Disk Tools|GimageX|X:\Program Files\GImagex\X86\ gimagex.exe||Network|Mozilla FireFox|X:\Program Files\FireFox\ FirefoxPortable.exe||CD Record Tools|Infra Recorder|%SystemDrive%\Program Files\InfraRecorder\InfraRecorder.exe||Disk Tools|MBRWizard|%SystemDrive%\Program Files\ MBRWiz\MBRWhisky.exe||QuickLaunch|PENetwork|%SystemDrive%\Program Files\ PENetwork\PENetCfg.exe||Network| PENetwork|%SystemDrive%\Program Files\ PENetwork\PENetwork.exe ||[autorun]hidenowait|Starting ObjectDock|X:\Program Files\OBJECTDOCK\ObjectDock.exe[shells]BS Explorer|BSExplorer\Explorer.exeObjectDock|OBJECTDOCK\ObjectDock.exe[postconfig]hidewait|Human Interface Device Access|x:\windows\system32\net.exe start "hidserv"hidewait|Computer Browser|x:\windows\system32\net.exe start "Browser"hidewait|User Profile Service|x:\windows\system32\net.exe start "ProfSvc"hidewait|Server|x:\windows\system32\net.exe start "LanmanServer"hidewait|DNS Client|x:\windows\system32\net.exe start "Dnscache"

Application to be DownloadedFirefox Portable Extract to (C:\WinPE_Project\Program Files\FireFox)Cubic Explorer 0.90 ZipExtract to (C:\WinPE_Project\Program Files\ CubicExplorer)INFRA RECORDER version 0.46.2 Portable ZipExtract to (C:\WinPE_Project\Program Files\InfraRecorder)MBRWizard – Script from Nightman on Winbuilder VistaPE Project.Extract from Script and copy to folder ( C:\WinPE_Project\Program Files\MBRWiz)PENetwork Beta V3.2 or Higher from Winbuilder VistaPE Application Script made by Holger Kotsch ( Note: If you want to add WIFI Support you need to manually copyThe files specified on the script plus registry settings)Copy to Folder (C:\WinPE_Project\Program Files\PENetwork)Objectdock downloadObjectDock Portable I downloaded this as a Script from WinbuilderWhere. Copy to folder (C:\WinPE_Project\Program Files\OBJECTDOCK )BSExplorer – Script from Winbuilder. Extract the files to C:\WinPE_Project\Program Files\BSExplorer  GImageX v2.0.14Create a folder on Program Files Name GImageX. Extract the files and copyThe X86 folder to (C:\WinPE_Project\Program Files\GImagex)Dependency Walker 2.2Extract the files to(C:\ WinPE_Project\Program Files\DependencyWalker) Your Program Files Folder should now look like this now.  ProgramFolder.png   156.72KB   360 downloads WIM File ExtractionsOpen Imagex Gui v2.0.16 BETA and Apply from the Windows 7 RC1 the Install.WIM to C:\WinPE_Project\Install Folder (Make Sure to Select Index 5 from the Install.WIM)Make sure you select the correct drive letter.Oops I am out of Space for more Pictures. I work something out soon Picture goes HereNext Select from the Windows 7 RC1 the BOOT.WIM and apply to C:\WinPE_Project\Boot Folder Make Sure to Select Index 2 From the boot.WIM)Make sure you select the correct drive letter.Oops I am out of Space for more Pictures. I work something out soon Picture Goes HereFile Copy Process 1. Copy the Folder (C:\WinPE_Project\Program Files) to (F:\WinPE_Project\Boot) and Over write when prompted2. Copy the vistape.cfg and Winpeshl.ini to C:\WinPE_Project\Boot\Windows\System32This is the list of the files you need to copy, I will keep updating as I get more.

Windows\System32 Files Need it from Install.wim copy them to (C _linenums:0'><strong class='bbc'>Windows\System32 Files Need it from Install.wim copy them to (C:\WinPE_Project\boot\Windows\System32</strong>apphelp.dllCertEnroll.dll             CertEnrollUI.dll clbcatq.dll crtdll.dll cscapi.dll devmgr.dll efsadu.dll msoert2.dll msrating.dll ndfapi.dll netplwiz.dll occache.dll oledlg.dllpuiapi.dll RstrtMgr.dll shdocvw.dll shfolder.dll vaultcli.dll wdi.dllmsfeeds.dll Msi.dllGDIPLUS.DLL    IEshims.dllimgutil.dllinetcomm.dllmlang.dllMMDevAPI.dll

Hint Find the Folder or DLL Inside and just paste to target Boot, Make sure to Create the Folders or Paste them!

Windows Folder Created with DLLs insideFrom Install Wim Copy FolderWindows\winsxs\x86_microsoft-windows-security-vault_31bf3856ad364e35_6.1.7100.0_none_625c0918901ee09aCopy Folder to Target (C _linenums:0'><strong class='bbc'>Windows Folder Created with DLLs inside</strong>From Install Wim Copy FolderWindows\winsxs\x86_microsoft-windows-security-vault_31bf3856ad364e35_6.1.7100.0_none_625c0918901ee09aCopy Folder to Target (C:\WinPE_Project\boot\Windows\winsxs\)From Install Wim Copy FolderWindows\winsxs\x86_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7100.0_none_ec13f209f2934e2aCopy Folder to Target (C:\WinPE_Project\boot\Windows\winsxs\)From Install Wim Copy FolderWindows\winsxs\x86_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7100.0_none_746d768d089a904a        Copy Folder to Target (C:\WinPE_Project\boot\Windows\winsxs\)Files on Folder are {Msi.dll, msimsg.dll}                                                                    From Install Wim Copy FolderWindows\winsxs\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_8.0.7100.0_none_d3ba97b35255ec5fC:\WinPE_Project\boot\Windows\winsxs\Windows\winsxs\File Inside {IEshims.dll}From Install Wim Program Files\Internet Explorer\IEshims.dllTo (C:\WinPE_Project\Boot\Program Files\IEshims.dll)From Install Wim Copy FolderWindows\winsxs\x86_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7100.0_none_f0cfd45d663bf2d5Copy Folder to Target (C:\WinPE_Project\boot\Windows\winsxs\)From Install Wim Copy File to FolderWindows\winsxs\x86_microsoft-windows-ie-imagesupport_31bf3856ad364e35_8.0.7100.0_none_ca223091ab2b6539\imgutil.dllCopy Folder to Target (C:\WinPE_Project\boot\Windows\winsxs\)From Install Wim Copy Files to FolderWindows\winsxs\x86_microsoft-windows-mail-comm-dll_31bf3856ad364e35_6.1.7100.0_none_eaa422cbada275b2INETRES.dllinetcomm.dllCopy Folder to Target (C:\WinPE_Project\boot\Windows\winsxs\)From Install Wim Copy Files to FolderWindows\winsxs\x86_microsoft-windows-mlang_31bf3856ad364e35_6.1.7100.0_none_c7d243da39141f88mlang.dllmlang.datCopy Folder to Target (C:\WinPE_Project\Boot\Windows\winsxs\)From Install Wim Copy Files to FolderWindows\winsxs\x86_microsoft-windows-mmdeviceapi_31bf3856ad364e35_6.1.7100.0_none_c5f73bf90e77abd3MMDevAPI.dllCopy Folder to Target (C:\WinPE_Project\Boot\Windows\winsxs\)

Creating Your VHD files

Open A Command Prompt Windows and Type Each Command

diskpartcreate vdisk file=c:\winpe.vhd type=fixed maximum=2024select vdisk file=c:\winpe.vhdattach vdiskcreate partition primaryassignformat quick label=VHDexit

Oops I am out of Space for more Pictures. I work something out soon
Picture Goes Here

Adding the VHD to your Boot Menu


Updated July 29, 2009. Auto fill GuiID

bcdedit /create /d "WinPE 3.0 X86" /application osloaderfor /f "tokens=1-3" %%a in ('bcdedit /create /d "WinPE 3.0 X86" /application osloader') do set guid1=%%cbcdedit /set %guid1% device vhd=[C:]\winpe.vhdbcdedit /set %guid1% osdevice vhd=[C:]\winpe.vhdbcdedit /set %guid1% path \windows\system32\winload.exebcdedit /set %guid1% systemroot \windowsbcdedit /set %guid1% detecthal yesbcdedit /set %guid1% winpe yesbcdedit /displayorder %guid1% /addlastExit

Oops I am out of Space for more Pictures. I work something out soon
Picture Goes Here


Now lets copy the files (C:\WinPE_Project\Boot\*.*) to the Newly created VHD
Once the files are copied reboot your PC and At the Boot menu Select WinPE 3.0



Oops I am out of Space for more Pictures. I work something out soon
Picture Goes Here

Object Dock is here : ObjectDock Script

Good Tutorial Morphs

Works like a charm, but would like to add 2 comments...

1. there is a typemismatch i found out:
In the section "Adding the VHD to your Boot Menu" there is a space missing between systemroot and \windows
command: bcdedit /set {GUI ENTRY} systemroot \windows

And, like me as i didnt know better what was meant by {GUI ENTRY}, sorry im not so used to PE environments, but the GUI ENTRY is created after the first command

bcdedit /create /d "WinPE 3.0 X86" /application osloader

Maybe you can add/change this in your manual?

Pls continue with this manual, its really good!

What advantages does booting from a vhd file give over booting from a wim file?

What advantages does booting from a vhd file give over booting from a wim file?

At least mklink.exe works.

And what is written to the local disk (vhd) is not gone with next boot.

So you are facing the same problem as booting winpe from harddisk (over time), as it gets messed up.

Joakim

I presume that's only true if the vhd is hosted on writable media. If its hosted on a DVD then I presume its not writable? Or are writes redirected to ram? Or is it readonly?

What advantages does booting from a vhd file give over booting from a wim file?

The only advantage there is to booting to VHD is that It will allow you to make
what ever changes you like, You can install Applications and test, Step by Step
customize you WinPE. Once you complete your Project Load to your Windows 7
and mount the VHD to a Drive. After Mounted use GIMAGEX to capture the boot.wim
Copy the boot wim to your thumb drive where you already have your files. This is a huge
time saver!

Right now I am working on my new site were I plan to make guides and host some files.
It has been hard learning, PHP, MySQL, Apache and Joomla to make the site work the way I want to.
If I had the money I will have go Sharepoint 2007 wish I already know how to configure.

The only advantage there is to booting to VHD is that It will allow you to make
what ever changes you like, You can install Applications and test, Step by Step
customize you WinPE. Once you complete your Project Load to your Windows 7
and mount the VHD to a Drive. After Mounted use GIMAGEX to capture the boot.wim
Copy the boot wim to your thumb drive where you already have your files. This is a huge
time saver!

Right now I am working on my new site were I plan to make guides and host some files.
It has been hard learning, PHP, MySQL, Apache and Joomla to make the site work the way I want to.
If I had the money I will have go Sharepoint 2007 wish I already know how to configure.

In reference to toytoy question

Works like a charm, but would like to add 2 comments...1. there is a typemismatch i found out:In the section "Adding the VHD to your Boot Menu" there is a space missing between systemroot and \windowscommand: bcdedit /set {GUI ENTRY} systemroot \windowsAnd, like me as i didnt know better what was meant by {GUI ENTRY}, sorry im not so used to PE environments, but the GUI ENTRY is created after the first commandbcdedit /create /d "WinPE 3.0 X86" /application osloaderMaybe you can add/change this in your manual?Pls continue with this manual, its really good!

You get the {GUI ENTRY} after running the bcdedit /create /d "WinPE 3.0 X86" /application osloader
You can then copy this {GUI ENTRY} to text file before continuing
I do have a more advance batch file that will do all of this for you, It should work in Windows 7
I will test first then post the code.

I presume that's only true if the vhd is hosted on writable media. If its hosted on a DVD then I presume its not writable? Or are writes redirected to ram? Or is it readonly?

If VHD is hosted on read-only media like a DVD, normally it would fail because disk writing is not redirected to RAM. Anything changes offline or online is done to disk live. But there is a thing in this VHD boot technology called differencing disk; setting parent-child relationship between VHD images, where the parent is never modified, only the child; all writes are redirected to the child. One use is that different users can share the same parent (a predefined environment) with their own child images (their preferred environment and settings).

It also sounds like snapshots of a virtual machine. It helps during configuration and testing of an image by protecting the base while still allowing saving the writes. If things go wrong, simply delete the child and reestablish another child relationship to parent to begin again.

If VHD is hosted on read-only media like a DVD, normally it would fail because disk writing is not redirected to RAM. Anything changes offline or online is done to disk live. But there is a thing in this VHD boot technology called differencing disk; setting parent-child relationship between VHD images, where the parent is never modified, only the child; all writes are redirected to the child. One use is that different users can share the same parent (a predefined environment) with their own child images (their preferred environment and settings).

It also sounds like snapshots of a virtual machine. It helps during configuration and testing of an image by protecting the base while still allowing saving the writes. If things go wrong, simply delete the child and reestablish another child relationship to parent to begin again.

Or, if both read-only and read-write are desired in different times, it may be possible to configure the BCD with 2 entries so that when read-only protection is needed, boot to the parent; when saving changes is needed, boot to the child.

I update the guide please check
http://pcdeployment....c...30&Itemid=2

According to the win7 aik you don't have to specify a drive letter for the vhd file. You can use:

bcdedit /set {guid} device vhd=[locate]\windows7.vhd
bcdedit /set {guid} osdevice vhd=[locate]\windows7.vhd

This may work better if the vhd is on a different drive than the bcd store.

According to the win7 aik you don't have to specify a drive letter for the vhd file. You can use:

bcdedit /set {guid} device vhd=[locate]\windows7.vhd
bcdedit /set {guid} osdevice vhd=[locate]\windows7.vhd

This may work better if the vhd is on a different drive than the bcd store.

is it possible to store the vhd in unc path ? like

bcdedit /set {guid} device vhd=[\\nas\portableapps]\windows7.vhd
i want it to use for pxe
the image boots flawlessly but i cant integrate my apps in the boot.wim

No, you can't access network at that stage. I suppose you want to use external apps outside the boot.wim in a PXE boot condition? You have to integrate apps into the boot.wim, or else it wouldn't work. Or, you can put the apps on a network share and after having booted PE, connect to the network share and access the apps there.

For the latter choice, one way of doing it is to add this to the startnet.cmd

:: this is to get authenticated on the server and access the share

net use z: \\hostname\share /user:username password

:: this is to automate diskpart with a "script.txt" 

diskpart /s script.txt



:: where script contains line of mounting a virtual disk:

select vdisk file="z:\apps.vhd"

attach vdisk

assign letter=y

exi

then you can access the apps from y:

File Copy Process

1. Copy the Folder (C:\WinPE_Project\Program Files) to (F:\WinPE_Project\Boot) and Over write when prompted
2. Copy the vistape.cfg and Winpeshl.ini to C:\WinPE_Project\Boot\Windows\System32


I get stuck at copying these files to the boot folder, windows will not let me copy them there.

I update the guide please check
http://pcdeployment....c...30&Itemid=2

I tried to go to the link, but got an "INTERNAL SERVER ERROR" page. Would it be possible for you to ZIP up the guide, including the scripts and make the file available?


Please......!!!

Has anyone found a better giude than this one or at least one that is complete?

This looks very good, but I work at a repair shop....ok FoxConn to repair HP servers, well we see many use quite a bit of memory, is there a way to make a VHD with the X64 Windows 7 with SP1? I would like to slipstream quite a bit of drivers into it...over 4gig worth to be compatible with everything we work on and I would like to also be able to install programs in it to debug the units too, but I am new, I have seen grub4dos multiboot and that would also be great if I could go into one of those screens and choose either to boot into the Windows 7 environment or choose between a set of dos tools.

I know this is possible, but how?