I make an image on a D630 and works great try to deploy it to a E5400 and it blue screens.
Answer Summary:
http://theitbros.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1
Did you make sure you sysprep'ed the image? For the Win7 Image to be hardware independent you'll need to run sysprep.
Answered 03/26/2012 by: dchristian
Red Belt

  • Yes. Make sure you sysprep the image. We create the image and then sysprep with hardware independence and use Clonezilla. @dchristian is on the right track!
Please log in to comment
1
I have sysprepped the image using sysprep creator here from Itninja. What is the key to making it hardware independant?
Answered 03/27/2012 by: brentballard
Senior Purple Belt

  • This got me going when I was starting out.

    http://theitbros.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish
  • That did it guys I have loaded it on several different dektop and laptops.
Please log in to comment
0
I suspect that your your D630 image will have different storage matrix drivers to the E5400 and that may be causing the BSOD.
Windows 7 is HAL independent, so I doubt it will be the old issue with Windows XP and HAL mismatches.

You don't mention how and with what you are creating your image with (MDT, SCCM, KBOX - something else?), but there will be a method of injecting drivers in the image deployment phase, so that when it boots for the first time it will have the required drivers available.

Please provide more information, and someone with the know-how will probably jump in with a solution for your toolset - I'm a little rusty after not touching this kind of thing for a couple of years now :)

Hope that helps,

Dunnpy
Answered 03/26/2012 by: dunnpy
Red Belt

  • Sorry Using Kbox I will try the sysprep using hardware independence.
Please log in to comment
0
It is best if you create a new image for the new generation of latitudes. I have a separate image for legacy latitudes D520, 530, D620, D630, D820, and D830. Also make sure that the image is sysprep otherwise you are guaranteed to fail.

On a side note, you got win7 to work on a d630? heh, I'll have to try that for fun.
Answered 03/26/2012 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0
Definitely make sure you check Generalize when using Sysprep so it looks for drivers on the new machine for you. Best practice would have you at leaset make a new image for each series. Are you under a lease program? If you are purchasing OEM and per machine, you should try to stick to the same model each year to lighten the image creation load.
Answered 03/26/2012 by: Hammer1790
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share