Twingate Hyper-V Connector
Problem
Some environments - particularly in manufacturing, operations, and traditional enterprise IT - run entirely on Windows Server infrastructure with no Linux hosts available. The Twingate connector is Linux-based, which left these environments without a viable deployment path. Asking these customers to provision and manage a Linux server from scratch was a significant barrier that blocked Twingate adoption entirely.
Approach
Built PowerShell scripts that automate end-to-end connector provisioning on Windows Server via Hyper-V. The primary script (Deploy-TwingateConnector.ps1) handles API-driven connector record creation via the Twingate API, provisions Ubuntu 24.04 Gen2 VMs with cloud-init automated configuration, and generates per-VM ED25519 SSH keypairs for secure access. It downloads the Ubuntu cloud image (~600 MB) on first run and caches it for reuse. VMs are named using the pattern TG-Connector-<RemoteNetwork>-<N>.
The script supports five lifecycle actions: Deploy, Remove, UpdateConnector, UpdateOS, and List - covering the full connector lifecycle from a single tool. Batch connector creation is supported with configurable count, and updates are applied sequentially via SSH.
Outcome
Opens up Twingate deployment to Windows-only environments with fully automated provisioning. Admins comfortable with PowerShell get API-driven deployment with no manual token handling, automatic rollback on failure, and lifecycle management for updates and removal. A legacy script using pre-built images is also included for simpler use cases. Published under the Twingate-Solutions general scripts repository.