@george1421 Oh so MDT will work in conjunction with Fog? I’ve never tried to run it outside of SCCM but its currently what i’m using to load drivers and apps into our builds with SCCM after the initial deployment. I’d prefer the thin method as it seems easier to keep up to date and add and remove apps at will.

@Wayne-Workman Sounds great thanks again for your quick replies!

Great thanks for the info. I’m used to sysprep and ghost from long ago but using SCCM is a bit different since you just give it a windows cd image and it basically does an install for you then installs software or any other things you want. In this regard it sounds like fog works more like ghost. The good thing is the newer versions so windows seem to contain most of the drivers you might need for newer systems so there won’t be as much fiddling with drivers probably. I did look at the snapin stuff but didn’t see a way to deploy additional software. I need to look more into the client I guess but I was hoping for a system that did not require anything installed on the systems to be imaged. Most will leave our premises and possibly never return.

Does fog work like SCCM where I can build 1 generic image and use it for multiple flavors of hardware? How will it know what drivers need to be added to the system if so? I’m looking for a solution for building systems on our MSP side of the business and can’t use SCCM because of licensing and frankly SCCM is slow and clunky as it is. The big thing i’d probably miss with fog is the ability to pick and choose what software is added to the system. Is fog able to join systems to a domain? What about patching after deployment? I’m guessing no so how do people handle this? Thanks!