WAL Deployment Playbook

Sage 50 Multi-User Deployment Playbook

Target: Windows Server 2019 Standard VM on Proxmox VE
Users: Up to 5 concurrent Sage 50 users + admin access
Support: Fully Microsoft-supported + legally licensed


1. Hardware Setup

Core Components

Component Spec / Recommendation
CPU AMD Ryzen 5/7 or Intel i5/i7 (6–8 cores)
RAM 32 GB DDR4
Storage 1 TB NVMe SSD (for VM)
Host Boot Disk 128 GB SATA SSD (for Proxmox OS)
Network Intel Gigabit Ethernet NIC
Case/Power Quiet Mini PC or micro-ATX case + 80+ Bronze PSU
UPS APC Back-UPS 700VA or similar
Backup Drive 1 TB external USB SSD for VM backups

Optional

Accessory Benefit
ZFS Filesystem Built-in redundancy and snapshotting
Quiet Cooling Ideal for shared or office environments

Cost around £500 or so

2. Hypervisor: Proxmox VE

  • Install latest Proxmox VE on boot SSD
  • Create a VM:
    • 16–24 GB RAM
    • 4+ vCPUs
    • 150–250 GB NVMe virtual disk
    • Enable UEFI and QEMU guest agent
  • Enable snapshot & backup options

3. Windows Server 2019 VM Setup

Licensing

Licence Vendor Price (GBP) Notes
Server 2019 Std Currys Business £425.53 16-core OEM
5 User CALs Ebuyer £139.99 For shared file/app access
5 RDS User CALs Trusted Tech Team UK £510.99 For concurrent RDP sessions

**Cost around £1,000 or so

**Total costs around £1,500 and under £2,000

Installation Steps

  • Install Windows Server 2019
  • Join workgroup or domain if applicable
  • Activate all licences
  • Configure static IP and hostname
  • Install Sage 50 software centrally

4. User Access Configuration

RDS Setup

  • Install Remote Desktop Services role
  • Configure 5 RDS User CALs
  • Create 5 user accounts with strong passwords
  • Use Group Policy to lock down environment if needed

Admin Access

  • Use mstsc /admin for console session (Session ID 0)
  • Alternatively use Proxmox web console for out-of-band access

5. Backup & Restore

  • Set up scheduled Proxmox VM backups (ZFS or directory)
  • Export regular Sage backups to external USB SSD
  • Test snapshot and restore procedures monthly

6. Maintenance & Best Practices

  • Use Windows Update and enable reboots during low-use periods
  • Apply Proxmox updates via web UI monthly
  • Use Console access to avoid burning RDS CALs for admin
  • Keep one local admin user reserved for recovery

7. Optional: Secure Remote Access

  • Use Cloudflare Tunnel or VPN to avoid open ports
  • Allow only RDP via secure tunnel
  • Disable direct internet exposure to RDP port

Appendix: Console Access

What Is It?

  • The local screen/session of the server (Session 0)

How to Use It

```bash mstsc /admin

May 18, 2025


Previous post
Talk draft 2 We met when he was ten and I was twelve, and we were friends for the next fifty-six years. I think I’ve done many things only because Tim dragged me
Next post
WAL Linux VM Proxmox includes Debian (and is a Linux system) — and that’s actually a huge win: ⸻ ✅ Why Proxmox Includes Debian Linux Reason Explanation