Unsolved WDS Install Images - Groups Strategy

---

Is it the group or the wim that allows you to have multiple options when pushing out new images with WDS?

Mike mentioned that you can create groups that allow you to put images together that reduce the amount of storage used. He mentions compression on the images and also "single instancing" where you can have multiple installs in one wim.

What would you put in a group but not a single wim? Is it just the wim that does single instancing? Are there limitations for using one over the other? Can I mix architectures? Are there any examples or best practices?

Video Location:

MCSA Windows Server 2012 - 70-411 Course Subtitle: Administering Windows Server 2012
Deploy and Manage WDS
38:04

It appears that file resources are shared automatically. I'm still not sure what MS means when it says "across each image group." Perhaps it's each group shares resources within itself or each group shares with each other group.

I think I just wanted to know how to approach setting groups up. Or if it makes a difference.

Microsofts Comments in the Server 2008 FAQ
https://technet.microsoft.com/en-us/library/cc732729(v=ws.10).aspx#General

Windows Deployment Services does not use the Single Instance Store functionality that was used in RIS. Instead, Windows Deployment Services uses a method by which file resources are shared across each image group (and therefore single-instanced) and the metadata of each image resides in a separate .wim file. The image store takes the concept of split .wim images a step further by creating a split media set consisting of two files:

• An "empty" .wim file that contains only the definition of the image

• A Res.rwm file that contains all the file resources for all images in the image group. The data within Res.rwm is single-instanced and compressed; therefore, the Single Instance Store service is no longer needed. In fact, with Windows Deployment Services, the storage size on disk for images within an image group is greatly reduced, and it is more efficient than the storage mechanism used in RIS.

I didn't see anything similar in the Server 2012 notes.
https://technet.microsoft.com/en-us/library/hh831764.aspx