I currently use ImageX / DISM for my Windows imaging, I've used other solutions in the past but lately I've been using a customized Windows PE environment for imaging, deployment and restoration; just today I created the reference image for the laptop I use.
In my experience I find it more useful to have an image with a bare minimum of things (OS, drivers, activation, updates, maybe Office, that sort of thing) over a full image, but it all depends on the frequency of restorations. A couple of months ago I had to restore a full image from mid-2012 in a machine and the time spent to get it up to date (Windows, programs, removing rarely used stuff and installing new programs, ...) was probably longer than the equivalent of just installing what the user uses at the time.
Full (or incremental/differential) images could be useful if restoring frequently or in data protection / disaster recovery scenarios though, for which ImageX / DISM may not be a suitable solution.
Currently for imaging I'm doing:
dism /capture-image /imagefile:"Destination.wim" /capturedir:"Path" /name:"Name" /description:"Description" /compress:max /checkintegrity /verify
And this to restore (with /index:i too when there's more than one image in the file):
dism /apply-image /imagefile:"Source.wim" /applydir:"Path" /checkintegrity /verify
I store images locally on an external drive, but it should be possible to copy the image over to a networked machine or backup directly to it mounting the resource via "net use" for example.