I don't have the lab situation, but I do deploy our images using SCCM. I use MDT to create my reference image, with a build and capture task sequence. Then import the wim into SCCM to deploy. In my case, I maintain a single reference image for all workstations, and add device specific drivers and applications as part of the SCCM osd task sequence.
In your case, depending on how drastically different the images for each lab are, you may or may not be able to use a single reference image, but you should be able to move some of the customizations into the osd task sequence at least, and then when the lab managers need to add or change something they can edit the task sequence rather than rebuilding the entire image. Steve — Sent from Mailbox On Thu, Mar 26, 2015 at 9:03 AM, Iacaruso, Mike <[email protected]> wrote: > I have a question and I am looking for opinions from other who use SCCM for > image deployment. I currently use MDT for image creation and deployment and > I have SCCM 2012 R2 for software distribution. There are several labs in my > environment that each has a lab manager or coordinator that currently use > Ghost for image creation and deployment. The idea is to move them to SCCM > and allowing each lab to create and deploy images to their respected lab > using RBA. How are other SCCM admins managing this type of environment? Has > anyone had any issues with RBA? Do you manage the entire imaging process > centrally or is breaking into roles a better option? > Thanks > Mike Iacaruso > Enterprise Desktop Engineer > Office of Technology Services > Towson University > 410-704-3965 > [email protected]<mailto:[email protected]>
