LabVIEW Run-Time Engine merge module

[Jordan N.]

In the past with LV 7.1 and others I could just create my own MSI installer package by going to the applibs\distkit\redist\modules subfolder and include the MSM files(merge modules).  I would use a third party MSI creator program and include these modules.  We just upgraded to LV 8.2 and I do not see the merge modules.  Are these something I can download?

I need these because LV runtime as well as all the other MSI files that National Instruments creates do not deploy with Active Directory.

[Elizabeth_S]

The LabVIEW Run-Time Engine merge module is not available.  I would recommend using Applications Builder to create an installer. 

Building an Installer (Windows)

http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/build_installer/ 

[Jordan N.]

The Application Builder does not build MSI files that are compatible with Microsoft Installer technology for a managed software installation.  I don't understand why none of the National Instruments MSI files are compatible with this technology, but they still set give them MSI wrappers.

I have heard Macrovision’s AdminStudio is supposed to be able to take an existing setup package and convert it to "real" MSI files.  Does anyone know if this work for NI products?

[JustinBritten]

Jordan,

These LabVIEW merge modules are no longer available.  As already mentioned, to build an installer you must use the LabVIEW Application Builder.  Once you have built an installer, you may use a combination of Active Directory and Microsoft SMS to deploy.  Unfortunately, Active Directory has limited built-in deployment functionality -- it only allows for deployment of an MSI.  Instead, use Active Directory to define your authentication/authorization policy and SMS (or a similar tool) to deploy throughout your organization.

As for Macrovision’s AdminStudio, this software will not convert a National Instruments installer to an MSI or a series of MSIs.  National Instruments utilizes a proprietary installer technology -- it is not a traditional 'setup' package.

Regards,

Justin

[JustinBritten]

Jordan,

In thinking about this more, I may have a solution for your use-case.  Go to ni.com/downloads and download the LabVIEW Run-Time Engine for your version of LabVIEW from the Drivers and Updates link.  For your convenience I've provided a direct link to each Run-Time Engine below.

http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C130D?opendocument&node=1...

On the download page you will find two versions of the LabVIEW Run-Time Engine.  One, called the LabVIEW 8.2 Run-Time Engine (Web Browser Only), is much smaller.  This is a self-extracting executable which includes a single LabVIEW Run-Time Engine .msi.

You could split your application into two MSIs -- one is the Run-Time Engine and the other is your custom MSI.  Then, use Active Directory to sequentially deploy each MSI individually.

Will this work for you?

Regards,

Justin

[Jordan N.]

Thanks,  Sorry for the delay in responding.

I have tried the runtime that has come with LV Developers, however that did not work, so I will give the Web version a try to see if that MSI deploys.  I will let you know.

What is the difference between the two other than the size anyway?

[Jordan N.]

Sorry, but that did not work.  I downloaded the smaller 32 MB file.  I used Winzip and WinRAR to extract the files.  The funny thing is neither of these saw the LVRuntimeEng82.msi file.  I saw only 10 or so other files that looked like they were just the latest Windows Installer package.

I decided to run the downloaded EXE file and see what extracted into my TEMP folder and I found the LVRuntimeEng82.MSI file.  I then copied that file tried to deploy that with Active Directory, but I got the same old message...

"Add operation failed.  Unable to extract the deployment information from the package.  Run a validation on the package to ensure that the package is correct."

[JustinBritten]

Jordan,

My apologies that this work-around was not successful.  At this point, your best option is to build an installer using the LabVIEW Application Builder and deploy using a combination of Active Directory and Microsoft SMS (or a similar third-party deployment utility). 

Regards,

Justin