Win 7 Enterprise PCs crashing 48-72 hours after deployment

dondada73 · 27 Mar 2015

Hi-

So i'm in an enterprise environment and we're currently replacing user PCs. HP z420 workstations running Windows 7 Enterprise (64 bit). We receive our PCs directly from HP and then image them with Clonezilla, join them to the domain, etc. and off they go. Never any issues in the past. (w/ Z400 32-bit W7 boxes as well as slightly older z420 64bit boxes - smaller HD, 6gb RAM) with this last shipment of PCs, the process is the same.

Once deployed, every single one of these boxes starts crashing after roughly 48-72 hours, specifically Application Hang based errors related to java and IE 11. after tasking out of the offending application a reboot is required (app will not respond when re-opened) at which point the machine will hang on "shutting down". run the gamut of applying latest windows updates, java updates, AV updates, IE tweaks (some of which can't be changed because of group policy settings) and nothing is working.

once the machine is (inevitably) hard rebooted it behaves, but the same problems eventually re-appear.

ugh. it's killing me because of course we're under a time crunch and management just wants the project "swiftly completed"

AddRAM · 27 Mar 2015

Bad image :)

They are never fun.

You are doing what I/we call a pilot, this image should have been tested and worked out before hand.

The project manager and the on sight IT lead should be working together to fix the problem :)

dondada73 · 27 Mar 2015

I'm the onsite IT, PM is in another location. I've explained the issue to them several times. unfortunately it seems to be confined to my particular office. they say they do not see the issues on the (same) machines, using the same image in their location (= "seems like it's your problem") Image was tested before it was given to me. the weird thing is when i've got the PCs on the bench (normally for up to 4 days) before i deploy them to the users, i don't see any issues (not that i'm really web browsing from these machines or anything, mostly just allowing them to "burn in" and look for any red flags)

2 things have changed since the last batch of PCs we received and imaged : 1)the storage type in BIOS had to be changed to accommodate the new image and 2)the image was originally created for a smaller HD size so i had to re-size the C: partition using GParted so that the entire 500GB was available on the machines after the image was applied.

so you think it is indeed the image? i need some ammo to take into the next conference call!

AddRAM · 27 Mar 2015

Those 2 issues should have no bearing on the outcome, although I know it`s a PITA to keep changing things, but that`s part of IT.

They are passing the buck, they can`t just say Oh it`s your location.

It has to be the image, it should be working perfectly if the machines are the same.

essenbe · 27 Mar 2015

You may want to check the hardware and make sure it is exactly the same. OEMs are famous for putting in whatever hardware they can get for a cheaper price. If the hardware is different, the drivers in your image is wrong.