MSP Mode Versions MISMATCH

[opk.giandomenico]

Is version parity required between the MSP Director and the remote tenant's NAKIVO deployment, or is there a workaround to connect them despite a version mismatch? Updating the MSP Director and every customer's instance every time is too time-consuming.

MSP Director version: 11.2.1.104556
Remote Tenants: 11.2.2.108504

 

[The Official Moderator]

5 hours ago, opk.giandomenico said:

Is version parity required between the MSP Director and the remote tenant's NAKIVO deployment, or is there a workaround to connect them despite a version mismatch? Updating the MSP Director and every customer's instance every time is too time-consuming.

MSP Director version: 11.2.1.104556
Remote Tenants: 11.2.2.108504

 

Hello @opk.giandomenico,

MSP Director and remote tenant deployment need to be on the exact same version and build.

There is no workaround for this.

[opk.giandomenico]

Considering i've updated Director and all customer one week ago and considering 11.2.2 has been released something like some days ago now i need to update all again. It need alot of time..

[The Official Moderator]

On 8/19/2026 at 7:30 PM, opk.giandomenico said:

Considering i've updated Director and all customer one week ago and considering 11.2.2 has been released something like some days ago now i need to update all again. It need alot of time..

Dear @opk.giandomenico

Thanks for the feedback.

We understand that frequent releases combined with strict version parity can create additional overhead for MSP environments with many tenants.

Unfortunately, there’s currently no workaround for the matching-version requirement.

We take feedback like this into consideration when evaluating future improvements to release management and update workflows for MSP environments.