Wondering if anyone's encountered this: Recently we reimaged (wiped and reinstalled a Windows image) a Dell Latitude E6420 ATG. It had Windows 7 before and worked fine, but ever since the reimage once Endpoint Encryption begins (well, a few minutes after it begins) you can't log in to Windows, or if you were logged in when it began you can't unlock the workstation later, and if you were logged in frequently Explorer.exe no longer responds (keyboard [CAPS lock] and mouse still work though). The HDD indicator above the keyboard is solid; even if I leave the computer on over the weekend I come back Monday the HDD's still solid activity and nothing is responsive.
I checked for updates on Dell's website for the E6420 ATG and incorporated the latest drivers into the image. Even tried Intel's latest Chipset (which was just the iaStor file). System's on the latest BIOS too (A08).
The on-board diagnostics (selectable at boot) ran and found no problems.
According to Device Manager in Safe Mode (which works fine) the system is using an Intel 6 Series / C200 Series chipset driver and the AHCI storage controller. The ATG also has a touch screen and a SSD (Lite-On LAT-128M2S 128 GB).
Deploy the same image, but without the Endpoint Encryption agent/client (so encryption never starts) and the system appears fine.
Deploy the same image without Dell's system drivers and now the unlock workstation doesn't completely hang for hours on end, it returns to CTRL + ALT + DEL after about a minute (as if the blank spot where the username/password fields would be are timing out due to inactivity). So, progress in some sense.
To my knowledge this has not happened on any other system, including the standard Latitude E6420 (which is the model we're deploying to employees currently). We only have a handful of ATG units--still, I'd like to fix it instead of tell people we'll have to replace their machine (kind of need the semi-rugged/rugged model for some field workers).
If anyone's seen this issue, or something like it, I'd appreciate any information that may help identify why I can't log into Windows once the ATG is encrypted and why/how its pegging the HDD or causing the system to hang.
Message was edited by: pcktech on 12/13/11 7:38:10 AM CST, 12/13/11 7:55:11 AM CSTMessage was edited by: pcktech on 12/13/11 8:37:55 AM CST
I don't have any definite answers, but I do have a few ideas about additional details that could be helpful.
Raid is default on these models and the Dell BIOS has had some historical problems with this hard drive mode and EEPC. Switching to AHCI may help.
The Dell E6220 and Dell E6420's are among the models we're deploying globally and they have had back to back BIOS issues. I'm not confident that Dell has worked everything out, but having more information may give some clues about how to proceed. I think you can switch between RAID and AHCI without reimaging as long as you have Vista or Win7, but I doubt going to ATA would allow the system to boot. Windows XP isn't very good about accepting drive mode changes and may require a reimage to test the various SATA modes.
I have some other ideas, but it would require a download of the Sysinternals tools from http://www.microsoft.com/sysinternals/ - I don't usually go that route unless I've exhausted the basics, but I have been able to track down the cause of some pretty difficult problems that would have been almost impossible otherwise.
Thank you zeitgeist for your recommendations, and I'm sorry I couldn't reply sooner (got sick), but I did find a solution Thursday. I had to do a full disk format; not a quick format, but the one or two hour long format. I did it using diskpart > FORMAT FS=NTFS
By default our reimaging scripts use FORMAT FS=NTFS QUICK, but apparently that wasn't erasing enough data from the disk. My only speculation is it has to do with SSDs, Full Drive Encryption, and how SSDs deal with data cleanup. Not sure if this is an issue with the Lite-On SSD in the E6420 ATG or not; I don't think we've deployed many E6520s (Samsung SSDs) in order to compare--could even be a one-time deal.
So, to summarize: If full disk encryption causes your SSD to lock up try a full format of the hard drive. Full formats may not be ideal for SSDs, but it seems to have done the trick in this case.