I'm new to deploying server images, etc. After a lot of reading, I feel like I have a pretty good grasp on the basic tools and techniques for adding drivers, updates, etc., but I have a few questions.
First of all, this is a "virgin" environment - there are no preexisting deployment servers. I mention this only because I've seen some articles outlining how I could accomplish what I want to do if I already had a WDS server in place (build
and capture, etc.).
So, from the top: I did a "junk" install of server 2012 standard just to familiarize myself with the interface, etc. Having done that, I'm now planning on starting anew and doing a hyper-v setup with two VMs. What I would like to do, first,
is take my "stock" server installation image and slipstream all of the updates a fresh server with no additional roles would require.
Where I'm running into a bit of a hitch is the actual acquisition of the appropriate update msu/cab files. Is there a good way for me to do this now that this junk installation has been updated? I can't very well use windows update to download the
already-installed packages, and I see no good way to download all the ones I would want, and just the ones I would want, short of doing it manually. There has to be a better way, right? And, going forward, once I have a WDS in place, I would obviously
want to keep my images current with the appropriate updates. Is there a good method for automatically acquiring the appropriate packages for maintaining disparate images (if, say, one VM is running RDS and the other is running ADDS, I wouldn't want to
apply the ADDS to the RDS server image... right?).
Any input would be much appreciated.
↧
Questions about servicing a server image.
↧