Question Locked

Windows Server 2022 VM GPM

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am a student needing to setup a VM running Windows Server 2022 using VirtualBox. I have the VM set up, and must now access the Group Policy Management, but it says it requires a Domain User Account. What would I need to do to go about setting that up?

6 replies

by Wizard57M-TR

Sounds like it is time to study your text books. You should do this rather than ask in random forums on the internet. Your assignments and course work are designed to give you an introduction to various fields of endeavor. Successful completion will enhance your resume for future employment.

by rproffitt

1. Claude.
2. Chatgpt.
3. Reddit.

About Reddit. Wear your fire proof pants.

by Home Remodeling

You’ll need to set up Active Directory Domain Services (AD DS) first. Install the AD DS role on your Windows Server 2022 VM, promote the server to a domain controller, and create a new domain such as student.local. Then, use Active Directory Users and Computers to create a domain user account. Sign in with that account and open Group Policy Management. This will give you the domain environment required to create and manage Group Policies.

by oliviaparker09

If this is a lab VM, you’ll need to set up Active Directory first. Install the Active Directory Domain Services (AD DS) role, promote the server to a domain controller, and create a domain such as lab.local. Then create a user in Active Directory Users and Computers and log in with that domain account. After that, GPMC should let you manage the domain and create/edit GPOs.

by Aplle

You need to create a domain first. You can do this by installing Active Directory on your Windows Server. Then create a domain user account and use it to access Group Policy Management. Since you’re using VirtualBox, you can set everything up inside your VM.

by Noah Mitchell

That message is normal because Group Policy Management needs a domain to work against so a local account on its own will not do it. Before you promote the server give the VM a static IP and point its DNS at itself or promotion and later logons can get flaky. Then add the directory role through Server Manager and promote the machine to a domain controller for a small lab domain. Once that finishes sign in with a domain account and create a test user in the directory tools so you can check logon and policy from a member machine. Take a snapshot before you start the promotion too so you can roll back quickly if you mistype the domain name or the wizard fails partway through.

This discussion is closed to new replies.