Windows Server Licensing — Bring Your Own License (BYOL)
This is an important notice for all customers using Windows Server templates on Cloud679.
⚠ Important: Cloud679 Windows Server templates are provided as evaluation images only. You must supply your own valid Microsoft license to use Windows Server in production. Cloud679 does not provide or include Windows Server licenses.
What is BYOL?
BYOL (Bring Your Own License) means you use a Microsoft Windows Server license that you already own or purchase separately. This is a standard practice when running Windows workloads on cloud infrastructure.
What Happens Without a License?
Windows Server will run in evaluation mode without activation, which means:
- The system will display a watermark on the desktop
- After the evaluation period (180 days), the system may shut down periodically
- Running unlicensed Windows Server software may violate Microsoft's terms of service
How to License Your Windows Server VM
Option 1 — Use an Existing License
If you already have a Windows Server license (e.g. from a volume licensing agreement), activate Windows using your existing product key:
- Connect to your VM via Remote Desktop
- Open Settings → System → About → Activate Windows
- Enter your product key
Option 2 — Purchase a New License
You can purchase Windows Server licenses from:
- Microsoft Volume Licensing
- An authorised Microsoft reseller in your region
- Microsoft Azure Hybrid Benefit (if you have Software Assurance)
Which License Do I Need?
| Template | License Required |
|---|---|
| Windows Server 2019 | Windows Server 2019 Standard or Datacenter |
| Windows Server 2022 | Windows Server 2022 Standard or Datacenter |
Adding a Network Card to Your Windows VM
⚠ Important: Due to a known limitation with Windows Server templates, the network configuration step is not shown during VM deployment. You will need to manually add a network card after your VM is created.
Steps to add a network card:
- Once your Windows VM is deployed, open it from the Virtual Machines list
- Click Edit Hardware
- Click Add Network Card
- Select Public Network from the network dropdown
- Set Model to e1000
- Set Connect to ON
- Click Save
- Start your VM — Windows will detect the new network card on first boot
???? Tip: Linux VMs do not have this limitation — the network card is configured automatically during deployment from the template wizard.
Need Help?
If you have questions about Windows licensing, contact your Microsoft reseller or visit microsoft.com/licensing. For Cloud679-specific questions, contact support@kastel.com.fj.
