I'm in the progress of converting old ghost-images used for labs, learning and education in all Microsofts products (about 4TB of data) onto a WDS-server. I started putting them together in a few separated logical "Image Groups" under Install images.
It seems like as the .RWM-file grows, the deployment takes longer and longer the more images I add since the whole .WRM-file for the image-groups gets copied to the client before extracting it. Another problem is that the disk space (sometimes not bigger than 160GB) is too small for the temprary storage of the file on HDD.
What is the recommended approach to deploy images to clients, is it one image group for every image? I plan on having around 100-200 different images. Speed is crucial and hard drive space is limited.
Anybody tried using Server 2012's disk deduplication on the drive storing the RemoteInstall-directory? Is it supported by Microsoft? In that was I can save loads of disk space on the WDS-server storage.
I would be very grateful for any insight, recommendations or even if one could confirm my theory about the .WRM-files. Even when asking somebody, it's not always they can confirm how WDS works in the background.