Are those three machine identical, hardware wise. I know they are the same model, but manufacturers have been know to change things even within models.
Aside from the harddrives, the machines are identical.
The most likely cause is either that the hardware you are imaging has changed from the models you imaged previously, or something has gone wrong in the imaging process.
Even if the models are meant to be identical, they may now have a different motherboard. Any chance of imaging a machine of the same model type that has previously been successfully imaged? that way you can confirm if the image itself is still OK.
To clarify, I mean re-image a machine you have previously successfully imaged (not just a new one of the same model type).
The One-Stop Shop for LANDesk Enhancements
Correct, you will be surprised at the changes within models. The chipset is a big one to cause bluescreens since you are not doing HII. Hard drive controller can also be an issue.
I think you guys are right, for the most part.
We've received two batches of these machines from Dell. Some where manufactured in 2010, others in 2011. I built the image on a 2011 machine. I've attempted to image 5 of these machines (all same model, Opti 980), the three that we manufactured in 2010 failed, one of the 2011 machines worked, the other did not.
Now I'm not quite sure why some of the 2011 machines work and some do not. Very frustrated with Dell now.
Looks like even the 2011 are both different. I would definitely get with Dell on it and hammer that out. If this is going to be a continuous issue, I would suggest looking into Hardware Independent Imaging. While there is some work in setting it up, once you got it going it really makes life easier.
Yea it's just really weird though. The two machines have the exact same manufacturing date. I'm trying to deploy to the non-working one now just to verify.
I have looked into HII, in fact I had HII working for a little while, but then ran into an unattend.xml issue and no one on here or LANDesk support was able to help me sort it out. Bummer.
I want to get HII working, but this makes me even more confused. If LANDesk determines the drivers by the model name, how is it going to differentiate between different drivers for the same "model" computer?
1 of 1 people found this helpful
Well you can have multiple drivers for the same model. For example, if you have two computers with the same model but two different video cards, you can put both of those under the same model and only the right one will install.
Btw, what kind of issue were you seend with the unattend.xml?
Cool, good to know. Thanks!
The issue is covered in this thread http://community.landesk.com/support/thread/15404?tstart=0
The issue is basically: Image deployment works fine, as does driver downloading but once the machine reboots and goes through sysprep, I get an error because sysprep is using the wrong unattend.xml. The deployment places unattend.xml at the root of C:\, but somewhere along the way an unattend.xml gets created in C:\windows\panther, and sysprep tries to use that file. Occasionaly sysprep will pick the correct unattend.xml and everything will work fine, however this only happens about 1 out 20 deployments.
Someone does provide a very convoluted work around, but frankly I barely have enough time at work to get things working as they should, let alone having to jump through hoops.