Private corporate batches, live online cohorts and 1-on-1 mentoring in the Microsoft System Center suite — Configuration Manager, Operations Manager, Virtual Machine Manager, Orchestrator, Service Manager and DPM — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches Microsoft System Center as an operating estate rather than a product tour — site hierarchy and boundary-group design in Configuration Manager before any package is deployed, management-pack behaviour and override scoping in Operations Manager before any dashboard is drawn, and fabric and logical-network design in Virtual Machine Manager before any template is built. Sessions cover the failure paths engineers actually meet: task sequences that stop at the apply-image step, client health that reports green while nothing installs, alert storms caused by an untuned management pack, and DPM recovery points that exist but cannot be restored. Automation is taught in PowerShell and Orchestrator runbooks throughout, and every module is mapped to its Azure counterpart — Intune co-management, Azure Arc and Azure Monitor — so the estate has a forward path.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Microsoft System Center that means a trainer who has run it in production — the Microsoft System Center suite — Configuration Manager, Operations Manager, Virtual Machine Manager, Orchestrator, Service Manager and DPM — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Microsoft System Center batchMicrosoft System Center is a suite of enterprise management products for building, deploying, monitoring, protecting and automating a Windows-centric infrastructure estate. It is not one application: each component has its own database, its own agent model and its own administration surface, and the engineering skill lies in knowing which component owns which problem and how they hand off to each other.
Configuration Manager — long known as SCCM and now branded Microsoft Configuration Manager — handles device management: site hierarchies, boundary groups, collections, software distribution, operating system deployment through task sequences, software update management via WSUS, and configuration baselines for compliance. Operations Manager (SCOM) does health monitoring through management packs, agents reporting to management servers, overrides that tune monitors, and dashboards and alerting on top. Virtual Machine Manager (SCVMM) manages the virtualisation fabric: Hyper-V hosts, failover clusters, logical networks, VM templates and private clouds. Data Protection Manager (DPM) provides disk-to-disk backup for Windows workloads.
Orchestrator and Service Manager complete the suite on the process side. Orchestrator builds runbooks that chain actions across systems, and Service Manager provides the incident, change and CMDB layer that connects monitoring alerts to a workflow with an owner. In current estates all of this increasingly coexists with cloud counterparts — Azure Arc extending management to non-Azure machines, Intune co-management alongside Configuration Manager, and Azure Monitor consuming what SCOM used to be the only source of.
Very large numbers of Windows devices and servers are still managed by Configuration Manager, and Operations Manager still carries monitoring for estates where agent-based, on-premises health data is a regulatory or network requirement. Those systems do not disappear because a cloud alternative exists; they get connected to it, and someone has to own the seam.
That is where the current demand sits. Co-management with Intune, Azure Arc onboarding for servers that will never move, hybrid patching strategy, and migrating SCOM monitoring into Azure Monitor without losing the coverage a decade of management packs represents — these are all projects that require someone who genuinely understands the System Center side before they can be modernised.
The supply problem is real. The engineers who built these hierarchies are retiring or have moved to cloud roles, and newer engineers arrive knowing Intune and Azure Monitor but not why a boundary group is configured the way it is, what an override actually does, or how a task sequence fails. Depth here is unusually valuable precisely because it is unfashionable.
What each component owns, what it does not, and how they connect. Database and SQL Server requirements for each product, sizing and placement decisions, service accounts and least privilege, and the licensing and lifecycle position that determines whether you are extending an estate or planning its exit.
Topics: Component map: Configuration Manager, SCOM, SCVMM, Orchestrator, Service Manager, DPM · SQL Server requirements, collation, sizing and placement per component · Service accounts, least privilege and the accounts each product needs · Certificates, PKI and HTTPS communication across the suite · Sizing, scale limits and where hierarchies actually break · Lifecycle, current-branch servicing and support position · Where Azure counterparts overlap: Intune, Arc, Azure Monitor, Azure Backup
The foundation that every later Configuration Manager feature stands on. Site hierarchy and site system roles, discovery methods and what each one actually finds, boundaries and boundary groups including fallback behaviour, client installation methods, and client health as an engineering problem rather than a dashboard colour.
Topics: Site types, site system roles and role placement · Discovery methods: AD system, user, group, network, heartbeat · Boundaries, boundary groups, fallback and content lookup order · Client installation: push, GPO, manual, imaging, cloud · Client settings, policy polling and client cache management · Client health evaluation, ccmsetup and CCMEval diagnostics · Collections: query rules, include and exclude, limiting collections · Distribution points, content distribution and peer cache
Getting software onto devices predictably. The application model versus packages, detection methods and requirement rules, deployment types and supersedence, then software update management through WSUS with maintenance windows, automatic deployment rules and servicing — and configuration baselines for proving compliance.
Topics: Application model: deployment types, detection methods, requirements · Packages and programs, and when they are still the right answer · Supersedence, dependencies and uninstall behaviour · Software update point, WSUS synchronisation and update groups · Automatic deployment rules, maintenance windows and deadlines · Windows servicing, feature updates and Delivery Optimization · Configuration items, baselines and compliance reporting · Endpoint protection and Defender policy through the console
Task sequences, the highest-value and highest-frustration part of the product. PXE and boot images, driver management done properly, image capture and servicing, the task sequence steps and variables that make a build dynamic, and the diagnostic method for a sequence that fails at 4am in a build room.
Topics: Boot images, PXE, WDS and network boot troubleshooting · Driver packages, driver catalogues and model-specific handling · Image capture, offline servicing and reference image strategy · Task sequence steps, groups, conditions and variables · Bare metal, refresh and in-place upgrade scenarios · User state migration with USMT and state stores · Task sequence logging: smsts.log and reading it correctly · BitLocker, TPM and secure boot considerations during deployment
How SCOM actually decides something is unhealthy. Management group architecture and resource pools, agent deployment and agent-managed versus agentless, then management packs: what they contain, how discoveries populate the object model, and how monitors and rules differ in a way that matters every single day.
Topics: Management group architecture, management servers and resource pools · Operational, data warehouse and ACS databases · Agent deployment, agent failover and gateway servers · Management pack structure: discoveries, monitors, rules, views · Classes, objects, health model and state roll-up · Monitors versus rules and why alerts appear or do not · Sealed and unsealed packs, and where overrides must be stored · Cross-platform and network device monitoring
Turning raw monitoring into something on-call engineers trust. Override scoping and the discipline of storing them correctly, tuning a noisy pack down to actionable alerts, authoring custom monitors and rules for applications no pack covers, distributed applications, and reporting from the data warehouse.
Topics: Override targets, scoping and override management packs · Alert tuning method: noise inventory, thresholds, and closing loops · Authoring custom monitors, rules and unit monitors · Script-based and PowerShell monitoring · Distributed applications and service-level modelling · Notifications, subscriptions and on-call routing · Dashboards, views and web console usage · Data warehouse reporting and availability reports
Managing virtualisation as a fabric rather than as individual hosts. Host groups and clusters, logical networks and the VM network abstraction that confuses most newcomers, storage classifications, templates and profiles, private clouds with delegated access, and live migration and placement behaviour.
Topics: Host groups, Hyper-V hosts and failover cluster management · Logical networks, network sites, VM networks and uplink port profiles · Logical switches, port classifications and host network configuration · Storage: classifications, pools, file shares and clustered volumes · VM templates, hardware and guest OS profiles, service templates · Private clouds, capacity and delegated self-service · Placement, live migration, dynamic optimization and power optimization · Bare-metal host deployment from VMM
The process and protection half of the suite. Orchestrator runbooks with integration packs, published data and error handling; Service Manager work items, the CMDB and connectors that pull data from the other components; and DPM protection groups, recovery points and restores you have actually performed.
Topics: Orchestrator architecture, runbook servers and integration packs · Runbook design: activities, links, published data, looping, error branches · Invoking runbooks from alerts, requests and PowerShell · Service Manager work items: incident, change, service request, release · CMDB, connectors from Configuration Manager, SCOM and Active Directory · Service catalogue, request offerings and approval workflow · DPM protection groups, short-term disk and long-term retention · Recovery scenarios: files, SQL, virtual machines and bare metal
Running System Center for the long term and connecting it to what comes next. PowerShell modules for each component, reporting and SQL access, backup and disaster recovery of the management infrastructure itself, current-branch upgrades, and a realistic modernisation path through co-management, Azure Arc and Azure Monitor.
Topics: PowerShell modules for Configuration Manager, SCOM, SCVMM and DPM · Automating routine administration and bulk operations safely · Reporting Services, SQL queries and custom reports · Backing up and recovering the management infrastructure itself · Current-branch and update-rollup upgrade procedures · Intune co-management: workload sliders and phased migration · Azure Arc onboarding for servers and Azure Monitor agent migration · Deciding what to modernise, what to keep, and what to retire
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild a Configuration Manager site with discovery, boundary groups, distribution points and healthy clients, then prove content fallback works as designed.
Build a bare-metal task sequence, inject three realistic failures, and diagnose each from smsts.log without opening the console.
Take a management group generating hundreds of daily alerts, inventory the noise, apply correctly scoped overrides, and document every one.
Build logical networks, sites and uplink port profiles in Virtual Machine Manager so a template deployment lands on the right VLAN with no manual step.
Protect a SQL database and a virtual machine with DPM, destroy both, and perform timed recoveries against a documented objective.
Wire a SCOM alert through an Orchestrator runbook into a Service Manager incident, remediate automatically, and close the loop with an audit trail.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
My experience with the AIOps training was positive. The course covered important topics in a structured way, and Rajesh Kumar explained the concepts patiently. I found the practical aspects particularly helpful because they made the technical content easier to understand.
I was looking to improve my understanding of AIOps, and this training helped me achieve that goal. Rajesh Kumar explained the subject in a structured and practical manner. The sessions on different AIOps concepts were informative.
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.