Are you using a prerelease build for EPO 5.3? My RTW 5.3 is build 402. I have just successfully checked in the new RSD extension version 5.0.2, both by upgrading the previous 5.0.1 version and by checking it in cleanly without any errors.
No you're right. I only looked at my server.ini file which shows 402. I might need to talk to someone about that.
Is this a new install or upgrade?
Under Extensions and Epolicy Orchestrator are all of the extensions, other than your current RSD, showing as version 220.127.116.110?
Call McAfee support again and they said build 400 is the latest build. This server is a upgrade from 5.1.1. All the extensions do show 18.104.22.1680 except the RSD one. McAfee suggested I tried removing and reinstalling.
Yes I would remove the extension and try to check the new one back in. If you still get the error then the EPO upgrade was not completely successful in some way because of the version checks that are done by RSD. If you want to post your orion.log we might be able to find out why.
Will engage support next week to debug for us. Don't want to post log files on public forum due to privacy issue. It did fail again once I removed and try to reinstall the RSD extension.
RSD 5.0.2 requires the following extensions (or greater):
I can only try to simulate your error by manually modifying the configuration file that checks the extension versions but I can't seem to replicate your "...not compatible with this version ..." error.
I'm seeing the same thing on multiple servers
The strange thing for us is that both the test and production systems are no longer warning about RSD 5.02 not being compatible. Both our test and production ePO server were recently upgraded from 5.1.1 to 5.3.0.