From tool to VDI lifecycle platform - validated step by step, without a big bang.
The closed beta starts today. You’ve already read about what PVS Forge can do in the beta article—its own imager, multi-NIC stability, secure multi-server sync, context-sensitive diagnostics, inventory comparison, vDisk AI analysis, and custom post- and pre-sealing scripts. A solid foundation for everyday Citrix operations.
But this is just the beginning. PVS Forge is developing step by step from a single admin tool to a VDI lifecycle platform. Each release addresses a clearly defined problem - no big bang, no feature dumping, no migration drama. If you're in the beta, you grow with it.
That is the plan for 2026 through 2029.
v1.0 – General Availability (Q4 2026)
The closed beta becomes productive software. The full range of functions from the beta is stabilized, documented and backed up with full manufacturer support.
What v1.0 means:
- GA release of all beta features - production-ready, documented, with clear SLAs
- License model live Standard (up to 2 PVS servers) and Growth (from 3 PVS servers) - both with full functionality
- Full manufacturer support - Direct line, no ticket system with tier structures
- First customers productive in use - beta participants can seamlessly transition to v1.0, their experiences have been incorporated into the stabilization
v1.0 is not „new features“, but „beta features in production-ready quality“. If you are waiting for the first production-ready version: this is the moment.
v1.5 – Health Check (Q2 2027)
With v1.5 comes the PVS/MT Health Advisor - what Citrix architects do in their heads in every customer project is now cast in software.
The Health Advisor is not a BPA clone. It reads real configuration and performance values from your environment and provides Recommendations, who explain, Why something should be changed - not just „rule X is violated“, but „in your context this leads to problem Y because Z“.
What v1.5 brings:
- Provisioning and Master Target Health Advisor – Configuration assessment from your production PVS environment
- Explanatory configuration notes instead of rigid tick rules from 2018 documents
- PVS Reporter the environment, including the PVS server, device collections, vDisks, etc.
- vDisk Cache preserves the production Provisioning Services and conserves resources.
- Optimization Snippets Proven PVS optimizations — apply them after verifying them rather than recreating them manually, such as disabling Autoruns or moving the Spool folder. You can also upload your own snippets (Posh scripts).
- Citrix Director Add-In PVS Forge is finally bringing vDisk to Citrix Director! Which vDisk are we currently streaming, and what is its software version?
This raises PVS Forge from an „imaging tool“ to a „knowledge carrier“. Senior architect knowledge, available every day - not just when the consultant is on site.
From tool to VDI lifecycle platform
Validated step by step, without a big bang. Each release solves a clearly defined problem from everyday Citrix life.
Beta
- Own VHDX imager
- Multi-NIC stable, NetBIOS resolution
- Secure vDisk sync all PVS servers
- Smart, Parallel, Multi-vDisk Creation
- Image History with calendar view
- vDisk Comparison Old vs. New
- Single-Image Analysis with AI
v1.0
- GA release of the beta features
- License model productive (standard / growth)
- Full manufacturer support
- First customers Productive in use
v1.5
- PVS/MT Health Advisor
- vDisk Cache Parallel and low-impact vDisk creation
- Citrix Director Add-In Read-only indicator
- Explanatory configuration notes instead of BPA rules
- PVS Report – Servers, devices, vDisks, etc.
v2.0
- SQL backend for all data.
- MT-Lifecycle „Box & Cards“
- vDisk generation history over the entire life span
- Software statuses traceable per generation
- Lifecycle visualization with targeted rollback
- Workflow Builder – Image, Device, Release, Boot
v3.0
- Service-based architecture
- Continuous MT monitoring
- HTML5 console
- Multi-Persona & RBAC with AD/Entra
v2.0 – vDisk Lifecycle (Q1 2028)
A master target is a template, not an end device. Nevertheless, there is no overview in the standard consoles: Which vDisk generation came from which MT? Which software versions were frozen and when? Which generation is still running in which production environment?
With v2.0 comes the „Box & cards“ view: a master target and its vDisk generations over the entire life span - visualized, scrollable, with full history.
What v2.0 brings:
- MT lifecycle visualization - a master target, all its vDisk generations visible like cards in a box
- vDisk generation history - When was which generation produced, from which MT state, with which inventory
- Software versions traceable - per generation documents what was on it
- Targeted rollback - not „the last working version“, but „the version from March 15, before this one update“
- Workflow Builder – Custom workflows for imaging, assigning devices, setting release dates, and rebooting.
This changes how teams think about their images: away from „the current vDisk“ to „a generation in a documented line“. Audit, compliance, troubleshooting - everything will change.
v3.0 – Platform (Q1 2029)
What is today a single admin tool will become a VDI lifecycle platform. Service-based, multi-user capable, with roles, views and a shared database.
What v3.0 brings:
- Service-based architecture - PVS Forge no longer runs as a single tool on a PVS server, but as a backend service that multiple clients can talk to simultaneously
- SQL backend - Central, persistent data storage for inventories, job history, health data, configuration snapshots
- Continuous MT-Health in real time - no more point measurements, but continuous monitoring of master targets and vDisks
- HTML5 console - browser-based UI, platform-independent, multi-user
- Multi-Persona & RBAC - One database, three views: Admin (operational), Manager (control), Executive (reporting). Four roles, AD/Entra connection.
v3.0 is the step from tool to product ecosystem. Anyone working with an architect license model today can operate a team tool tomorrow - without throwing away the workflow they have built up since the beta.
Why this speed
Each release addresses a clearly defined problem, no feature dumping. Each phase is validated with beta customers before it becomes GA. Data and configurations grow with you - no migration break between versions.
This is a conscious decision. We have seen what happens when tools in the Citrix environment want too much too quickly: Features that no one can finish using, version jumps that force customers to re-implement, platform pivots that destroy investments.
PVS Forge goes the other way. Start small, build clean, validate, expand.
What this means for you
If you become a beta customer today, you get:
- The full functionality of the beta immediately
- Update to v1.0 seamlessly as part of your update subscription
- Health Advisor (v1.5), vDisk Lifecycle Visualization (v2.0) and the platform (v3.0) automatically as long as your update subscription is active
- Direct influence on the roadmap - what you need in your everyday life flows into the prioritization
And if you pause the update subscription at some point: your last build will remain functional. What you buy is yours. Forever.
[ Request beta access ] · [ View Licensing Model ] · [ Read the documentation ]