Tom, I understand and appreciate the desire to keep all the versions consistent, but we have intentionally changed our strategy here to provide patches for specific components when appropriate. This will give us more flexibility, in general, but most beneficially to add new OS support to our agents without having to wait for a full release of all components.
You’ve probably also noticed that our versioning scheme has changed a bit so the 3rd number in the version represents the patch number directly and each release will increment that number (so you don’t have to care about the 4th number). This should make it much easier to identify what patch levels you’re running (patch 1 is 9.2.1, patch 3 is 9.2.3) vs the older scheme (patch 5 is 9.0.835, patch 6 is 9.0.853). Our intention is to make it easier for customers to understand what they are actually running relative to what we release, and help the support process, since that’s always the first question that’s asked (and surprisingly often misreported).
The issue with the BESInstaller creating a client install package that we don’t release upgrades/fixlets for is one that we intend to fix. Once complete, that should generate an installer for whatever the latest client version is, 9.2.1 in this case.