Technical notes by area
Active Directory and Windows
Securing and running Active Directory: a tiering model for privileged accounts, Windows LAPS and emergency access accounts, FSMO roles, system state backup and forest recovery. Workstation management through Group Policy and Windows update rings, and SQL Server in the domain: gMSA, Kerberos, backups.
-
Privileged accounts in Active Directory
A three-tier model, separate administrative accounts, Windows LAPS, emergency access accounts and a reversible procedure for removing inactive objects. Protecting domain administrator credentials without a PAM system.
-
Maintaining and recovering Active Directory
FSMO roles and functional levels, system state backup and four ways to restore the directory, forest recovery, and signing tools in with a domain account over LDAPS or OIDC.
-
Workstation management
Dividing settings between Group Policy and an endpoint management tool, the workstation standard (image, packages, BitLocker, user data) and Windows update deployment rings.
-
SQL Server in a domain environment trial
Edition selection, the gMSA service account, connections to named instances (SQL Browser, SPN, Kerberos, certificate), logins and roles, transaction log truncation, and backups without SQL Server Agent in an Active Directory domain.
Microsoft 365 and Azure
Hybrid identity: synchronisation with Entra ID, sign-in methods, MFA, Conditional Access and roles with PIM. Email in Exchange Online (SPF, DKIM, DMARC, quarantine, retention) and Azure administration: RBAC, service principals, managed identities and Key Vault.
-
Hybrid identity and access to Microsoft 365
Synchronising Active Directory with Entra ID, sign-in methods (PHS, PTA, federation), passwords and MFA, the Conditional Access baseline set, and administrative roles with PIM. A coherent hybrid identity model without unnecessary dependence on on-premises servers.
-
Email in Microsoft 365
Rolling out SPF, DKIM and DMARC without blocking legitimate mail, quarantine policies in Exchange Online, the split between Purview and MRM in retention, and connecting applications that send plain SMTP.
-
Azure from the administrator’s side
RBAC and custom roles, app registrations and service principals, managed identities including servers with Azure Arc, and Key Vault with roles, a firewall and an audit log. Permissions, credentials and secrets in Azure without keys in configuration.
Network and core services
Network segmentation with zones and default deny, two internet links with health checks (SD-WAN) and vendor access through a gateway with session recording. DNS resilient to resolver failure, and certificate inventory and monitoring.
-
Network: segmentation, links and external access
A zone plan and flow matrix with default deny, health checks for two internet links with a plan for services tied to the address, and a session-recording gateway with time-limited accounts for external vendors.
-
Core services: DNS and certificates
DNS resilience against the failure of a single resolver, forwarder or Kubernetes cluster network, and certificate inventory and monitoring with alert thresholds matched to the renewal method.
Virtualisation and continuity
Hyper-V: workload placement, VHDX disks and checkpoints. 3-2-1 backups with an immutable copy and restore testing, Kubernetes cluster backups, and a first-hour outage procedure. Monitoring with actionable alerts (Zabbix) and Windows event logs (Graylog).
-
Hyper-V virtualisation
Placing workloads between virtual machines and Kubernetes, preparing node machines, VHDX disk growth, and how Hyper-V checkpoints work and where they stop being a safeguard.
-
Backups and outage handling
RPO and RTO, the 3-2-1 rule with an immutable copy, a restore test protocol, Kubernetes cluster backups (etcd in k3s, Velero) and the first-hour outage procedure: lead, messages, rollback and escalation.
-
Monitoring and event logs
Choosing metrics and building alerts that require action, and a strategy for Windows event logs: which events to collect, how to filter and process them, and how long to keep them.
Kubernetes and automation
A highly available k3s cluster with etcd quorum and a shared API address. CI/CD in GitLab with one pipeline template, versioned images and GitOps deployments. Automating administration: Ansible and AWX, PowerShell scripts, request fulfilment.
-
Highly available Kubernetes cluster
k3s etcd quorum, pod and data behaviour after a node failure, disruption budgets and a shared API address (kube-vip, keepalived, external load balancer) with diagnosis of address flapping.
-
CI/CD and declarative deployments
One versioned pipeline template in GitLab CI, immutable image tags carrying the version and commit hash, and deployment through a reconciliation loop in Argo CD instead of a script.
-
Automating administration
The scope of Ansible and the repository layout, PowerShell scripts run from Task Scheduler, and fulfilling requests through AWX or Ansible Automation Platform.