During this engagement with Bridgewater Associates, our Sr. SCCM Architect held a position of SCCM Architect Consultant for the client to assist with a new implementation of SCCM 2012 migrating off LANDesk. The design consisted of a 2 tier hierarchy with CAS and 3 primary sites. One site was dedicated for Piloting features and deployment while all other sites manged all desktops and servers. The Pilot site was used QA that was locked down leveraging the RBAC permission model. The environment was built with dual reporting in mind with one SSRS Reporting Point located on the CAS Central site for centralized reporting and one located on a Primary site for redundancy.
We also implemented a custom reporting solution based on the customers request to build a reporting solution that also leveraged a in-house CMDB that was used as the source of authority for identifying computers, inventory and identification. The client had some interesting requirements for the type of reports desired and they had to accomplish the following:
Custom Software Update reports.
Develop a set of reports for monitoring Software Update deployments.
Enable report subscriptions for automating sending reports.
Enable reports to auto send to owners for servers they manage at deployment start date/time.
Enable reports to auto send to owners for servers they manage at deployment end date/time.
Enable reports to auto send deployment status based on errors triggered.
This give servers owners an early chance to identify and resolve issues sooner than later.
Enable reports to auto send to the right server owners based on server or service type.
Customized reports and subscriptions allowed the automation to trigger sending various reports based on different deployment actions. End-users and management will still have the option to setup and create their own subscription for any report stored in the SQL Reporting Service portal.