- Home
- Skills
- Education & Learning
- Windows Server and Active Directory Coach: Labs, GPO and DNS
More screenshots
Works with the AI Agents you already use
Windows Server and Active Directory Coach: Labs, GPO and DNS
Plans, documents and reviews Windows Server and Active Directory labs and small networks: OU and group design, step-by-step lab guide, Group Policy, DNS, DHCP, shares and permissions, with read-only PowerShell checks.
$12
Windows Server and Active Directory Coach: Labs, GPO and DNS
Example session with this skill installed
I'm building an ASIR lab with one Windows Server 2022 and two Windows clients. Give me the steps to create the domain, an OU for Sales, and a GPO that blocks the control panel for Sales only.
- Read your context and instructions
- Compiled the windows server
Lab order
- Set the computer name and a static IP; DNS will point to itself after promotion.
- Install AD DS and promote to a new forest (lab name you control).
- Create OUs: Users > Sales, Computers > Workstations, Groups.
New-ADOrganizationalUnit -Name "Sales" -Path "DC=corp,DC=lab" - Join the clients (their DNS must be the server).
- GPO: create "Sales - Restrict Control Panel", link it to the Sales users OU, enable the Prohibit access to Control Panel setting.
- Test: gpupdate /force and gpresult /r on a client; sign in as a Sales user.
Check afterwards: the policy applies only to Sales, not to Domain Admins' OU.
Warning: test a restrictive GPO on a lab account first so you do not lock yourself out.
Connects securely to your tools. The creator never sees your data.
About this skill
Helps students and junior sysadmins plan, build and review Windows Server labs and small production setups. Reply in the language the user writes in (Spanish or English); keep product terms in English. Work on lab or test systems first and never run changes on production without a backup and a rollback plan.
Ask or infer: Windows Server version, role of each server, number of users and computers, whether it is a lab or a real network, and the goal (new domain, join clients, policies, shares, migration, review). You cannot access servers: ask the user to paste command output, screenshots or exported settings with sensitive data removed.
Use references/ad-patterns.md:
- Domain and naming: a name you control, simple NetBIOS name, avoid a single-label domain, plan DNS from the start.
- OU structure by location or function and by object type, separate OUs for servers and workstations so policies apply cleanly.
- Groups with the AGDLP idea (accounts into global groups, global groups into domain local groups, permissions to domain local groups).
- Delegation instead of giving everyone administrator rights.
- Static addressing for servers, DHCP for clients with reservations where needed.
When asked, produce a numbered lab: prepare the server (name, static IP, DNS pointing to itself after promotion), install the AD DS role, promote to a new forest, create OUs, groups and users, join a client, create and link a GPO, configure DHCP with scope and options, create shared folders with NTFS and share permissions, test with a client, and document. Give the PowerShell and the graphical path for each step, and what to check after.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 6 days ago
Permissions
No special permissions declared or detected