Overview

Windows Pods are ALYPOD compute instances that run Microsoft Windows Server. They are managed entirely from the ALYPOD Console, with Remote Desktop (RDP) for access. This article explains how Windows licensing, images and access work.

What you get

• Windows Server images (selectable during deployment), licensed through ALYPOD.
• RDP access over a public IPv4 address using the credentials you set at deploy time.
• Full administrator rights, so you can install any compatible Windows software.
• The same power, snapshot, resize and rescue controls as Linux Pods.

Choosing Windows

Use a Windows Pod when you need:

• Microsoft SQL Server, IIS, or .NET/ASP.NET applications.
• Remote desktop workstations or jump hosts.
• Windows-only line-of-business software.

For web hosting on a budget, a Linux Pod is usually cheaper and lighter.

Deploying and connecting

1. In the ALYPOD Console, click Deploy Pod and select a Windows template.
2. Choose the resource plan and set an administrator password.
3. Wait for the status to become Running.
4. Connect with RDP:

```powershell

From Windows, open mstsc.exe

mstsc /v:203.0.113.10 ```

From macOS/Linux use the Microsoft Remote Desktop client.

Good practices

• Enable the built-in firewall and restrict RDP (3389) to your own IP where possible.
• Keep Windows Update enabled and reboot during a maintenance window.
• Store important data off the Pod using snapshots or an S3 bucket.

Troubleshooting

• Problem: RDP refuses to connect. Solution: confirm the Pod is running, then use the console VNC tab to check the Windows firewall and RDP service.
• Problem: slow first login. Solution: Windows profiles can take time to build; subsequent logins are faster.

Related articles

• [Installing Windows Server]
• [Using the web console and VNC]
• [Power management: start, stop and reboot]