Windows Operations

Bring PowerShell diagnostics and Windows Server workflows into the same conversation as your Linux estate. Inspect first, execute with the right identity and keep every result traceable.

PowerShell & services

Inspect service state, processes, scheduled tasks and event logs; execute explicit PowerShell tasks under the configured agent identity.

Roles & features

Plan supported Windows Server roles such as IIS, AD DS and DNS after checking the installed edition, prerequisites and existing configuration.

Directory & DNS

Investigate domain connectivity, DNS resolution and relevant service health. Domain operations need a deliberately configured identity with the right privileges.

Software workflows

Use available package managers or operator-approved installers. Record exit codes, product state and any reboot requirement.

Files & permissions

Create application directories, inspect ACLs and validate installation paths. Keep service-account privileges scoped to the target operation.

Microsoft 365 hand-off

Use the configured Graph integration for permitted tenant operations. The local SYSTEM account is not a Microsoft 365 administrator.

Workflow

Inventory

Identify OS edition, roles, identity and relevant event logs.

Check dependencies

Confirm tools, access and reboot implications.

Apply the task

Run the permitted PowerShell or installer operation.

Validate

Read service state, role installation and application response.

Example prompts

@win01 inspect failed services and recent critical events. Do not change configuration.
@winweb01 install IIS if missing, start W3SVC and verify localhost responds.
@dc01 inspect DNS resolution and AD-related service health without changing the domain.

Evidence

  • PowerShell output and exit status
  • Role or product installation state
  • Service and event-log checks
  • Documented reboot or credential blocker

Prerequisites

  • Windows agent installed with a supported Python runtime.
  • PowerShell and the relevant management modules available.
  • Explicit domain or tenant credentials where a local identity is insufficient.

Boundaries

Installers requiring interactive GUI, licensing or a reboot may need operator input. Domain promotion and tenant changes are not automatically safe merely because the local agent runs as SYSTEM.