Plan The ITAM Dispatch Plan

Change window plan

Pick where you are and where you are going. Get the order of work.

Second edition October 2026 Last update … Personal project

The catch-up matrix tells you what changed. This page turns the same data into the thing you put in front of a client: a plan for one change window, in order, with the checks that have to pass first.

Answer three questions about your estate and pick where you are now and where you are going. The plan below is yours, not a generic checklist. It names the versions that must not be skipped, what to prepare before the window opens, the order of work across the platform, the beacon and the agent, and an honest list of what the change does not fix.

§1 Scope

Your estate

Where does the platform run?
Do you run OpenShift with the Kubernetes Resource Monitor? This is the deployment that broke in agent 26.2.0.
Do your beacon hosts use CyberArk Credential Provider or the Access Database Engine? From beacon 25.3.0 the beacon is a 64-bit application, so these drivers have to be the 64-bit build.
Is your estate mixed? Some machines on an older version than others.

Where you are, and where you are going

Agent →
Beacon →
Platform —
Show the plan as plain text, or put a plan back

The same plan, as plain text for a ticket or an email.



    

      
Put a plan back

      
Paste the plain text of a plan into the box and the page goes back to it: the same versions, and the same answers about your estate.

      
      

        
        
      

    

  


  
§2 Before the window opens 

  
These are the things that have to be true, or done, before the window opens. Each one names the check that tells you it is done.

  


  
§3 The order of work

  
The order below is a recommendation, and the reasoning is shown next to each step. The gates in the previous section apply whatever order you choose. Where your IT department decides differently, this page says so.

  


  
§4 Do not skip 

  
Versions and preparations that have to happen, and the reason each one matters. Getting one of these wrong is the difference between a routine window and an incident.

  


  
§5 What this change closes 

  
The items that are fixed once this window is done. This is the list to paste into the change record.

  

    

      
Agent

      

    

    

      
Beacon

      

    

  

  


  
§6 What it does not close 

  
A plan that only lists wins is not a plan. These are still open after the window, and they need a follow-up window or a different answer.

  

    

      
Agent

      

    

    

      
Beacon

      

    

  

  


  
§7 What this plan assumes

  


  
This plan is built from Flexera's own release notes, lifecycle tables and published advisories. It is a starting point for your own assessment, not a substitute for the release notes themselves, and it does not replace the judgement of whoever runs your estate.


  

    
    

      
Ali Najef Abu Ita

      
Technical Consultant · Founder, CerAImic

      
Personal project. Not a publication of Noventiq, Flexera, Snow, Octopus, or CerAImic. Independent work, my own views. Built with OpenClaw · 2026. Reach out via CerAImic if it was useful.