giz059 Posted February 3, 2006 Share Posted February 3, 2006 Hello everybody,I have to make a ghost image of a w2000 installation which must be able to be load to very different machine.For exemple i put a w2000 on a P4 using chipset i915 and SATA disk. I make a ghost image of this installation.And i would like this image to work on a laptop with a i830 chipset and ide Disk for example ??How can i make my ghost image independant from the harware ??Thank's a lot !! Link to comment Share on other sites More sharing options...
averagecdn Posted February 3, 2006 Share Posted February 3, 2006 As long as your staying within the same chipset manufacturer you will not have problems. The problems arise when you try to go from an intel chipset to a nvidia or other branded chipset. Is this image being used in a network with AD also? Link to comment Share on other sites More sharing options...
cluberti Posted February 3, 2006 Share Posted February 3, 2006 It can be done with sysprep and a few other tricks, but it isn't easy. If you're still interested, and can't use a network-install technology such as RIS (or http://unattended.sourceforge.net/ or similar), let me know. Link to comment Share on other sites More sharing options...
averagecdn Posted February 3, 2006 Share Posted February 3, 2006 As long as you are staying within the same chipset manufacturer there is nothing special that needs to be done because the chipset driver it loads will be an intel chipset driver (ICHxxxx). Unless this image is being brought into an Active Directory network. In this case to prevent problems related to duplicated SID's then you will need to sysprepIf its Windows XP it would be sysprep -quiet -reseal. Link to comment Share on other sites More sharing options...
giz059 Posted February 3, 2006 Author Share Posted February 3, 2006 (edited) Hie cluberty,Sure i'm really intersted in what you can propose (few tricks).I hope i manage to do it !!Thank's a lot for your answer !And it cannot be done using RIS Edited February 3, 2006 by giz059 Link to comment Share on other sites More sharing options...
fizban2 Posted February 3, 2006 Share Posted February 3, 2006 averagecdn,you still have to worry about different versions of NIC card and video cards and the like, building a Standard image you may need to gather all the drivers that you would per machine or device and get them loaded to s single image, then it would be a little easier, are all the machines you are working with a specific brand (ie dell, hp, etc?) are you doing this for laptops as well as desktops? if you wait a little while into the year, Microsoft should be releaseing a nice new tool called Ximageallows for multiple images to be intergrated together. very cool tool. @ cluberti, you know when this might be relesead? Link to comment Share on other sites More sharing options...
giz059 Posted February 3, 2006 Author Share Posted February 3, 2006 hie fizban,My ghost image should work on desktop and on laptop (same image for all hardware).For the moment all pc's are HP Compaq but there are old ones and new ones (very different chipset) Link to comment Share on other sites More sharing options...
averagecdn Posted February 3, 2006 Share Posted February 3, 2006 There was no clarification from the original post about anything other than than the chipset. Yes of course you will need to "bake in" all the other possible drivers and edit the PNP Driver paths. However you can narrow down exactly what drivers are being used so that if you have 3 devices that all use the same driver by viewing the SETUPAPI.log. Instead of loading 3 drivers you can load 1 driver that will support all the other hardware. Link to comment Share on other sites More sharing options...
tioaboa Posted February 3, 2006 Share Posted February 3, 2006 HiThis document from, HP which applies to XP can be used with 2000, the important part in getting a universal image is using sysprep to reset the pnp ID's.check out the link below for a handy PDF by HP although it applies to any hardware not just HP.http://h10025.www1.hp.com/ewfrf/wc/generic...c00592862&lc=enI use this technique extensivly with Win2k and XP on HP\compaq, Dell and home brew PC's without any probems.regardsIan Link to comment Share on other sites More sharing options...
giz059 Posted February 6, 2006 Author Share Posted February 6, 2006 (edited) thanks for this hp whitepaper which seems to be very interesting.trying it this week and let you knom how it works... Edited February 7, 2006 by giz059 Link to comment Share on other sites More sharing options...
giz059 Posted February 7, 2006 Author Share Posted February 7, 2006 i have a problem with my sysprep 1.1In fact i add the [systemmassstorage] section and when i only put :[sysprepMassStorage]pci\cc_0101=%systemroot%\inf\mshdc.infpci\cc_0604=%systemroot%\inf\machine.infpci\cc_0601=%systemroot%\inf\machine.infpci\cc_0602=%systemroot%\inf\machine.infpci\cc_0600=%systemroot%\inf\machine.infpci\cc_0500=%systemroot%\inf\machine.infit works.But when i want to add specific lines for my desktop and laptop :[sysprepMassStorage]pci\cc_0101=%systemroot%\inf\mshdc.infpci\cc_0604=%systemroot%\inf\machine.infpci\cc_0601=%systemroot%\inf\machine.infpci\cc_0602=%systemroot%\inf\machine.infpci\cc_0600=%systemroot%\inf\machine.infpci\cc_0500=%systemroot%\inf\machine.infpci\ven_8086&dev_2448=%systemroot%\inf\machine.infpci\ven_8086&dev_24cc=%systemroot%\inf\machine.infpci\ven_8086&dev_244e=%systemroot%\inf\machine.infpci\ven_8086&dev_24d0=%systemroot%\inf\machine.infpci\ven_8086&dev_2570=%systemroot%\inf\machine.infpci\ven_8086&dev_24c0=%systemroot%\inf\machine.infpci\ven_8086&dev_2560=%systemroot%\inf\machine.infpci\ven_8086&dev_2580=%systemroot%\inf\machine.infpci\ven_8086&dev_2640=%systemroot%\inf\machine.infpci\ven_8086&dev_2660=%systemroot%\inf\machine.infpci\ven_8086&dev_2662=%systemroot%\inf\machine.infpci\ven_8086&dev_2641=%systemroot%\inf\machine.infpci\ven_8086&dev_2651&cc_0101=%systemroot%\inf\mshdc.infpci\ven_8086&dev_266f=%systemroot%\inf\mshdc.infIt doesn't work anymore Any ideas ? Link to comment Share on other sites More sharing options...
IcemanND Posted February 7, 2006 Share Posted February 7, 2006 Porbably has to do with some of the ones you put in not being mass storage drivers.for example:PCI\VEN_8086&DEV_244E.DeviceDesc = "Intel® 82801 PCI Bridge - 244E"PCI\VEN_8086&DEV_2448.DeviceDesc = "Intel® 82801 PCI Bridge - 2448"PCI\VEN_8086&DEV_2570.DeviceDesc = "Intel® 82865G/PE/P/GV/82848P Processor to I/O Controller - 2570"SysprepMassStorage should only contain storage drivers. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now