MOVE Multiplatform 2.6.2.265 Client with MOVE 3.6.1 Extensions

[McDuff]

Greetings

Can anyone confirm that the new MOVE 3.6.1 extensions are backwards compatible with MOVE Multiplatform 2.6.2.265 clients?

Thanks in advance.

[Former Member]

No. You have to upgrade to v3.6.1.

[Former Member]

Well, it seems to work. The 3.6.1 extensions still contain the settings for deprecated versions for backward compatibility.

We have upgraded all clients to 3.6.1 now, but in our environment, 2.6.x still worked after checking in the new 3.6.1 Extensions.

[Former Member]

When you checked in 3.6.1 did you have polices for both 2.6.2 and 3.6.1 or just 3.6.1. i want to have both 3.6.1 and 2.6.2 Clients on the same ePO server but point the 3.6.1 clients to new OSS servers on a  new ePO. Then migrate the client to the new ePO after upgrading them all to 3.6.1 clients.

[McDuff]

We actually just completed our migration to 3.6.1 a little while ago.  We had both 3.6.1 clients and 2.6.2 clients, with each version using different offload servers.  To do this, we had two sets of 3.6.1 policies (we did determine they are backwards compatible):  one pointing to 2.6 offload servers, one pointing to the 3.6.1 servers.  When we migrated the clients to 3.6.1, we first changed these 2.6 clients use the policy which points to the 3.6.1 offload servers, and then we upgraded the clients.

Remember that MOVE 2.6 and 3.6.1 each determine their offload servers from a different policy:

1.  MOVE 2.6 clients determine their offload server(s) via this deprecated policy.

2.  MOVE 3.6.1 clients determine their offload server(s) via this new 3.6.1 policy.

[Former Member]

That exactly what I am wanting to do and planning to test once I  build a old 4.6.8 test server. Then after upgrade migrate to 5.3.2.  Just wanted to see if anyone else did this. Thanks .

[Former Member]

Ok i plan to test this, but, in theory if 2.6.2 client get their policy from the General policy and 3.6.1 from the OSS assignment. Could you just assign  the OSS in each place and the client will just get the policy based on if its 2.6.9 or 3.6.1.

[McDuff]

Yes that sounds like a good idea, then you wouldn't need to change policies.  As soon as the client is upgraded, it'll use the settings in OSS assignment.  Test it out.

[Former Member]

Yep that was my thought. i have done the same with other products like  encryption and the policies only applied when it meet the correct version. Ill give feedback once i test, for FYI.

[Former Member]

Quick question. when you were managing 2.6 clients with 3.6 extensions were you able to make changes to the policy?