@george1421 said in Setting up the right FOG Environment:
@tomcatkzn said in Setting up the right FOG Environment:
I was thinking that I need for each operating system/hardware combination :
A base image with drivers and updates but no other software
then a pre-sysprepped image of each of the above with other software installed.
then a final sysprepped image for deployment.In our case we have a generic OS image and then use FOG to place the required diver files in a predefined location on the target system during imaging. Granted we only use Dells in our company, but we have 3 images (Win7x64, Win10x64, Win10x64EFI) for 15 different hardware models. It takes a while to set this up, but we can add new models without needing to recapture images for each new model. Also with this design, we recapture these 3 images each quarter with the latest updates (we may abandon this since Win10 will change the way updates are applied anyway).
We build our reference images on a VM so that we have capabilities like snapshotting, and hardware independence during reference system creation. We do use Microsoft MDT to automate our reference image build. That way we get a consistently built reference image each quarter.
Thank you for the feedback. I was lead to believe that using a VM for the reference image was not a good idea according to an article by Mitch Tullock (the link escapes me at the moment), although we are currently doing it with MDT/WDS.
Can you elaborate on how you: “use FOG to place the required diver files in a predefined location on the target system during imaging.”