Windows Server & Enterprise Infrastructure Listing Assistant

---
name: windows-servers-networking-listing
description: "This skill produces an organized, Windows-focused inventory list of enterprise infrastructure components. Use when the user asks for “Windows list of servers”, “Windows modules”, “Windows server roles”, “what Windows components exist”, “Microsoft Windows Server inventory”, or when they request coverage of specific Windows Server elements like Active Directory, DNS, DHCP, RDS, WSUS, Hyper-V, Failover Clustering, SCCM, Intune, Azure DevOps, Defender for Endpoint, or Power BI."
---
Build a Windows enterprise/server inventory list.

Workflow:
1) Start from the user’s requested scope: “Windows servers”, “Windows modules”, “Windows roles/features”, “Citrix/VMware”, “firewalls/switches/routers”, “Linux enterprise flavours”, “NAS”, etc.
2) Always include Microsoft Windows Server and then list Windows Server modules/roles that the user asked for or that were mentioned in the request.
3) If the request includes endpoints/device management, add Microsoft Intune, Microsoft Endpoint Manager, and related management items.
4) If the request includes virtualization, add Microsoft Hyper-V.
5) If the request includes identity, add Microsoft Active Directory plus AD DS and Azure Active Directory/Azure AD items only if explicitly requested.
6) If the request includes clustering/high availability, add Microsoft Failover Clustering.
7) If the request includes deployment/patching, add WSUS and SCCM only when requested or when the user says “server management/patching”.
8) If the request includes networking, include DHCP Server and DNS Server and Network Policy and Access Services (NPAS) only if “networking roles” are requested.
9) If the request includes admin consoles, add Windows Admin Center.
10) If the request includes storage/file services, include File and Storage Services.
11) If the request includes remote access, include Remote Desktop Services (RDS).
12) Output as clear sections with bullet lists.

Defaults & validation:
- Default to Windows Server + the Windows modules/roles explicitly provided in the mission brief when the user asks for “Windows list”.
- Do not add components not present in the mission brief.
- If the user asks for Citrix/VMware/firewalls/switches/routers/Linux NAS, list placeholders only as categories; do not invent brand products.

Example output (when asked “Windows list of servers and modules”):
- Servers: Microsoft Windows Server; (and include Microsoft System Center Configuration Manager (SCCM), Microsoft Hyper-V, Microsoft Failover Clustering, Microsoft SQL Server, etc. as provided)
- Server roles/modules: AD DS; DHCP Server; DNS Server; File and Storage Services; RDS; WSUS; NPAS; Network Policy and Access Services; Windows Server Core; Hyper-V; Failover Clustering.