Meetings are one of us yelling over the wall at the other :) Number of staff to cover these responsibilities is what I'm mostly curious about. We have two, for 60k devices and 200 sites. Using MDT.
Sent from my iPhone > On Nov 12, 2015, at 12:18 PM, Jimmy Martin <[email protected]> wrote: > > It's the same all over... :-) but I don't see anything in your list about > the 4 hours of meetings per day :-) > > > Jimmy Martin > (901) 227-8209 > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Joe Sestrich > Sent: Thursday, November 12, 2015 10:51 AM > To: mdtosd Myitforum <[email protected]> > Subject: [MDT-OSD] How many on your staff work in "imaging"? > > I'm curious what other teams are doing. How many people do you support? How > many images/OSes? Variety of hardware? > > By "imaging", I'm including everything from soup to nuts: > > Evaluating new hardware - Benchmark, QA, obtain and add drivers to SCCM/MDT. > > Support hardware issues with new features, driver issues, accessory support > (docking, wireless, Bluetooth, etcetera.) User and tech education. > > Manage current OS/base image - add/remove features, icons, look and feel. > Decide on standards. QA the builds. > > Eval new OS'es. Create new base images. Features, icons, look and feel, > standards, QA as above. > > Build and manage the deployments - build task sequences, test on assorted > hardware. > > Build and manage MBAM/Bitlocker deployment. Script TPM activation, MBAM > install, test and deploy. > > Manage replication of deployment solution to production. > > 3rd level support for all the above. > > The floor is yours... > > Sent from my iPhone > > > > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the foregoing > messages, and delete it immediately. > > P Please consider the environment before printing this email... >
