Private corporate batches, live online cohorts and 1-on-1 mentoring in Windows Server for infrastructure engineers — Active Directory, Group Policy, PowerShell remoting, IIS, Hyper-V and Windows build agents — 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 Windows for engineers who have to automate it rather than click through it: the service, registry and event-log model that every diagnosis starts from, Active Directory and Group Policy design, PowerShell as an object pipeline with remoting over WinRM and Desired State Configuration for declarative state, IIS and application hosting, Hyper-V and Windows containers, and the patch, monitoring and hardening work that keeps an estate defensible. Windows is treated as a full participant in a DevOps toolchain — Ansible over WinRM, Windows build agents, MSBuild and MSI packaging, Chocolatey and WSL.
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 Windows that means a trainer who has run it in production — Windows Server for infrastructure engineers — Active Directory, Group Policy, PowerShell remoting, IIS, Hyper-V and Windows build agents — 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 Windows batchWindows, in an infrastructure context, means Windows Server and the identity, hosting and management stack built around it. The kernel is a hybrid design with a hardware abstraction layer, an executive providing object management, memory management and I/O, and a user mode where services, drivers and applications live. Configuration is centralised in the registry, background work runs as services under the Service Control Manager, and everything of consequence is recorded in the event log — which is why the first three places to look during any Windows incident are services, events and performance counters.
The distinguishing feature of a Windows estate is Active Directory. Identity, authentication, authorisation and configuration are all delivered through a directory: domains and forests define trust boundaries, organisational units structure objects, Kerberos issues tickets, and Group Policy pushes machine and user configuration to thousands of endpoints without touching any of them individually. Around that sit DNS and DHCP as hard dependencies, certificate services for internal PKI, and file and print services. Getting Active Directory design right determines whether the estate is manageable; getting it wrong is expensive to unwind.
For engineers arriving from a Linux or cloud background, the important shift is that Windows automation is object-based rather than text-based. PowerShell returns structured objects rather than strings, remoting runs over WinRM, and Desired State Configuration expresses target state declaratively. That is what makes Windows a first-class participant in a DevOps estate — Ansible over WinRM, Windows build agents, MSBuild and MSI packaging, Chocolatey for package management, Windows containers, and Windows Subsystem for Linux where a Linux toolchain is genuinely the right answer.
Most enterprises are mixed estates, and the automation and reliability practice that matured on Linux is now expected to cover the Windows half as well. Teams that have containerised their Java services still have domain controllers, file servers, IIS applications and .NET build agents, and those need the same treatment: configuration as code, patch automation, monitored recovery and least-privilege access.
The hiring gap sits precisely there. There are plenty of Windows administrators who work through the graphical console and plenty of DevOps engineers who avoid Windows entirely. What organisations need are engineers who can do both — script a domain build in PowerShell, run Ansible against Windows hosts, put a Windows CI agent in a pipeline, harden a server against a real baseline, and diagnose a failure with Sysinternals rather than by rebuilding the box.
Security has sharpened this further. Active Directory is the primary target in most enterprise intrusions, and credential theft, privilege escalation and lateral movement are Windows-specific disciplines. Understanding Kerberos, delegation, privileged access design, credential protection and audit logging has become a core infrastructure skill rather than a specialist security one.
How the operating system is actually put together, because every later diagnosis depends on it. Kernel and user mode, the executive subsystems, processes and services, the registry as configuration store, the boot and startup path, and the editions and installation options including Server Core.
Topics: Kernel mode, user mode and the executive subsystems · Processes, threads, handles and objects · Services and the Service Control Manager · The registry: hives, keys, permissions and where configuration really lives · Boot sequence, startup and recovery options · Editions, licensing and Server Core versus Desktop Experience · Filesystems: NTFS, ReFS, permissions and inheritance · Event log architecture and where to look first
The day-to-day surface. Roles and features, local users and groups, storage from disks through Storage Spaces to shares, file services and permission models, scheduled tasks, and the management tooling that scales beyond one server.
Topics: Roles and features, and installing them without the wizard · Local users, groups and built-in privileges · Disks, volumes, Storage Spaces and ReFS · File shares, SMB, share versus NTFS permissions · Distributed File System and replication · Scheduled tasks and task scheduler security · Server Manager, remote management and Windows Admin Center · Backup and system state recovery
The centre of any Windows estate. Domains, trees, forests and trusts, domain controllers and replication, the organisational unit structure that makes delegation possible, DNS and DHCP as hard dependencies, and the authentication protocols underneath — Kerberos, tickets, service principal names and delegation.
Topics: Domains, trees, forests, trusts and functional levels · Domain controllers, global catalog and FSMO roles · Replication, sites and subnets · Organisational unit design and administrative delegation · DNS integration and the records Active Directory depends on · DHCP, scopes, reservations and failover · Kerberos: tickets, SPNs, constrained and unconstrained delegation · Accounts: user, computer, service, managed service accounts · Certificate services and internal PKI basics
Configuration management for the Windows estate. How policy objects are processed and merged, linking and inheritance, security filtering and WMI filters, preferences versus policies, loopback processing, and the systematic method for finding out why a setting did not apply.
Topics: Group Policy objects, links, scope and processing order · Inheritance, blocking, enforcement and precedence · Security filtering and WMI filtering · Group Policy preferences and item-level targeting · Loopback processing and when it is required · Administrative templates and central store · Security settings, restricted groups and audit policy · Diagnosing with gpresult, Resultant Set of Policy and the operational log · Backup, version control and change management for policy
Windows automation done properly. The object pipeline and why it differs from text-based shells, modules and discovery, error handling, remoting over WinRM including sessions and delegation, and Desired State Configuration for declarative, drift-resistant server state.
Topics: The object pipeline: objects, properties, filtering and formatting · Cmdlet discovery, modules and the PowerShell Gallery · Variables, scripts, functions and parameter validation · Error handling, streams and transcripts · PowerShell remoting: WinRM, sessions, fan-out and the double-hop problem · Just Enough Administration and constrained endpoints · Desired State Configuration: resources, configurations and drift · Execution policy, script signing and logging
Serving applications from Windows. Host networking and firewall configuration, then IIS in depth — sites, bindings, application pools and their identities, certificates and TLS, ARR and load balancing, plus hosting .NET applications and the failures specific to pool recycling and identity.
Topics: Network configuration, name resolution and Windows Firewall rules · IIS architecture: worker processes, application pools, modules · Sites, bindings, host headers and TLS certificates · Application pool identity, recycling and idle timeout · Hosting .NET Framework and .NET applications · Request tracing, failed request logging and diagnostics · Application Request Routing and load balancing · Network Load Balancing and connection draining
Running workloads on Windows Server. Hyper-V virtual machines and virtual switching, failover clustering with cluster shared volumes and live migration, then Windows containers — process versus Hyper-V isolation, base images and the version-matching rules that trip everyone up.
Topics: Hyper-V roles, generation 1 and 2 virtual machines, dynamic memory · Virtual switches and network configuration for guests · Checkpoints and their production caveats · Failover clustering: quorum, witness, cluster shared volumes · Live migration and rolling cluster upgrades · Windows containers: process isolation versus Hyper-V isolation · Base images, version compatibility and image size · Running Windows containers under Docker and Kubernetes
Keeping an estate healthy and diagnosing it when it is not. Update management and maintenance windows, performance counters and data collector sets, event log analysis at scale, the Sysinternals tool set, and structured approaches to hangs, leaks, high CPU and crash dumps.
Topics: Update management, maintenance windows and reboot orchestration · Performance counters, data collector sets and baselines · Event log analysis, forwarding and centralised collection · Sysinternals: Process Explorer, Process Monitor, Autoruns, Handle · Diagnosing high CPU, memory leaks and handle leaks · Crash dumps, memory dumps and basic analysis · Windows Error Reporting and reliability history · Network capture and connectivity troubleshooting
Making Windows defensible and making it part of the delivery toolchain. Least privilege and tiered administration, credential protection against theft and lateral movement, hardening baselines and audit, then Ansible over WinRM, Windows build agents, packaging and WSL.
Topics: Least privilege, tiered administration and privileged access workstations · Credential theft, pass-the-hash and lateral movement defences · LAPS, Credential Guard and protected users · BitLocker, secure boot and platform integrity · Security baselines, benchmarks and measured hardening · Audit policy, log retention and evidence · Ansible against Windows over WinRM · Windows build agents in Jenkins and other CI systems · MSBuild, MSI packaging and Chocolatey · Windows Subsystem for Linux and when it is the right tool
We rebuild the agenda around the tools you actually run.
Request a custom agendaBuild a two-controller domain entirely in PowerShell — no wizards — then verify replication, FSMO placement and delegated administration through an organisational unit design.
Deliver a hardening baseline through Group Policy, then diagnose three deliberately broken applications caused by filtering, precedence and loopback respectively.
Write a Desired State Configuration for a web host, apply it, introduce drift by hand, and prove the configuration restores the intended state.
Host two applications with separate pool identities and TLS bindings, prove they cannot reach each other's resources, then diagnose a failure that only appears after pool recycle.
Capture a performance baseline, induce a memory and handle leak, and identify the responsible process and call path using Process Explorer, Process Monitor and counters.
Harden a Windows host to a baseline, manage it with Ansible over WinRM, attach it as a build agent, and produce a signed MSI from the pipeline.
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
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.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
| 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.