How to Set Up Active Directory on a Windows VPS for Small Business

For small businesses moving to the cloud, setting up Active Directory (AD) on a Windows VPS is a cost-effective way to centralize user management, enforce security policies, and enable single sign-on — without the expense of on-premises hardware or Azure Active Directory Premium. With a Windows VPS, you can run a full domain controller in the cloud for a fraction of the cost. This guide walks through the entire setup process, from provisioning the VPS to promoting it as a domain controller. If you need help choosing a provider, see our Windows VPS comparison table.

Why Use a Windows VPS for Active Directory?

Active Directory is the backbone of Windows-based networks. It handles authentication, authorization, group policies, and directory services. Running AD on a Windows VPS offers several advantages for small businesses:

• No hardware investment — No need to buy and maintain physical servers.
• Always-on availability — Data centers provide redundant power, cooling, and networking.
• Scalable — Start small and upgrade CPU/RAM as your organization grows.
• Remote access — Users can authenticate from anywhere via VPN or DirectAccess.
• Disaster recovery — Snapshots and backups are built into most VPS platforms.

Prerequisites

• A Windows VPS with at least 2 vCPUs and 4 GB RAM (8 GB recommended for production).
• Windows Server 2022 or 2025 Standard Edition (Datacenter edition also works).
• A static public IP address (most VPS providers include this).
• A domain name you own (e.g., yourcompany.local for internal or a public domain).
• Administrator access to the VPS via RDP.

Step 1: Provision Your Windows VPS

Deploy a Windows Server 2025 VPS from your provider. During deployment, pay attention to these settings:

• Choose a datacenter close to your team for the lowest latency.
• Select SSD NVMe storage for better AD database performance.
• Attach an additional virtual disk (20–50 GB) for the AD database, logs, and SYSVOL — it’s best practice not to use the OS drive for AD data.

For a reliable and affordable Windows VPS, consider InterServer Windows VPS (promo code TRYINTERSERVER) or Vultr for flexible hourly billing.

Step 2: Initial VPS Setup

1. Connect via RDP using the Administrator credentials.
2. Run Windows Update and install all critical updates. Reboot if needed.
3. Set a static IP address on the VPS network adapter (use the same IP as assigned by your provider).
4. Configure the DNS server to point to 127.0.0.1 (temporarily — you’ll install DNS later as part of AD DS).
5. Change the Administrator password to a strong, unique password.

Step 3: Install Active Directory Domain Services (AD DS)

There are two ways to install AD DS: via Server Manager (GUI) or PowerShell. We’ll cover both.

Method A: Using Server Manager (GUI)

1. Open Server Manager > Manage > Add Roles and Features.
2. Select Role-based or feature-based installation.
3. Select your server from the server pool.
4. Check Active Directory Domain Services and click Add Features when prompted.
5. Click Next through the remaining steps and click Install.

Method B: Using PowerShell

Open PowerShell as Administrator and run:

Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools

This installs the AD DS role and management tools like Active Directory Users and Computers.

Step 4: Promote to a Domain Controller

After installing AD DS, you need to promote the server to a domain controller. This creates a new forest (if this is your first domain controller).

GUI Method:

1. Click the notification flag in Server Manager and click Promote this server to a domain controller.
2. Select Add a new forest and enter your root domain name (e.g., contoso.local).
3. Set the Directory Services Restore Mode (DSRM) password — store this somewhere secure.
4. Leave the DNS options at defaults (the wizard will install DNS automatically).
5. Accept the NetBIOS name suggestion.
6. Specify the database, log files, and SYSVOL paths — point them to your secondary drive if you added one.
7. Click Next and then Install. The server will reboot automatically.

PowerShell Method:

# Import the AD DS deployment module
Import-Module ADDSDeployment

# Create a new forest
Install-ADDSForest `
    -CreateDnsDelegation:$false `
    -DatabasePath "E:\NTDS" `
    -LogPath "E:\NTDS" `
    -SysvolPath "E:\SYSVOL" `
    -DomainName "contoso.local" `
    -DomainNetbiosName "CONTOSO" `
    -SafeModeAdministratorPassword (Read-Host -AsSecureString "Enter DSRM Password") `
    -Force:$true

After the reboot, log in with your domain Administrator account (CONTOSO\Administrator).

Step 5: Create Users and Groups

Now that your domain controller is running, create your organizational structure:

1. Open Active Directory Users and Computers from Server Manager or the Tools menu.
2. Right-click your domain and create Organizational Units (OUs) to organize your users, computers, and groups (e.g., Employees, IT, Computers).
3. Create users by right-clicking an OU and selecting New > User.
4. Create security groups for permissions management.

Step 6: Configure Group Policies

Group Policy is one of the most powerful features of AD. Use it to enforce security settings across all domain-joined computers:

• Password Policy — Set minimum password length, complexity requirements, and expiration.
• Account Lockout Policy — Lock accounts after 5 failed attempts to prevent brute force attacks.
• Software Restriction Policies — Block unauthorized software from running.
• Windows Update Configuration — Force automatic updates.

Open Group Policy Management from the Tools menu, create a new GPO, link it to your domain or OUs, and edit the settings.

Step 7: Join Client Computers to the Domain

For client machines to authenticate against your cloud AD, they need network connectivity to the VPS:

1. Set up a VPN (using SSTP or L2TP on the Windows VPS) so client computers connect securely to your private network.
2. On each client, go to Settings > About > Rename this PC (Advanced).
3. Click Change under “To rename this computer or change its domain.”
4. Select Domain and enter your domain name (contoso.local).
5. Enter domain administrator credentials when prompted, then reboot.

Step 8: Configure Backup and Disaster Recovery

Your Active Directory database is critical infrastructure. Set up these protections:

• Windows Server Backup — Schedule a daily system state backup (this includes the AD database, registry, and SYSVOL).
• VPS Snapshots — Take a snapshot before every major change.
• Second domain controller (advanced) — For redundancy, provision a second Windows VPS and add it as an additional domain controller. This provides failover if the primary goes down.

Conclusion

Setting up Active Directory on a Windows VPS gives your small business enterprise-grade identity management without the enterprise price tag. With a properly configured domain controller, you can centralize user accounts, enforce security policies, and simplify network management — all from a cloud-based server that costs between $20 and $80 per month. For help choosing a VPS provider with the right specs for your AD deployment, check out our Windows VPS comparison page.