Joshua Dumas
asked on
syspreping machine types of machines with one image
Has anyone ever setup a machine using sysprep to blow down to multipal machines. What I have is a Compaq Deskpro EN 733 and a Compaq Evo 1.6 and I would like to create one image and blow it down to mulpital machines. See what they do here is create a image for a single type of machine. What I am thinking is to have one image and dump all the drivers for all the machines into the $OEM$ folder and see what happens...BUT I am wondering if anyone has ever done this and how successful were you?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I found the thread where we discussed this in length.. I am sure it will help you with your imaging.... And yes, it can be done, but follow the advice of these experts..
https://www.experts-exchange.com/questions/20870044/Windows-Preinstallation-Kit.html
https://www.experts-exchange.com/questions/20870044/Windows-Preinstallation-Kit.html
Using sysprep 1.1 should allow for this, even if it doesn't changing the IDE Controllers to Windows Default and then sysprepping allows you to put an image on pretty much anything.
I successfully imaged a Compaq Deskpro EN and put it on a IBM Thinkpad A21m, and they don't get much different from them!
That was with using Sysprep 1.0 as well. 1.1 is supposed to allow for different HALS but I've not tried that.
I successfully imaged a Compaq Deskpro EN and put it on a IBM Thinkpad A21m, and they don't get much different from them!
That was with using Sysprep 1.0 as well. 1.1 is supposed to allow for different HALS but I've not tried that.
Thanks...
FE
FE
I work as a desktop engineer for an organization of around 35,000 end users in Americas, Europe and Asia. My primary role is creating images for our laptop and desktop users (28000 laptops / 7000 desktops) Our two images (1 for laptop / 1 for desktop)must support each two types of hardware (2 types of desktops and 2 types of laptops). Getting confusing? We are releasing an image for all of the desktops on our organization (basically two different models of Dell), first we create an image on one of those desktops, backit up using Ghost, then then put it onto the other model of desktop. This only works if the two types of hardware are relatively close in hardware specs to each other. Any drivers that need to be loaded / installed are installed. We then back this image up using ghost, NOW we can have an image that contains hardware drivers for two different models of Desktop Computer. We do the same process for the laptop.
After creating this "coreload" image, we then write a script that will configure the machine when it is first booted, run Sysprep, etc...
Creating an image this way eliminates the need to add drivers to the $OEM$ folder for the sysprep process. Remember, for this to work the two / three different machine types must be at least from the same manufacturer, and hopefully the mobo chipsets and other hardware wont be too different. Please let me know if there are any other questions, this is a vast topic.