WinPe Plugin list

March 30th, 2008

WinPE additional plug-ins(packages) These additional packages will increase the size of your boot Wim; The name of the package followed by description is below…-WinPE-FONTSupport-<region>-Packages -  Additional font support for ja-jp, ko-kr, zh-cn, zh-hk, and zh-tw.

-WinPE-HTA-Package - HTML application support

-WinPE-MDAC-Package - Microsoft Data Access Component support

-WinPE-Scripting-Package - Windows Script Host support

-WinPE-SRT-Package - Windows Recovery Environment component (OPK only)

-WinPE-WMI-Packages -  Windows Management Instrumentation (WMI) support

-WinPE-XML-Package -  Microsoft XML (MSXML) parser support

 See my last post to view the correct syntax to enter if adding one of the above plugins.

Tags: , , , , , , , , , ,
Posted in Geekend, Microsoft, Microsoft Deployment, Uncategorized, Weekend | 178 Comments »


A WinPE Boot disk in 5 Minutes!

March 17th, 2008

PDF Version

WinPE boot media in 5 easy minutes

Read on…

  1. Download the WAIK/OPK installer from MS here:  

MS WAIK DOWNLOAD

 

WAIK Download Google results  

  1. Install it to default dir’ for ease of use.

 

  1. Go to the newly installed WinPE command prompt and enter the following syntax (each line should be entered separately) green text are comments

   copype x86 c:\mywinpeImagex /mountrw winpe.wim 1 mount

xcopy “c:\Program Files\Windows WAIK\Tools\x86″ mount\x86 /cherkyi

Now choose components to add if required, I recommend the scripting plug-in:

peimg /install=WinPE-Scripting-Package mount\Windows

Now adding drivers, example, for NIC’s use the VISTA drivers + have the drivers ready on your C: drive in a folder i.e. C:\Drvs

Peimg /inf=”c:\drvs\b57driver.inf ” mount\Windows

Peimg /prep mount\Windows

imagex /unmount /commit mount

del iso\sources\boot.wim /q

imagex /export  winpe.wim 1 iso\sources\boot.wim

oscdimg -n -bc:\mywinpe\etfsboot.com c:\mywinpe\ISO c:\mywinpe\winpe_x86.iso

  1. The last 5 lines there are prepping the .Wim to be finalised and then exported to the .iso for burning.
  2. Now burn the .iso it’s already bootable so no need to mess around, Nero will do just fine.
  3. Boot the source PC to the CD and test it out
  4. See my next post for Capturing an image and applying an image etc using imagex

…………….Click the top PDF link to download the instructions as a PDF.

Posted in Geekend, Microsoft | 99 Comments »


EaSy guide to WinPE 2.0 (Vista and XP) + Imaging (with all the holes Plugged!)

March 13th, 2008

Hey,

Just a quick note to check back soon, I will be posting an easy guide to another everyday conundrum; How to quickly put together a WinPE 2.0 boot disk (for use in roll-outs etc) but without the need for any third party tools.

The reason I’m doing this is simple; although winpe 2.0 (final version) has been around now for over a year or so people still are not using it as much as they could/should be in the live environment. Perhaps they are scared of learning new tricks, perhaps they are not uber geeks with time to waste on new tricks?

Whatever the reason if you read the Microsoft pages they will tell you its as easy as a,b,c and 1,2,3 and there are no problems to be had…But anyone that has messed around with previous versions of PE (or given up and gone to Bartpe) will know that with different hardware and OS configurations making these discs work right is not ‘easy’!

My guide will cover some major issues that i discovered and will CERTAINLY save you the time trawling the web to find the solutions. Also included are downloads that can be put to use with no tweaking or changes necessary AND a fix for the dreaded ‘Uber bug’.

 Woo!

Check back soon.

Tags: , , , , , , , , , , , , , , ,
Posted in Geekend, Microsoft, Microsoft Deployment | 97 Comments »


A Devcon Example - Quick and easy

