Hardware independant imaging

MDT can do this - although it's not entirely obvious when you first dip your toes into it (you need to add it as an application, and then put some logic into a task sequence so that Windows will install that "application" when necessary during deployment). There are multiple ways to do it, so I'll include some links here on driver management in general (the first link is a script you can add to MDT to handle these "applications" for drivers, and how to configure it):

• http://deployment.xtremeconsulting.com/2009/11/02/install-driver-exe-package-new-tool/
• MDT 2010: Driver injections « [Deploy_Windows (TRUE)]
• Assign Drivers to Computer Makes and Models « Xtreme Deployment
• Johan Arwidmark - MDT 2010 Lite Touch Driver Management

The important takeaway here, though, is understanding that what you are asking sounds easy, but is in fact pretty darned complex. You're going to be learning a new tool (or two), and doing things differently than you may have in the past. The light at the end of the tunnel, though, is that the tools aren't necessarily complex, they're just involved. Once you learn how to use something like MDT, you really will have a TON more control over your deployments of Windows, applications, and drivers!

SCCM and MDT is best suited for machines that are always connected to a network, because it is most beneficial as a deployment/management solution, rather than a 'one-off-install-and-send-them-away'

If its friends and clients, you may have some issues around the licensing too...

MDT is designed for either network or removable-device-based deployment (it can be PXE booted, it can create an ISO to be burned to DVD of the deployment point, or it can be copied to USB and run from there assuming the USB key is bootable).