SCCM 2012 - Deployment Time and Cost?

Hi,

My organisation is looking into the deployment of SCCM 2012. I would like to get an estimate of how long the deployment may take, and any methods that I can use to estimate the engineering effort/time that might be required. I have included some high level information about our environment below.

I understand that no-one can give me a definitive guide, but I thought that many experts would have completed similar deployments and could give me some useful advice.

The functionality we are looking to deploy from the outset is: Hardware and Software Inventory, Patch Management (Microsoft Patches) and the Forefront Client. The deployment is to the End User Computing fleet only initially. Once this is complete we will look to extend the functionality later.

My environment is approximately:
 - 750 Wintel based users at the primary site
 - Windows 7
 - Single site deployment which may be extended to branch offices at a later date
 - 60 servers (80% virtual, server deployment to come later)
 - No pre-existing SCCM environment in place. We do have a SQL server that we can create another instance on.

I would appreciate any guides or examples that people have worked on so that I can estimate the engineering time/cost for the mini project.
LVL 1
rjkirbyAsked:
Who is Participating?
 
Nagendra Pratap SinghConnect With a Mentor Desktop Applications SpecialistCommented:
One day installation. Total of 7 days for most common tasks.

As for documentation and training, that is a harder topic.
0
 
merowingerCommented:
If it's quick and dirty it can be done very fast, but i suggest to start with test Systems first and make sure that you Clients are configured correctly and the deployments are working properly. With SCCM you have local Admin permissons on all Clients and you should make sure you do not kill all Clients at once!!!
0
 
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Actually one day is for installation only. Then there are steps like discovery, collection planning, bandwidth settings, post install work like backup/DB trimming etc.

Each of them can take one day.

SCCM has dozens of features now. Software updates can take a lots of hours even for the first push. OS deployment has to be tested for each model.

It can be an ultra large project if you include things like Macintosh/Linux support.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.