Unable to use Switch Executive deployment engine

[NavyJack]

We can't seem to be able to use the Switch executive deployment Engine which we purchased a while back (3 copies). We have version 2.1 of Switch Executive which ws used for developing our system, but noticed the Deployment engines purchased are only 2.0.1. Is this the problem, or are we just not doing something right?

[Jordan_D]

Hi NavyJack,

NI Switch Executive configurations can only be deployed on machines with the same version deployment engine . Since your deployment engine is older than your configuration, you will not be able to use it without upgrading your deployment engine.

[NavyJack]

Thanks Jordon.

One more question then.  How about backward compatibility (i.e. Switch Executive Deployment Engine 2.1.1. with Switch Executive 2.1)?

[Jordan_D]

Hi Jack,

The specific pair that you mentioned in your post are compatible with each other. As a general rule, you should be using the same version for development and deployment. With this in mind, there are some cases, such as maintenance releases when the newer deployment versions will still be able to work with the older configurations. The specific case you mentioned in your most recent post is one of these cases with Switch Executive Deployment Engine 2.1.1 and with Switch Executive 2.1. I hope this clarifies things.

[NavyJack]

Certainly does.  Thanks a million.  Your response was most appreciated.

[Srđan_Zirojević]

I just wanted to chime in and clarify the clarification some more 🙂

NI will make every effort to support reading old configurations in all new versions of its software. So, if you have craeted a configuration using version x, all versions y, where y >= x should be able to understand the configuration x.

The additional benefit with some minor/tiny version updates is that your configuration might be read with even a lower version of NISE. E.g. if you create something with version 2.1.1, version 2.1 might be able to read it since there were no changes to configuration metadata aspects of the product.

Hope this did not confuse you now.

-Serge

[NavyJack]

Thanks!  Yes, I understood everything.  In my original "problem" I was trying to read a 2.1 config file with a 2.0.1 deployment engine, which didn't work.  I've got new versions of both (2.1.1) on the way.

Again, thanks for the help.