{"id":726,"date":"2026-05-30T04:09:41","date_gmt":"2026-05-30T04:09:41","guid":{"rendered":"http:\/\/pvs-forge.com\/?p=726"},"modified":"2026-07-27T10:50:01","modified_gmt":"2026-07-27T10:50:01","slug":"pvs-forge-roadmap-2026-2029","status":"publish","type":"post","link":"https:\/\/www.pvs-forge.com\/en\/pvs-forge-roadmap-2026-2029\/","title":{"rendered":"PVS Forge Roadmap 2026\u20132029"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>Vom Werkzeug zur VDI-Lifecycle-Plattform \u2013 schrittweise validiert, ohne Big-Bang.<\/em><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Die geschlossene Beta ist heute. Was PVS Forge schon kann, hast du im Beta-Artikel gelesen \u2013 eigener Imager, Multi-NIC-Stabilit\u00e4t, sicheres Multi-Server-Sync, kontextsensible Diagnostik, Inventory-Vergleich, vDisk KI-Analyse, Custom Post- und Pre-Sealing Scripts. Solide Basis f\u00fcr den Citrix-Alltag.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aber das ist erst der Anfang. PVS Forge entwickelt sich Schritt f\u00fcr Schritt vom Single-Admin-Tool zur <strong>VDI-Lifecycle-Plattform<\/strong>. Jeder Release adressiert ein klar abgegrenztes Problem \u2013 kein Big-Bang, kein Feature-Dumping, keine Migrations-Drama. Wer in der Beta dabei ist, w\u00e4chst mit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das ist der Plan f\u00fcr 2026 bis 2029.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">v1.0 \u2013 General Availability (Q4 2026)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Die geschlossene Beta wird zur produktiven Software. Der vollst\u00e4ndige Funktionsumfang aus der Beta wird stabilisiert, dokumentiert, mit vollem Hersteller-Support unterlegt.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Was v1.0 bedeutet:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>GA-Release<\/strong> aller Beta-Features \u2013 produktionsreif, dokumentiert, mit klaren SLAs<\/li>\n\n\n\n<li><strong>Lizenzmodell live<\/strong> Standard (bis 2 PVS-Server) und Wachstum (ab 3 PVS-Server) \u2013 beide mit vollem Funktionsumfang<\/li>\n\n\n\n<li><strong>Voller Hersteller-Support<\/strong> \u2013 direkter Draht, kein Ticket-System mit Tier-Strukturen<\/li>\n\n\n\n<li><strong>Erste Kunden produktiv<\/strong> im Einsatz \u2013 Beta-Teilnehmer k\u00f6nnen nahtlos in v1.0 \u00fcbergehen, ihre Erfahrungen sind in die Stabilisierung eingeflossen<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">v1.0 ist nicht \u201eneue Features&#8220;, sondern \u201eBeta-Features in produktionsreifer Qualit\u00e4t&#8220;. Wer auf den ersten produktiv einsetzbaren Stand wartet: das ist der Moment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">v1.5 \u2013 Health Check (Q2 2027)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Mit v1.5 kommt der <strong>PVS\/MT Health Advisor<\/strong> \u2013 das, was Citrix-Architekten in jedem Kundenprojekt im Kopf machen, jetzt in Software gegossen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Der Health Advisor ist kein BPA-Klon. Er liest reale Konfigurations- und Performance-Werte aus deiner Umgebung und gibt <strong>Empfehlungen<\/strong>, die erkl\u00e4ren, <em>warum<\/em> etwas ge\u00e4ndert werden sollte \u2013 nicht nur \u201eRegel X ist verletzt&#8220;, sondern \u201ein deinem Kontext f\u00fchrt das zu Problem Y, weil Z&#8220;.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Was v1.5 bringt:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Provisioning- und Master Target Health Advisor<\/strong> \u2013 Konfigurations-Bewertung aus deiner produktiven PVS-Umgebung<\/li>\n\n\n\n<li><strong>Erkl\u00e4rende Konfigurations-Hinweise<\/strong> statt starrer H\u00e4kchenregeln aus Dokumenten von 2018<\/li>\n\n\n\n<li><strong>PVS Reporter<\/strong> der Umgebung mit PVS-Server, Device Collections, vDisk usw.<\/li>\n\n\n\n<li><strong>vDisk Cache<\/strong> schont die produktiven Provisioning Services und spart Ressourcen.<\/li>\n\n\n\n<li><strong>Optimization Snippets<\/strong> Bew\u00e4hrte PVS-Optimierungen \u2014 gepr\u00fcft anwenden statt manuell nachbauen, wie Autoruns deaktivieren oder Spool Ordner verschieben. Zus\u00e4tzlich k\u00f6nnen eigene Snippets (Posh Skripte) hochgeladen werden.<\/li>\n\n\n\n<li><strong>Citrix Director Add-In<\/strong> PVS Forge bringt endlich die vDisk in Citrix Director! Welche vDisk streamen wir gerade mit welchem Softwarestand?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Damit hebt sich PVS Forge von \u201eImaging-Werkzeug&#8220; zu \u201eWissenstr\u00e4ger&#8220;. Senior-Architekten-Wissen, jeden Tag verf\u00fcgbar \u2013 nicht nur, wenn der Berater im Haus ist.<\/p>\n\n\n\n<meta charset=\"UTF-8\">\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n<title>PVS Forge Roadmap<\/title>\n<link rel=\"preconnect\" href=\"https:\/\/fonts.googleapis.com\">\n<link rel=\"preconnect\" href=\"https:\/\/fonts.gstatic.com\" crossorigin=\"\">\n<link href=\"https:\/\/fonts.googleapis.com\/css2?family=Archivo:wght@600;700;800;900&amp;family=IBM+Plex+Mono:wght@400;500;600&amp;family=IBM+Plex+Sans:wght@400;500;600&amp;display=swap\" rel=\"stylesheet\">\n<style>\n  :root{\n    --bg:#0E0E1C;\n    --bg-2:#16162A;\n    --panel:#1E1E38;\n    --ink:#E8E8F2;\n    --muted:#9292B0;\n    --steel:#5B7A9D;\n    --fire:#F5A623;\n    --fire-hot:#FF6B35;\n    --line:rgba(146,146,176,0.16);\n  }\n  *{margin:0;padding:0;box-sizing:border-box}\n  .pvsf-roadmap{\n    background:var(--bg);color:var(--ink);\n    font-family:'IBM Plex Sans',sans-serif;\n    padding:80px 28px;\n    position:relative;overflow:hidden;\n  }\n  .pvsf-roadmap::before{\n    content:\"\";position:absolute;inset:0;\n    background:radial-gradient(800px 400px at 20% 0%,rgba(245,166,35,.08),transparent 60%),\n               radial-gradient(600px 400px at 80% 100%,rgba(91,122,157,.08),transparent 60%);\n    pointer-events:none;\n  }\n  .pvsf-roadmap .wrap{max-width:1280px;margin:0 auto;position:relative}\n  .pvsf-roadmap h1,.pvsf-roadmap h2,.pvsf-roadmap h3{\n    font-family:'Archivo',sans-serif;line-height:1.1;letter-spacing:-0.02em}\n  .pvsf-roadmap .mono{font-family:'IBM Plex Mono',monospace;letter-spacing:.04em}\n\n  \/* Header *\/\n  .pvsf-head{text-align:center;margin-bottom:64px}\n  .pvsf-eyebrow{\n    display:inline-flex;align-items:center;gap:8px;font-size:12.5px;font-weight:600;\n    color:var(--fire);background:rgba(245,166,35,.1);border:1px solid rgba(245,166,35,.25);\n    padding:6px 14px;border-radius:100px;margin-bottom:20px;\n    font-family:'IBM Plex Mono',monospace;letter-spacing:.08em;text-transform:uppercase;\n  }\n  .pvsf-eyebrow .dot{width:6px;height:6px;border-radius:50%;background:var(--fire);\n    box-shadow:0 0 8px var(--fire);animation:pulse 2s ease-in-out infinite}\n  @keyframes pulse{0%,100%{opacity:1}50%{opacity:.4}}\n  .pvsf-head h2{font-size:44px;font-weight:800;margin-bottom:16px}\n  .pvsf-head h2 .grad{background:linear-gradient(100deg,var(--fire),var(--fire-hot));\n    -webkit-background-clip:text;background-clip:text;color:transparent}\n  .pvsf-head p{font-size:17px;color:var(--muted);max-width:600px;margin:0 auto}\n\n  \/* Timeline track *\/\n  .pvsf-track{\n    display:grid;\n    grid-template-columns:repeat(5,1fr);\n    gap:16px;\n    position:relative;\n  }\n  .pvsf-track::before{\n    content:\"\";position:absolute;\n    top:42px;left:5%;right:5%;height:2px;\n    background:linear-gradient(90deg,\n      var(--fire) 0%,var(--fire) 12%,\n      var(--steel) 25%,var(--steel) 88%,\n      rgba(91,122,157,.3) 100%);\n    z-index:0;\n  }\n\n  \/* Step *\/\n  .pvsf-step{position:relative;z-index:1;display:flex;flex-direction:column;align-items:center}\n  .pvsf-node{\n    width:84px;height:84px;border-radius:50%;\n    background:var(--bg-2);border:2px solid var(--steel);\n    display:grid;place-items:center;\n    font-family:'Archivo',sans-serif;font-weight:800;font-size:14px;\n    color:var(--muted);margin-bottom:22px;\n    position:relative;\n    transition:.25s;\n  }\n  .pvsf-step.now .pvsf-node{\n    background:linear-gradient(140deg,var(--fire),var(--fire-hot));\n    border-color:var(--fire);color:#1a0f00;\n    box-shadow:0 0 24px rgba(245,166,35,.5),0 0 60px rgba(245,166,35,.25);\n    animation:glow 2.5s ease-in-out infinite;\n  }\n  @keyframes glow{0%,100%{box-shadow:0 0 24px rgba(245,166,35,.5),0 0 60px rgba(245,166,35,.25)}\n                  50%{box-shadow:0 0 32px rgba(255,107,53,.65),0 0 80px rgba(245,166,35,.4)}}\n  .pvsf-step.next .pvsf-node{\n    border-color:var(--fire);color:var(--fire);\n    background:rgba(245,166,35,.08);\n  }\n  .pvsf-step.future .pvsf-node{\n    border-color:var(--line);color:var(--muted);\n    border-style:dashed;\n  }\n  .pvsf-step.vision .pvsf-node{\n    border-color:var(--line);color:var(--muted);\n    border-style:dashed;opacity:.7;\n  }\n\n  \/* Status pill *\/\n  .pvsf-status{\n    font-family:'IBM Plex Mono',monospace;font-size:11px;letter-spacing:.1em;\n    text-transform:uppercase;color:var(--muted);margin-bottom:10px;\n    padding:4px 10px;border-radius:6px;background:var(--bg-2);\n    border:1px solid var(--line);\n  }\n  .pvsf-step.now .pvsf-status{color:var(--fire);border-color:rgba(245,166,35,.3);background:rgba(245,166,35,.08)}\n  .pvsf-step.next .pvsf-status{color:var(--fire);border-color:rgba(245,166,35,.3)}\n\n  \/* Card *\/\n  .pvsf-card{\n    background:linear-gradient(160deg,var(--panel),rgba(30,30,56,.4));\n    border:1px solid var(--line);border-radius:14px;\n    padding:22px;width:100%;text-align:left;\n    transition:.25s;position:relative;overflow:hidden;\n  }\n  .pvsf-step.now .pvsf-card{\n    border-color:rgba(245,166,35,.4);\n    box-shadow:0 12px 40px rgba(0,0,0,.4),0 0 0 1px rgba(245,166,35,.15);\n  }\n  .pvsf-step.now .pvsf-card::before{\n    content:\"\";position:absolute;top:0;left:0;right:0;height:2px;\n    background:linear-gradient(90deg,var(--fire),var(--fire-hot));\n  }\n  .pvsf-card h3{\n    font-size:24px;font-weight:800;margin-bottom:4px;color:var(--ink);\n  }\n  .pvsf-card .codename{\n    font-family:'IBM Plex Mono',monospace;font-size:12.5px;color:var(--steel);\n    margin-bottom:16px;letter-spacing:.02em;\n  }\n  .pvsf-step.now .pvsf-card .codename{color:var(--fire)}\n  .pvsf-card ul{list-style:none;padding:0}\n  .pvsf-card li{\n    font-size:13.5px;color:var(--muted);line-height:1.55;\n    padding-left:14px;position:relative;margin-bottom:7px;\n  }\n  .pvsf-card li::before{\n    content:\"\";position:absolute;left:0;top:9px;width:5px;height:5px;\n    border-radius:50%;background:var(--steel);\n  }\n  .pvsf-step.now .pvsf-card li::before{background:var(--fire)}\n  .pvsf-card li:last-child{margin-bottom:0}\n  .pvsf-card li strong{color:var(--ink);font-weight:600}\n\n  \/* Mobile *\/\n  @media (max-width:900px){\n    .pvsf-roadmap{padding:60px 20px}\n    .pvsf-head h2{font-size:32px}\n    .pvsf-track{\n      grid-template-columns:1fr;\n      gap:32px;\n      padding-left:50px;\n    }\n    .pvsf-track::before{\n      top:5%;bottom:5%;left:30px;right:auto;\n      width:2px;height:auto;\n      background:linear-gradient(180deg,\n        var(--fire) 0%,var(--fire) 12%,\n        var(--steel) 25%,var(--steel) 88%,\n        rgba(91,122,157,.3) 100%);\n    }\n    .pvsf-step{flex-direction:row;align-items:flex-start;gap:20px}\n    .pvsf-node{\n      width:56px;height:56px;font-size:11px;margin-bottom:0;flex-shrink:0;\n      margin-left:-46px;\n    }\n    .pvsf-card{flex:1}\n    .pvsf-status{position:absolute;top:-8px;left:30px;background:var(--bg);padding:2px 8px;font-size:10px}\n  }\n<\/style>\n\n\n\n<section class=\"pvsf-roadmap\">\n  <div class=\"wrap\">\n\n    <header class=\"pvsf-head\">\n      <span class=\"pvsf-eyebrow\"><span class=\"dot\"><\/span> Roadmap 2026\u20132029<\/span>\n      <h2>Vom Werkzeug zur <span class=\"grad\">VDI-Lifecycle-Plattform<\/span><\/h2>\n      <p>Schrittweise validiert, ohne Big-Bang. Jeder Release l\u00f6st ein klar abgegrenztes Problem aus dem Citrix-Alltag.<\/p>\n    <\/header>\n\n    <div class=\"pvsf-track\">\n\n      <!-- Beta -->\n      <div class=\"pvsf-step now\">\n        <div class=\"pvsf-node\">BETA<\/div>\n        <span class=\"pvsf-status\">Now \u00b7 2026<\/span>\n        <div class=\"pvsf-card\">\n          <h3>Beta<\/h3>\n          <div class=\"codename\">\/\/ Closed Beta l\u00e4uft<\/div>\n          <ul>\n            <li><strong>Eigener VHDX Imager<\/strong><\/li>\n            <li><strong>Multi-NIC<\/strong> stabil, NetBIOS-Resolution<\/li>\n            <li><strong>Sicherer vDisk-Sync<\/strong> alle PVS-Server<\/li>\n            <li><strong>Smarte, parallele, multi-vDisk Erstellung<\/strong><\/li>\n            <li><strong>Image Historie<\/strong> mit Kalenderansicht<\/li>\n            <li><strong>vDisk Vergleich<\/strong> Alt gegen Neu<\/li><strong> <\/strong><li><strong>Single-Image-Analyse mit KI<\/strong><\/li>\n\n\n          <\/ul>\n        <\/div>\n      <\/div>\n\n      <!-- v1.0 -->\n      <div class=\"pvsf-step next\">\n        <div class=\"pvsf-node\">v1.0<\/div>\n        <span class=\"pvsf-status\">Q4 \u00b7 2026<\/span>\n        <div class=\"pvsf-card\">\n          <h3>v1.0<\/h3>\n          <div class=\"codename\">\/\/ General Availability<\/div>\n          <ul>\n            <li><strong>GA-Release<\/strong> der Beta-Features<\/li>\n            <li><strong>Lizenzmodell<\/strong> produktiv (Standard \/ Wachstum)<\/li>\n            <li><strong>Voller Hersteller-Support<\/strong><\/li>\n            <li><strong>Erste Kunden<\/strong> produktiv im Einsatz<\/li>\n          <\/ul>\n        <\/div>\n      <\/div>\n\n      <!-- v1.5 Health Check -->\n      <div class=\"pvsf-step future\">\n        <div class=\"pvsf-node\">v1.5<\/div>\n        <span class=\"pvsf-status\">Q2 \u00b7 2027<\/span>\n        <div class=\"pvsf-card\">\n          <h3>v1.5<\/h3>\n          <div class=\"codename\">\/\/ Health Check<\/div>\n          <ul>\n            <li><strong>PVS\/MT Health Advisor<\/strong><\/li>\n            <li><strong>vDisk Cache<\/strong> parallele und schonende vDisk Erstellung<\/li>\n            <li><strong>Citrix Director Add-In<\/strong> read only Anzeige<\/li>\n            <li><strong>Erkl\u00e4rende Konfigurations-Hinweise<\/strong> statt BPA-Regeln<\/li>\n            <li><strong>PVS Report<\/strong> &#8211; Server, Devices, vDisk usw.<\/li>\n          <\/ul>\n        <\/div>\n      <\/div>\n\n      <!-- v2.0 vDisk Lifecycle -->\n      <div class=\"pvsf-step future\">\n        <div class=\"pvsf-node\">v2.0<\/div>\n        <span class=\"pvsf-status\">Q1 2028<\/span>\n        <div class=\"pvsf-card\">\n          <h3>v2.0<\/h3>\n          <div class=\"codename\">\/\/ vDisk Lifecycle<\/div>\n          <ul>\n            <li><strong>SQL-Backend<\/strong> f\u00fcr s\u00e4mtliche Daten.<\/li>\n            <li><strong>MT-Lifecycle<\/strong> \u201eSchachtel &amp; Karten&#8220;<\/li>\n            <li><strong>vDisk-Generations-Historie<\/strong> \u00fcber den ganzen Life-Span<\/li>\n            <li><strong>Software-St\u00e4nde<\/strong> pro Generation nachvollziehbar<\/li>\n            <li><strong>Lifecycle-Visualisierung<\/strong> mit gezieltem Rollback<\/li>\n            <li><strong>Workflow Builder<\/strong> &#8211; Image, Device, Release, Boot<\/li>\n          <\/ul>\n        <\/div>\n      <\/div>\n\n      <!-- v3.0 Platform -->\n      <div class=\"pvsf-step vision\">\n        <div class=\"pvsf-node\">v3.0<\/div>\n        <span class=\"pvsf-status\">Q1 2029 \u00b7 Vision<\/span>\n        <div class=\"pvsf-card\">\n          <h3>v3.0<\/h3>\n          <div class=\"codename\">\/\/ Platform<\/div>\n          <ul>\n            <li><strong>Dienstbasierte Architektur<\/strong><\/li>\n            <li><strong>St\u00e4ndige MT-\u00dcberwachung<\/strong><\/li>\n            <li><strong>HTML5-Konsole<\/strong><\/li>\n            <li><strong>Multi-Persona &amp; RBAC<\/strong> mit AD\/Entra<\/li>\n          <\/ul>\n        <\/div>\n      <\/div>\n\n    <\/div>\n  <\/div>\n<\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">v2.0 \u2013 vDisk Lifecycle (Q1 2028)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Master Target ist eine Vorlage, kein Endger\u00e4t. Trotzdem fehlt in den Standard-Konsolen jede \u00dcbersicht: Welche vDisk-Generation kam von welchem MT? Welche Software-St\u00e4nde wurden wann gefroren? Welche Generation l\u00e4uft noch in welcher Produktivumgebung?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mit v2.0 kommt die <strong>\u201eSchachtel &amp; Karten&#8220;-Sicht<\/strong>: ein Master Target und seine vDisk-Generationen \u00fcber den ganzen Life-Span \u2013 visualisiert, bl\u00e4tterbar, mit voller Historie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Was v2.0 bringt:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>MT-Lifecycle-Visualisierung<\/strong> \u2013 ein Master Target, alle seine vDisk-Generationen sichtbar wie Karten in einer Schachtel<\/li>\n\n\n\n<li><strong>vDisk-Generations-Historie<\/strong> \u2013 wann wurde welche Generation produziert, von welchem MT-Zustand, mit welchem Inventory<\/li>\n\n\n\n<li><strong>Software-St\u00e4nde nachvollziehbar<\/strong> \u2013 pro Generation dokumentiert, was drauf war<\/li>\n\n\n\n<li><strong>Gezielter Rollback<\/strong> \u2013 nicht \u201edie letzte funktionierende Version&#8220;, sondern \u201edie Version vom 15. M\u00e4rz, vor diesem einen Update&#8220;<\/li>\n\n\n\n<li><strong><strong>Workflow Builder<\/strong> <\/strong>&#8211; Eigene Workflows von Imaging, Devices Zuweisen, Release Datum festlegen, Neustarten.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Das ver\u00e4ndert, wie Teams \u00fcber ihre Images denken: weg vom \u201edie aktuelle vDisk&#8220; hin zu \u201eeine Generation in einer dokumentierten Linie&#8220;. Audit, Compliance, Troubleshooting \u2013 alles wird damit anders.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">v3.0 \u2013 Platform (Q1 2029)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Was heute ein Single-Admin-Tool ist, wird mit v3.0 zur <strong>VDI-Lifecycle-Plattform<\/strong>. Dienstbasiert, multi-user-f\u00e4hig, mit Rollen, Sichten und einer gemeinsamen Datenbasis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Was v3.0 bringt:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dienstbasierte Architektur<\/strong> \u2013 PVS Forge l\u00e4uft nicht mehr als einzelnes Tool auf einem PVS-Server, sondern als Backend-Dienst, mit dem mehrere Clients gleichzeitig sprechen k\u00f6nnen<\/li>\n\n\n\n<li><strong>SQL-Backend<\/strong> \u2013 zentrale, persistente Datenhaltung f\u00fcr Inventories, Job-History, Health-Daten, Konfigurations-Snapshots<\/li>\n\n\n\n<li><strong>Continuous MT-Health<\/strong> in Echtzeit \u2013 keine Punkt-Messungen mehr, sondern fortlaufendes Monitoring der Master-Targets und vDisks<\/li>\n\n\n\n<li><strong>HTML5-Konsole<\/strong> \u2013 browser-basiertes UI, plattformunabh\u00e4ngig, multi-user<\/li>\n\n\n\n<li><strong>Multi-Persona &amp; RBAC<\/strong> \u2013 eine Datenbasis, drei Sichten: Admin (operativ), Manager (Steuerung), Executive (Reporting). Vier Rollen, AD\/Entra-Anbindung.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">v3.0 ist der Schritt vom Tool zum Produkt-\u00d6kosystem. Wer heute mit einem Architekten-Lizenz-Modell arbeitet, kann morgen ein Team-Tool betreiben \u2013 ohne den Workflow wegzuwerfen, den er sich seit der Beta aufgebaut hat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Warum dieses Tempo<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Jeder Release adressiert ein <strong>klar abgegrenztes Problem<\/strong>, kein Feature-Dumping. Jede Phase wird mit Beta-Kunden validiert, bevor sie GA wird. Daten und Konfigurationen wachsen mit \u2013 kein Migrations-Bruch zwischen Versionen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das ist eine bewusste Entscheidung. Wir haben gesehen, was passiert, wenn Tools im Citrix-Umfeld zu schnell zu viel wollen: Features, die niemand fertig benutzen kann, Versions-Spr\u00fcnge, die Kunden zur Re-Implementierung zwingen, Plattform-Pivots, die Investitionen vernichten.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PVS Forge geht den anderen Weg. Klein anfangen, sauber bauen, validieren, ausbauen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Was das f\u00fcr dich bedeutet<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Wenn du heute Beta-Kunde wirst<\/strong>, bekommst du:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Den vollen Funktionsumfang der Beta sofort<\/li>\n\n\n\n<li>Update auf v1.0 nahtlos im Rahmen deines Update-Abos<\/li>\n\n\n\n<li>Health Advisor (v1.5), vDisk-Lifecycle-Visualisierung (v2.0) und die Plattform (v3.0) automatisch, solange dein Update-Abo aktiv ist<\/li>\n\n\n\n<li>Direkten Einfluss auf die Roadmap \u2013 was du in deinem Alltag brauchst, flie\u00dft in die Priorisierung ein<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Und falls du das Update-Abo irgendwann pausierst: dein letzter Build bleibt funktional. <strong>Was du gekauft hast, geh\u00f6rt dir. F\u00fcr immer.<\/strong><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>[ <a href=\"http:\/\/pvs-forge.com\/pvs-forge-beta\/\" data-type=\"post\" data-id=\"714\">Beta-Zugang anfragen<\/a> ]<\/strong> <strong>\u00b7<\/strong> <strong>[ <a href=\"https:\/\/www.pvs-forge.com\/pvs-forge-beta\/\" data-type=\"post\" data-id=\"714\">Lizenzmodell ansehen<\/a> ]<\/strong> <strong>\u00b7<\/strong> <strong>[ <a href=\"https:\/\/docs.pvs-forge.com\" data-type=\"link\" data-id=\"https:\/\/docs.pvs-forge.com\">Dokumentation lesen<\/a> ]<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Vom Werkzeug zur VDI-Lifecycle-Plattform \u2013 schrittweise validiert, ohne Big-Bang. Die geschlossene Beta ist heute. Was PVS Forge schon kann, hast du im Beta-Artikel gelesen \u2013 eigener Imager, Multi-NIC-Stabilit\u00e4t, sicheres Multi-Server-Sync, kontextsensible Diagnostik, Inventory-Vergleich, vDisk KI-Analyse, Custom Post- und Pre-Sealing Scripts. Solide Basis f\u00fcr den Citrix-Alltag. Aber das ist erst der Anfang. PVS Forge entwickelt sich [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":744,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[9],"tags":[],"class_list":["post-726","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pvs-forge"],"uagb_featured_image_src":{"full":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap.png",600,435,false],"thumbnail":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap-150x150.png",150,150,true],"medium":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap-300x218.png",300,218,true],"medium_large":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap.png",600,435,false],"large":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap.png",600,435,false],"1536x1536":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap.png",600,435,false],"2048x2048":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap.png",600,435,false],"trp-custom-language-flag":["https:\/\/www.pvs-forge.com\/wp-content\/uploads\/2026\/05\/forge-roadmap-18x12.png",18,12,true]},"uagb_author_info":{"display_name":"Thomas K\u00f6tzing","author_link":"https:\/\/www.pvs-forge.com\/en\/author\/thomas-koetzing\/"},"uagb_comment_info":0,"uagb_excerpt":"Vom Werkzeug zur VDI-Lifecycle-Plattform \u2013 schrittweise validiert, ohne Big-Bang. Die geschlossene Beta ist heute. Was PVS Forge schon kann, hast du im Beta-Artikel gelesen \u2013 eigener Imager, Multi-NIC-Stabilit\u00e4t, sicheres Multi-Server-Sync, kontextsensible Diagnostik, Inventory-Vergleich, vDisk KI-Analyse, Custom Post- und Pre-Sealing Scripts. Solide Basis f\u00fcr den Citrix-Alltag. Aber das ist erst der Anfang. PVS Forge entwickelt sich&hellip;","_links":{"self":[{"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/posts\/726","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/comments?post=726"}],"version-history":[{"count":25,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/posts\/726\/revisions"}],"predecessor-version":[{"id":976,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/posts\/726\/revisions\/976"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/media\/744"}],"wp:attachment":[{"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/media?parent=726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/categories?post=726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pvs-forge.com\/en\/wp-json\/wp\/v2\/tags?post=726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}