1E NomadBranch. :)

Daniel Ratliff


-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Fast, David D.
Sent: Friday, November 13, 2015 10:43 AM
To: [email protected]
Subject: RE: [MDT-OSD] How many on your staff work in "imaging"?

For you admins who manage thick images for multiple remote locations, how do 
you distribute the images? I have 4 thick images, each of which is 8-12GB; due 
to the size of the images and WAN bandwidth concerns, I have to distribute via 
DVD/physical shipment.
David
-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Friday, November 13, 2015 7:57 AM
To: [email protected]
Subject: RE: [MDT-OSD] How many on your staff work in "imaging"?

60,000 devices, 4 thick images ( 1 base, 1 base +sql, and 2 dev), 35 'builds' 
using a thick image + other additional items added in the TS. Hardware is 95% 
Lenovo, with just over 35+ total models supported. 

Myself and a junior admin do all imaging, hardware cert, and building/managing 
OSD. 350+ techs do the day to day imaging at each site. 

Daniel Ratliff

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Joe Sestrich
Sent: Thursday, November 12, 2015 4:23 PM
To: [email protected]
Subject: Re: [MDT-OSD] How many on your staff work in "imaging"?

4 would be just about right for us, I think. Two for BAU and two for new stuff. 
Not going to happen, though.... Do more with less, faster.

Sent from my iPhone

> On Nov 12, 2015, at 12:26 PM, Marable, Mike <[email protected]> wrote:
> 
> I’ll take a crack here.
> We support about 15,000 users, but more importantly we support 30,000+ 
> machines.
> We currently have 4 images: 32bit and 64bit Windows 7 and Windows 10.
> Hardware comes from either Dell (up to about 3 years ago) and now HP.  
> There’s probably about 20+ models we support that cover the majority of our 
> systems.  That being said we do support just about anything and everything 
> different departments bring in at a very basic level (if it completes the 
> build sequence, that’s as far as we go).
> 
> My team has 4 people primarily involved in OS deployment.  Each of us focuses 
> on different aspects.
> 
> Mike
> 
> 
> 
> 
>> On 11/12/15, 11:50 AM, "[email protected] on behalf of Joe 
>> Sestrich" <[email protected] on behalf of 
>> [email protected]> wrote:
>> 
>> 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
> **********************************************************
> Electronic Mail is not secure, may not be read every day, and should 
> not be used for urgent or sensitive issues



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain CONFIDENTIAL material.  If you receive this 
material/information in error, please contact the sender and delete or destroy 
the material/information.

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Reply via email to