Overview
Windows Server Pods on ALYPOD are provisioned from a Windows template in the ALYPOD Console — you do not need to run the Windows setup wizard yourself. This article covers deploying, connecting and the first configuration tasks.
Before you begin
- An ALYPOD account at account.alypod.com.
- A Remote Desktop client (built into Windows; Microsoft Remote Desktop on macOS/Linux).
- A strong administrator password.
Steps
- Sign in to account.alypod.com and open the ALYPOD Console.
- Click Deploy Pod and choose a Windows plan.
- Select a region and a Windows Server template (for example 2019 or 2022).
- Set the administrator password (Windows licensing is handled by ALYPOD).
- Optionally add a cloud-init/unattend script if the template supports it.
- Create the Pod and wait for Running.
Connecting with RDP
- Copy the Pod's public IP from the console.
- From a Windows client:
powershell
mstsc /v:203.0.113.10
- Log in as
Administratorwith the password you set.
If RDP is not reachable, open the Pod's VNC console tab to see the Windows desktop directly.
First configuration
- Set the timezone:
powershell
Set-TimeZone -Id "UTC"
- Install updates:
powershell
Install-Module PSWindowsUpdate -Force
Get-WindowsUpdate -Install -AcceptAll -AutoReboot
- Enable and restrict the firewall so only your IP reaches RDP:
powershell
New-NetFirewallRule -DisplayName "RDP-Allow-Office" -Direction Inbound `
-Protocol TCP -LocalPort 3389 -RemoteAddress 198.51.100.7 -Action Allow
Security tips
- Never leave RDP exposed to the whole internet if you can whitelist your IP.
- Use long, unique administrator passwords and consider renaming the account.
- Take snapshots before major changes.
Troubleshooting
- Problem: RDP "cannot connect". Solution: confirm the Pod is running and use
the VNC console to check the firewall and the
TermService. - Problem: password rejected. Solution: reset it from the console, then reboot.
- Problem: activation warning. Solution: Windows images are licensed through ALYPOD; contact support via account.alypod.com if activation fails.
Related articles
- [Windows Pods explained]
- [Using the web console and VNC]
- [Initial server hardening after installation]
