Jump to content

Recommended Posts

Posted

I've been there ... you build an image of a machine to go off to a supplier who will load it onto a batch of machines you are due to receive ... you ask a cow-orker to finish off the patches and to install 2 items of software (last minute changes by staff as to what they want) and you tell them to make sure it boots properly after a test sysprep.

 

It comes back and this is what you find. Your Cow-orker has updated drivers to what he thinks it should be, has installed the software on it, has failed to reboot it or even sysprep it, just powered it down using the power button and then sent it off. Said cow-orker is then on holiday and you find yourself with 35 laptops just like this.

 

The solution was to write a check-list of everything that needed to be done to a machine to prepare it for imaging ... it was a painful lesson to learn.

Posted (edited)

Our image for our re-kit in 2009 was all TESTED, CHECKED & was good to go... turns out that they changed the chipset on the model we'd bought and it meant that the image they deployed didn't work as expected, not quite as bad as this... more of a gfx issue but still very frustrating and across 2 computer rooms.

 

I feel for the guy!

Edited by dwhyte85

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...