Most Valuable Professional
Group: Forum Members
Until Macrium develops such a solution, if you have any Windows Server systems in your organization, one option you might consider is keeping Reflect Site Manager for backups and restores of specific systems, but using WDS (Windows Deployment Services) for gold image deployment. It's included with every Windows Server instance, fairly easy to set up (nothing like SCCM), and it has some very cool features. For example:
- Images are file-level rather than block-level, which means the files can be single-instanced, so for example if you had two 25GB gold images that were 95% identical, then even before considering compression, the WDS server would only need a little over 26 GB (25GB + the 5% difference of the second image) rather than 50GB to store the two images. This also means that a single image can support both Legacy BIOS and UEFI clients, since WDS deployment builds the "ancillary" partition structure dynamically for each client.
- It supports maintaining a driver library on the server external to the images, and it can then include those drivers with the image it deploys to clients either based on the client's detected hardware or always (e.g. to include drivers for external peripherals not connected during imaging). This means that if you started rolling out a new type of PC, you would just need to add its required drivers to the WDS server, and ALL of the images you deploy through WDS now support that new PC, without ever having needed to touch the images themselves. Same goes if you needed to start including a critical driver update in future images -- just replace the driver in the WDS library and images will start rolling out with the new driver instead, even if an older version of that driver was originally baked into the image.
- PCs can be automatically joined to the domain (or not) and named according to a formula you can specify.
- It supports network booting into both an image deployment environment and an image capture environment; the source image for both is just the Boot.wim file from any regular Windows installation media, though it includes support for injecting drivers into these boot environments and you can even fully customize the image through other means if desired. It can also generate bootable media for the capture and deployment environments if you have systems that can't perform network booting.