01 · Starting point
Situation
1,200 clients needed a reproducible rollout covering images, user profile migration, software packages, Endpoint Protection and meaningful reporting.
Constraints
- Rollout target of 1,200 clients
- Dependencies between images, profiles, applications and security
- Reproducible deployment and reporting
02 · Responsibility
My scope of responsibility
I planned the rollout concept, optimised the SCCM site and implemented the key technical building blocks, from collections and distribution points to MDT, USMT and task sequences.
03 · Technical work
Documented scope of work
Key decisions
Map rollout, profile migration, security and reporting in one shared task sequence architecture. A client rollout is only complete when operating system, user data, applications, protection and operational visibility work together.
- I planned the rollout concept for 1,200 clients and optimised the SCCM site.
- I created collections, task sequences, images and software packages and managed distribution points.
- I integrated Reporting Services, Endpoint Protection, USMT and MDT runbooks.
04 · Technical context
Technology in use
SCCM
SCCM was part of the documented toolset in this Endpoint Management engagement.
MDT
MDT was part of the documented toolset in this Endpoint Management engagement.
USMT
USMT was part of the documented toolset in this Endpoint Management engagement.
Endpoint Protection
Endpoint Protection was part of the documented toolset in this Endpoint Management engagement.
AdminStudio
AdminStudio was part of the documented toolset in this Endpoint Management engagement.
Reporting Services
Reporting Services was part of the documented toolset in this Endpoint Management engagement.
05 · Factual basis
Evidence and limits
The client rollout was prepared as a repeatable, monitorable SCCM process.
- Role
- SCCM Consultant
- Period
- January 2013 — March 2013
Lesson from the engagement
Large rollouts become manageable when migration, security and reporting are built into the deployment flow from the start.
Confidentiality note: Internal architecture and operating data of this engagement are not published.