Hi Arakasi, Hi Marcos,
Thanks for your quick replies, really appreciate it!
Let me clarify your questions:
1: The external hosting provider only provide the infrastructure. We have full access to the "old" RAS server and fully manage it.
2: Correct, the "new" RAS installation is hosted directly in our own infrastructure and we would like to redirect all clients to this new RA.
So I did create a Configuration Change and Policy Update (tried both scenarios) from the "old" RAS, the change was supposed to update the URL on each clients, to point to the "new" RAS who would welcome these new clients.
I tried various combinations, (for example created the policy / config change from the "new" RAS, exported and imported on the "old" RAS, but although successfully pushed to the clients, nothing get ever changed and clients keep pointing to the "old" RAS.
This is why I though about a potential incompatibility between the versions of "old" RAS and the clients.
I'm not against deploying a newer version of the clients, but our clients are spread out around the world and not really fully managed within an entity (such as a domain). It's therefore not so straight forward to push a new MSI package to all those clients, although it could eventually be a scenario (if we can perform a version 4 uninstallation, + new installation of version 5 and configuration, all this in a single MSI package).