Runtime engines removed from Deployment

[Marinuss]

Hello All

A question about TestStand deployment:

• I have my development PC where I write Labview and TestStand code and Run the Deployment Utility
• We have 10 different products that each have a deployment.
• So one deployment PC will have 10 TestStand tests installed on it.
• In each of these 10 test’s Deployment Utility, I have the following Additional Components selected (Basically TestStand, Labview Runtime and VISA Runtime)

I have the following challenge:

1. Because each deployment has all the runtime engines included, after every product installation it ask for licence activation.
2. I want to have deployments that do not include the runtime engines, So I don’t have to restart and do licensing after every product test installation.
3. Below is how I think to do things. (Help me if I’m wrong)
1. Option 1: I create a dummy deployment that only contains Runtime and TestStand Engines. (Install once on deployment PC), then deploy each product test that does not include runtime and teststand engines.
2. Option 2: Install TestStand UI and runtime engines from Labview Suite onto Deployment PC, then deploy each product test that does not include runtime and teststand engines. (But I don’t know how to install TestStand UI and runtime engines from Labview Suite)
3. Option 3: Install TestStand UI and runtime engines from Website onto Deployment PC, then deploy each product test that does not include runtime and TestStand engines. (Is this possible?)

I hope my question makes sense, how would you do this?

Marinus

[~jiggawax~]

You are on the right track.  We always do what we call a baseline installer that has the runtime engines, drivers, etc.... the things that we do NOT edit and come from a third party (in this case NI).  Then we install our high-mix test on top of that.  I would recommend using NIPM to deploy but that might be too much of a lift for you at this time since you have a process that works.

If you have to release to a PLM then I would create my own installer, so Option 1.  If you are ok with just giving them instructions to download from the vendor then Option 3.  Option 2 seems painful but the advantage over Option 3 is that they will get the right versions.

Option 1 gives you the MOST control in that the end user will always have exactly what they need/want.

[Scott_Richardson]

Marinuss -

If preventing the display of the activation prompt at the end of running an installer is the focus of your mitigation options, the below snippet might help, and see the the linked page for a list of other options:

Automating an Installer:

---

To make the installation process skip any license activation, include the --prevent-activation option in the command prompt.

start "" /wait "path of install.exe" --prevent-activation

Note: License activation must still be performed to use any product requiring activation.