01 · Starting point
Situation
An existing SCCM environment showed structural and network-related problems, while open tickets and missing administrative knowledge weighed on operations.
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 analysed the site structure, took on escalation tickets, resolved network issues and ran a workshop with practical exercises for the administrators.
- I reviewed and optimised the SCCM site structure.
- I analysed open network issues and took on support tickets.
03 · Technical work
Documented scope of work
Key decisions
Combine platform optimisation with working on real tickets and an admin workshop. The new structure was not only to work technically, but to be understood and operated securely by the internal team.
- I developed and led a workshop with practical exercises for the administrators.
04 · Technical context
Technology in use
SCCM
SCCM was part of the documented toolset in this Endpoint Management engagement.
Site Design
Site Design was part of the documented toolset in this Endpoint Management engagement.
Networking
Networking was part of the documented toolset in this Endpoint Management engagement.
Troubleshooting
Troubleshooting was part of the documented toolset in this Endpoint Management engagement.
Administrator Training
Administrator Training was part of the documented toolset in this Endpoint Management engagement.
05 · Factual basis
Evidence and limits
SCCM structure, open technical issues and administrator knowledge were brought together in a compact improvement engagement.
- Role
- SCCM Consultant / Trainer
- Period
- March 2010 — April 2010
Lesson from the engagement
Platform optimisation lasts when the future operators can follow decisions and diagnostic paths directly on their own system.
Confidentiality note: Internal architecture and operating data of this engagement are not published.