OneAgent environment move not happening because of version?

[AntonioSousa]

When using Remote configuration management of OneAgents, to move from a Managed to SaaS environment, we started seeing in the logs that this was not happening because of the OneAgent version. Doing the same with oneagentctl revealed the same problem.

Updating OneAgent solved the Remote configuration management & oneagentctl issue, and those OneAgents were quickly moved between environments.

New tenant is an Azure Native Dynatrace Service, and there we can only download most recent OneAgent versions. Is this some limitation that someone has experienced?

[PacoPorro]

I recommend checking the older version in the source tenant and verifying with support for the latest version in the target.
I had the same problem.

[Julius_Loman · Accepted solution]

@AntonioSousa  every Dynatrace environment has a minimum OneAgent version defined. Unfortunately, this is not a user-facing setting. Typically it is set to the latest version when the environment was created. At least I believe so. For Managed - this applies to cluster version - when it was installed.

I assume your SaaS environment is fresh, so it has a higher minimum OneAgent version than the Managed you are migrating from. You can also raise a support request to lower the minimum OA version if you are unable to upgrade OneAgents.

[AntonioSousa]

@Julius_Loman,

That's what was done: the minimum OneAgent version was changed to support the migration of the older OneAgent versions. BTW, the reason was to support Windows 2008 servers that had no update path.

[Julius_Loman]

Exactly. I also lowered the minimum supported OA due to Windows 2008 which was last supported by OA 1.269.