Customized Windows PE 5.0

A quick run-through covering creating a customized Windows PE bootable drive, mainly so I don't space out and forget any of the steps (*ahem* again).

The below is based on the Deployment and Imaging tools available by installing Windows ADK 8.1


Create Windows PE files

Run Deployment and Imaging Tools Environment as Administrator

 Create the base structure with copype command:

 copype <architecture> <directory>

 Example for 64 bit:
copype amd64 c:\winpe64

Example for 32 bit:
copype x86 c:\winpe32
Paths to packages

 amd64:
\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs
x86:
\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs
Mount boot.wim

(assuming current path is the root of WinPE, e.g., c:\winpe)

 dism /mount-wim /wimfile:media\sources\boot.wim /index:1 /mountdir:mount


Adding Key Packages

 (assuming current path is \Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs)

 
1:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-Scripting.cab  
2:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-Scripting_en-us.cab  
3:    
4:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-WMI.cab  
5:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-WMI_en-us.cab  
6:    
7:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-MDAC.cab  
8:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-MDAC_en-us.cab  
9:    
10:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-HTA.cab  
11:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-HTA_en-us.cab  
12:    
13:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-NetFx.cab  
14:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-NetFx_en-us.cab  
15:    
16:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-PowerShell.cab  
17:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-PowerShell_en-us.cab  
18:    
19:  dism /image:c:\winpe\mount /add-package /packagepath:WinPE-DismCmdlets.cab  
20:  dism /image:c:\winpe\mount /add-package /packagepath:en-us\WinPE-DismCmdlets_en-us.cab


Add customizations

Add a customized HTA menu (e.g., menu.hta in \windows\hta\) then add the below line to startnet.cmd in \windows\system32 to open it on startup:

%windir%\system32\mshta.exe %windir%\hta\menu.hta
Unmount boot.wim after committing changes

 dism /unmount-wim /mountdir:c:\winpe\mount /commit
Prepare USB stick

 (via either diskpart or Disk Management. The partition must be marked as Active.)

 diskpart
list disk
select <disk number>
clean
create partition primary
format quick fs=ntfs label="WinPE"
assign letter=W
active
Example for finding the correct Disk number:

 DISKPART> list disk

   Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB      0 B
  Disk 1    Online         7634 MB      0 B

 DISKPART> sel disk 1

 Disk 1 is now the selected disk.
Alternatively, prepare a USB HDD with multiple partitions:
diskpart
list disk
select <disk number>
clean
create partition primary
format quick fs=ntfs label="WinPE"
assign letter=W
active
select <disk number>
clean
create partition primary
format quick fs=ntfs label="Data"
assign letter=X
It's worth noting that UEFI only supports booting from FAT32 partitions.
Copy \media\ and its sub-directories to the root of the USB stick/drive:

 robocopy /mir c:\winpe\media w:


Comments

Post a Comment

Popular posts from this blog

Change the ComputerName value in Unattend.xml using PowerShell

A quick and dirty PowerShell script to update the value of ComputerName in Unattend.xml before imaging. This particular value is located at: <unattend>  <settings pass="generalize">   <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">     <computername> Which is a bit of a mouthful, but we can be lazy and just pull the value from the nth component node (in my case it's 3, or the 4th component node). PowerShell uses dots to describe the hierarchical path, which looks a lot neater than the above: $xml.unattend.settings.component[3].computername To repeat, the value of .component[n] will change depending on the structure of the file. The value of the...
Read more

Testing out Link Aggregation

Image
I picked up a TP-Link managed switch last week as something of a compromise between affordability and features - as it turns out though, it does just about everything I could ask for, just without the extra expense from buying something that has HP or Cisco written on the side. I grabbed the TL-SG3216, a fanless L2 managed switch with 16x1Gigabit ports as it ticked all the boxes: Silent (fanless) Managed Link Aggregation/802.3ad (LACP) 802.1Q (VLAN) STP As a bonus, the CLI interface (via console cable or ssh) is very similar to Cisco's IOS, so I don't have to learn an entirely new syntax to configure it. Before I replace my existing switch, I spent a bit of time testing out its features. First up, I setup a spare Raspberry Pi with a second ethernet interface (via a USB dongle) to test out link aggregation. First up, the configuration on the Pi (Raspbian): Install ifenslave to allow for the creation of bonded network interfaces # apt-get install ifenslav...
Read more

Adding 802.1Q Trunking to Debian GNU/Linux

Here's a quick guide to setting up 802.1Q trunking for VLANs on a Debian GNU/Linux box connected to one or more Cisco Catalyst switches, which could then be used as a cheap router replacement. Configuration on the Debian box: Add 8021q to /etc/modules so 802.1Q support is enabled at startup. To install it immediately: # modprobe 8021q Use vconfig to add the VLANs to the interface you'll be using (if vconfig is missing, run apt-get install vlan ): # vconfig add eth0 2 (In the above, eth0 is the physical interface and 2 is the ID of the VLAN) Give the interface an IP. Choose an address in the range you've set aside for that particular VLAN. In this example, VLAN 2 is using 192.168.2.0/24. # ifconfig eth0.2 192.168.2.201 netmask 255.255.255.0
Read more