3 ms·
>spend-four-hours-reimaging-the-machine or spend-unknown-period-of-time-trying-to-fix-new-problem Definitely. In our case its 8 hours minimum though for a re-i
by Havoc 13y ago
>spend-four-hours-reimaging-the-machine or spend-unknown-period-of-time-trying-to-fix-new-problem
Definitely. In our case its 8 hours minimum though for a re-image. Somehow the FDE makes pulling the old data off the machine slow.
You've got my sympathies though - I'd not like to be the one doing the IT in these cases. Can't be fun troubleshooting IT with that kind of time pressure.
- c0nsumer 13y agoThank you. It really, honestly is hard on our tech because they feel the pressure from all sides. Eight hours sounds rough for a reimage. I think ours are... maybe two or three? We've done a lot of work to get the reimage time down, and Win7 (WIMs) have made this really nice. If this is something that smells of a bigger problem (or has been seen elsewhere) then I push for them to get the user a wholly new machine, capturing the old one for analysis. If the user is given an upgraded machine, then there is usually little resistance, even with the downtime that'll be incurred. On the upside, if the issue can be reproduced readily, from this we can almost always get root cause and put a systemic fix in place. If it's sporadic... Well... I'm sure you understand how it goes trying to fix something that you can't yet reproduce. ;) (I'd love to troubleshoot your slow data backup issue... That's the stuff I rather enjoy.)
- Havoc 13y ago>I'd love to troubleshoot your slow data backup issue... That's the stuff I rather enjoy. I'm not directly involved with the tech side so I don't know the details. I gather they pull the old data off the disk using some offline low-level tool though (like you would for harddrive damage recovery). Between that and the encryption its somehow very slow. No idea why its like that though. >get the user a wholly new machine I wish it was the same here. They just give loan machines :/