01 · Starting point
Situation
Standardised operating system and software delivery required a complete SCCM structure to be built, while the internal team was also enabled for operations and migration.
Constraints
- Changes within an already established IT environment
- Short, clearly scoped engagement
- Internal system and operating details remain confidential
02 · Responsibility
My scope of responsibility
I documented the target design, prepared Active Directory, installed SCCM and implemented sites, distribution points, PXE, images, task sequences and application migration.
03 · Technical work
Documented scope of work
Key decisions
Build the platform end to end, from the directory service to operational distribution. SCCM only works reliably when AD, site design, content, PXE, images and monitoring are aligned.
- I designed and documented the SCCM configuration, site structure and AD prerequisites.
- I installed SCCM, set up distribution points and PXE and created images and task sequences.
- I planned software delivery, monitored the platform and supported the application migration.
04 · Technical context
Technology in use
SCCM
SCCM was part of the documented toolset in this Endpoint Management engagement.
PXE
PXE was part of the documented toolset in this Endpoint Management engagement.
Task Sequences
Task Sequences was part of the documented toolset in this Endpoint Management engagement.
Distribution Points
Distribution Points was part of the documented toolset in this Endpoint Management engagement.
Active Directory
Active Directory was part of the documented toolset in this Endpoint Management engagement.
05 · Factual basis
Evidence and limits
The organisation gained an end-to-end SCCM foundation for operating systems, applications and ongoing platform monitoring.
- Role
- SCCM Consultant
- Period
- July 2011 — August 2011
Lesson from the engagement
Endpoint platforms should be built as a service chain; a correctly installed site alone does not yet deliver a reliable rollout.
Confidentiality note: Internal architecture and operating data of this engagement are not published.