01 · Starting point
Situation
Errors in the SCCM topology, open support cases and unclear file server permissions made administration, software delivery and transparent reporting harder.
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 platform, supported the administrators with open cases and worked through SCCM, permission and reporting topics until operations had a traceable foundation.
- I analysed and corrected errors in the SCCM topology.
03 · Technical work
Documented scope of work
Key decisions
Correct topology, permissions and reporting together. SCCM stability is not just a site question; content access, file server rights and reliable reports determine how manageable it is day to day.
- I cleaned up file server permissions and set up SID mapping.
- I integrated SQL Reporting Services and resolved open SCCM-related tickets together with the administrators.
04 · Technical context
Technology in use
SCCM
SCCM was part of the documented toolset in this Endpoint Management engagement.
SQL Reporting Services
SQL Reporting Services was part of the documented toolset in this Endpoint Management engagement.
File Server
File Server was part of the documented toolset in this Endpoint Management engagement.
SID Mapping
SID Mapping was part of the documented toolset in this Endpoint Management engagement.
05 · Factual basis
Evidence and limits
The SCCM environment gained a more stable technical basis for administration, delivery and reporting.
- Role
- Migration Consultant
- Period
- February 2013 — April 2013
Lesson from the engagement
Endpoint platforms only become dependable in operation when topology, rights and visibility are treated as one system.
Confidentiality note: Internal architecture and operating data of this engagement are not published.