Note: First and foremost, I'm about to explain a very "rigged" version of our imaging practices. I have a separate question up regarding imaging best practices.
Problem: As of right now, our department is using .wim files to deploy images onto all new machines. These are setup in a virtual machine, then booted to a WinPE iso from within the VM to capture the image using ImageX with the /check and /verify options. Both switches are used when both capturing and applying the image, which has been 9-11 GB in size up to now. Deployment as of right now is done via simple WinPE boot usb and external HDD containing the .wim itself, copied & verified as identical via MD5 & SHA checksums.
This gets data integrity a good ways, but we still run "sfc /scannow" immediately when we hit the desktop after a computer has been imaged and booted just as an extra step to verifying that the deployment was solid. This is as far as I know how to go. We're also looking to change the entire capture & deployment part to a network resource soon for obvious reasons, but I'm not sure if that's better or worse with regard to data integrity.
Summary: In a nutshell, I'm looking for any other methods either simple or automated to implement or scans to run that further ensure the integrity of the OS and our custom configurations by the time we deem it ready to be sent out to the field. If there's a built-in one I'm missing for example, I'd be happy to learn of it!
Extra: This is a concern for us so we don't have machines in the field goofing up in various small and seemingly unrelated ways. Our client-to-help-desk ratio is around 250:1, so keeping deployment problems to a minimum is a must. Of course, there's also the issue of discerning whether there was an issue with deployment or a user somehow managing to wreak havoc on their machine, the computer's physical condition (a lot of our field locations can be quite dusty), etc.
I've been the one heading up anything imaging, and it started out of necessity, so I've had to start implementing the practice without fully learning what all my options, risks, etc. are. Any help would be greatly appreciated.