February 23rd, 2008

Devcon + XP upgrade… a quick and smooth ‘how to’ guide: 

Devcon simply put is the command line version of Microsoft’s Device Management that you will be familiar with in windows 2000 and above.

 

If your like me and have been unimpressed by the devcon resources you found on the web then this should help you. I recently completed an XP upgrade rollout with the help of Devcon and it was incredibly useful (yes I know upgrades suck but ‘they’ insisted).

 

 Step 1) you will need a reference computer i.e. one similar or ideally the same as the ones you are going to use Devcon on. You will also need Devcon.exe; Its available Here.  

Step2) Now ask yourself what am I going to be using devcon for??…This article will focus on driver installation for a specified hardware device after an XP Upgrade/install.

 

Step3) you need to have a windows distribution share if you are installing over the network. This article will not cover that. But its in the Distro’ share that your unattend.bat should be that will copy all the necessary files to the local pc before the upgrade starts. Here is an example of Unattend.bat (you can remove the Rem statements):

 

 copy \\ServerName\Windist\I386\unattend.txt c:

REM This line copies the unattend file to the local pc

xcopy /e /i \\ServerName\Windist\I386\Dell_Drivers c:\DellDri

REM This line copies everything that you have put into the Dell_Drivers folder to local pc

\\ServerName\Windist\I386WINNT32.EXE /copysource:Dell_Drivers /unattend:unattend.txt /s:\\ServerName\Windist\I386

REM this last long line starts the upgrade (using the unattend.txt file)

Step 4) your devcon script; for this you will need the Hardware Id of the device or devices that you are going to install. Some people say that the easiest way to get these ID’s is from Devcon itself but I say NO! Here is the easiest way to get Hardware ID’s

From the reference computer in windows open computer management and then device manager. Find the device i.e. network card and right lick à properties à then click on the details tab this will display a drop down menu that shows all the various ID’s the device uses. Write down the first Hard Ware ID in full.

 

Now create a new text file for the script, see below for example of the syntax required (this is all one line):

 

c:\DellDri\WinXP_nicDell620\devcon.exe UPDATENI “c:\DellDri\WinXP_nicDell620\b57win32.INF” PCI\VEN_14E4&

 

   We are referencing the folder that was copied earlier using the unattend.bat, in that folder is the devcon.exe and the drivers for the device. The script will call devcon.exe with the UPDATENI command and then fetch the .INF file and apply it to the device specified at the end of the line PCI\VEN_14E4&

Notice that for this device I only needed the first part of the hardware ID. Devcon found the device and then applied the .inf; it will return a ‘successful’ message when completed. When creating the above script SAVE IT WITH A .CMD extension preferably.

 

 Step 5) If you are using the devcon script after an upgrade then make sure it is referenced in your unattend.txt file for the windows install. The below example would call the scripts at first logon. 

[GuiRunOnce]    Command0=”c:\DellDri\WinXP_nicDell620\DellNic.cmd”    Command1=”c:\DellDri\WinXP_nicDell620\ShellStyle.cmd” 

Also See this website for other useful info on the subject of upgrading. As described the unattend file does skip allot of references in the unattend.txt when performing XP upgrades. 

Summary: 

-Create a folder that contains Devcon.exe and the driver files for the devices, also your Run Once scripts will need to be in here!

-Make sure this folder is copied to the destination PC HDD before the upgrade starts (using a script is easiest)

-Create the Devcon script and save it as .cmd then add the final path to the script into your unattend.txt file in the GuiRunOnce section as above.

-Run the upgrade and when complete logon to the  pc and your scripts should run.

 

End.

Tags: , , , , , , , , ,
Posted in Microsoft Deployment | 104 Comments »


LightBox test

February 19th, 2008

Scenery Scenery

Posted in Uncategorized | 104 Comments »


Hello world!

February 19th, 2008

Yes this is the first post! We had to start somewhere.

Posted in Uncategorized | 158 Comments »