Vickus
New Member
- Reaction score
- 0
- Location
- Sudbury, Ontario, Canada
I hear the best way to do it is with a USB stick, any suggestions?
+1.wim image = fastest!
You can't get any faster then wds
boot to network
load winpe
deploy image
reboot
takes less then 10 minutes.
My old method could do it in about the same amount of time depending on if its from the 10/100 network, 100/1000 network, or usb hdd.
Pop in winpe cd
plug in usb hdd
load winpe
batch script
reboot
imagex /capture x: y:\filename.wim "Image Name"
select disk 0
clean
rem == 1. System partition ======================
create partition primary size=300
format quick fs=ntfs label="System"
assign letter=S
active
rem == 2. Windows partition =====================
create partition primary
format quick fs=ntfs label="OS"
assign letter=W
list volume
exit
imagex /apply y:\filename.wim 1 x:
@echo off
cls
:start
echo ********** IMAGING **********
echo ***** PARTITIONING DISK *****
diskpart /s diskpart.txt
echo ***** APPLYING IMAGE *****
imagex /apply win7pro.wim 1 w:
echo ***** MAKING BOOTABLE *****
bcdboot w:\windows /l en-us /s S:
echo ***** IMAGING COMPLETE *****
pause
This is my old method:
Prepare image:
1) Install windows
2) At OOBE hit Ctrl+Shift+F3 to enter sysprep audit mode. You can close sysprep the system will continue to boot into audit mode until you seal it.
2) Install updates, software you wish to be included in the image except for AV, make tweaks, etc.
3) Run sysprep with Enter OOBE, generalize, shutdown.
Capture Image:
1) Boot system using a WinPE disc, usb, PXE boot, or even slave the drive
2) Run imagex
x: = drive you want to captureCode:imagex /capture x: y:\filename.wim "Image Name"
y:\filename.wim = filename of image
Image Name = What you want to call it, "Win 7 Pro", "Company Image"
3) Place image on flash drive, usb hdd, dvd, network share, wherever you want.
Apply Image:
1) Boot system using a WinPE disc, usb, PXE boot, etc
2) Partition hard drive diskpart /s script_file.txt
For MBR layout:
I also have an EFI version not handy.Code:select disk 0 clean rem == 1. System partition ====================== create partition primary size=300 format quick fs=ntfs label="System" assign letter=S active rem == 2. Windows partition ===================== create partition primary format quick fs=ntfs label="OS" assign letter=W list volume exit
3) Run Imagex
y:\filename.wim = image fileCode:imagex /apply y:\filename.wim 1 x:
1 = index, index starts @ 1. If you only have one image in a wim put 1, otherwise use the desired image number. (The wim format can hold multiple images in one file, IE: install.wim has all the versions of the OS in it.
x: = Target partition
4) Run bcdboot x:\windows /s s:
x:\windows = any windows directory
s: = system partition letter
Simple batch script I used to use:
Code:@echo off cls :start echo ********** IMAGING ********** echo ***** PARTITIONING DISK ***** diskpart /s diskpart.txt echo ***** APPLYING IMAGE ***** imagex /apply win7pro.wim 1 w: echo ***** MAKING BOOTABLE ***** bcdboot w:\windows /l en-us /s S: echo ***** IMAGING COMPLETE ***** pause
Related Reading:
Windows Imaging Format
Imagex Command Line Options
What is Sysprep
Sysprep your OS more then 3 times
Building and Deploying an image
Download Windows AIK
or
Download Windows OPK
Create a Custom Windows PE Image
Download Microsoft Deployment Toolkit
Capture Windows 7 image using MDT 2013
Deploy Windows 7 image using MDT 2013
Deploy Windows 7 on network without a server using MDT
GImageX GUI version of imagex
2. Presently I am using a WinPE disc for Diskpart and USB hard drive for wim images.
Is there a way for the script to prompt me for which wim to use? At the moment each one is called image.wim and they are in folders named win7hpx64 and win7prox64 etc.
Ditto.
This machine is STILL doing windows updates... it has to be going on over 300 updates now including service pack 1.
Thanks for the info, I'll try to put it into action here very soon.
This machine is STILL doing windows updates... it has to be going on over 300 updates now including service pack 1.
Would have save hours off of the total repair time, and even a good hour or more off of the hands on time.
Yes, that's a pain...
i hate when i need to restore the factory image from a Asus Eee Pc or anything else with a Atom CPU![]()
I need to get my act together![]()
Ditto.
Me too, just never enough time. Being crazy the past week, working from 6am until 9pm can only happen for so long
Paul
....... Or generally just about any old "factory restore" routine.
It's not just the updates, it's removing all accumulated "trials" and other junk which was a deemed a good idea at the time.