Ultimate Plugin "sysprep -pnp" On Target 2k Or Xp, when your RARE motherbard broken Options

[samplempg]

is there any special plugin like this exist ? If it dose, it will make bardPE even more technical LV. I am waiting one

[Former_tarkan_post]

i don't know how to implement sysprep...so that it modify all items on the installed windows version...but it is worth thinking about it....

[rgroves]

based upon what I know about Sysprep it needs to be installed into your C:\ drive and must be able to manipulate teh local registry.

I feel that if you run Sysprep from within PE the following will happen:
1) it won't run because PE is running from the CD.
2) If install PE to the HD, and run it from there, it will trash PE, and your system may not boot.

WHY are you wanting Sysprep on PE anyway?? If it's for mass system deployment, you should create an image fo hte machine and include sysprep inside that image.

[samplempg]

rqroves, I am so sorry about my bad english. I will explain why we need "sysprep -pnp" on TARGE OS (not PE ...it is in the title)

Let me give you a hint, try do unplug your Primary IDE Harddrive (which contain your Windows 2000 or XP OS). And put it into different system (in other word, different MOTHERBOARD). You will understand what I try to explain. Your system will end up to blue screen of death. windows 2000 or xp won't auto detect all the drivers like win98. The only way to make win2k boot up and auto detect all the drivers is using delpoy package and run "sysprep -pnp". (in most case we use "sysprep -pnp" on mass distribution which contain DIFFERENT TYPE MOTHERBOARD or generic ghost)

If you working in a BIG COMPANY, and they are using a SUPER OLD rackmount server as DC. What you ganna do if the server's motherboard broken ? Try to buy a same motherboard from museum? if sysprep plug exist, that will be awesome

[allow]

just an idea: try analyzing what sysprep -pnp does and maybe we can build a tool that will do the same from PE...

@samplempg & @all

if you can, please try sysprep with running regmon & filemon, anD see what you can find out...

[CWorks]

i have created an image using drive image on a vmware xp install with no sound or net
or usb and restored it to 14 different motherboards so far and it all went without a hitch
when they booted for the first time it would detect all the motherboard resources
and after a couple of reboots all was well without a bluescreen and no sysprep
i used xp sp1 with the rollup and had 2 updates from ms website when it was done

total time to install xp went from 45 - 60 min to 20 - 30 min
with office 2k3, nero 6, mozilla 1.5, norton sytemworks 2k3 installed also

they were all asus and abit boards with via chipset i don't like sis or intel chipset
most had sound and lan onboard

and to change username and company

xp username.reg

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"RegisteredOrganization"="Your Company Name"
"RegisteredOwner"="Your Name"

office 2k3 username.reg

CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\InstallProperties]
"RegOwner"="Your Name"
"RegCompany"="Your Company Name"

This post has been edited by cworks: Jan 16 2004, 03:28 PM

[CWP]

they were all asus and abit boards with via chipset i don't like sis or intel chipset most had sound and lan onboard

The main reason for the BSoD is the change in chipset manufacturers, so you wouldn't encounter that kind of problem.

CWP

[CWorks]

they were all asus and abit boards with via chipset i don't like sis or intel chipset most had sound and lan onboard

The main reason for the BSoD is the change in chipset manufacturers, so you wouldn't encounter that kind of problem.

CWP

vmware uses intel chipset so it should work for that also
i think it has to do with the video drivers 8 out of 10 times it's the video
drivers that have caused my BSod's or a combination of usb, lan, video, chipset

that's why i used vmware so i could eliminate all but the chipset the vieo was set to
the default vga driver that comes with xp

[CWP]

Odd, most of the time the changes in the video cards didn't cause BSoD's for me. Changing between chipset manufacturers would.

Then again, we were testing on real machines.

CWP

[CWorks]

i am using real machines to restore to when i created an image on real machine
and then restored on a different machine sometimes i would get a blue screen
all of them were via chipset just different video cards ati or nvidia

only ever built machines with via chipset

that's why i used vmware to make the image of xp from
xp uses the vga driver for it

the bsod's were about 3 out 10 machines
but now i'm 14 out of 14 and no bsod

this is not for a backup just to quickly setup a machine with everything installed and configured so i can have a machine go from parts to sold in under an hour
i build them in my spare time witch i don't have enough of so anything i can do to speed it up

[juul]

You can make a bootable CD and dump an image with a utility like Ghost to the HD. The image must consist off the subdirs : one with WINPE in minint, the other the normal i386 with a slipstreamed XP or 2K. Make sure that WINPE boots up on the HD. In PE you can do a scripted install off all you want.
duration half an hour for XP pro with office

[CWorks]

i use a bootable cd with drive image ver.6 for dos and have the image on a hard drive
set as slave and restore to the new drive set as master and then shutdown unplug drive
with image reboot install drivers for vid, nic, modem, etc... etc.. done in about 20 - 30 minutes already have everything installed in the image

i have tried it using usb hard drive and it took three times longer to restore it

[samplempg]

hiye coworkers.
We are talking about how to migrate a OS to different motherboard. Not how to make generic ghost. When the a gereneric ghost image load all the drivers on board, the os is NO LONGER GENERIC. Unless you login the system and type "sysprep -pnp" in command prompt. The problem is you don't even have CHANCE to enter the system because of BSOD, unless you got same motherboard (or that motherboard's brother or sister)

[d4vr0s]

Try changing the IDE ATA/ATAPI controller to 'Standard Dual Channel PCI IDE Controller' before you migrate.

[samplempg]

could you teach me how to enter a system and change the IDE setting when it is already showing blue screen of death ? (in that case, your old motherboard killed by SURGE, and you change a new motherboard. That mother board just don't let you enter your old OS)

actually I know one, just run PE and use erd2002 (or 2003) and regedit modify target os's registry setting (like ide or chipset whatever...require certain skills on understanding registry)

or use "sysprep plugin" if it exist

[dani2]

OH
I have a fix.
It is not in plugin format though.

I call it "FixIDE", it modifies the registry so your local windows can accept all the different standard IDE hard drives. Plus there is instructions on the disk on how to make your non supported SCSI/RAID driver work!

But, it isn't in plugin format. Does someone want to make the inf files for me?
Trust me it works. I work for a technican company and whenever we upgrade computers we just clone the drive and move the drive to the new hardware, run FixIDE and power it on

[samplempg]

Could you post a download link for FixIDE ?
And what kind environment you run fixIDE ? MS's recovery console or BOOT disk with NTFS support...or ?

[Joshua]

OH
I have a fix.
It is not in plugin format though.
But, it isn't in plugin format. Does someone want to make the inf files for me?

@dani2
no problem, send me the files and i make a plugin for that.
email: dcs@drowaelder.de
Joshua

[this-is-me]

Does this get around the BSOD moving windows xp from one sys to the other?

[dani2]

IF the bsod says "INACCESSABLE_BOOT_DEVICE" and you have the hard drive hooked up to the motherboard's IDE controller. There are instructions on it to apply your own drivers but that is a little more complicated.