I am packaging LabView for WinXP in msi format, resulting install all works except nidqsrvr.exe will not initialize app, any comments?

[mandres]

OS is WinXP, installer ver. is 2.0, NiDAQ is 6.1 with support for 6.0, and RT 6i/6.1

[crelf]

Your best bet is to contact National Instruments directly to see how to do it, and if they premit people creating distribution packages of their products (my guess is that they probably won't be too keen to allow you to create a LabVIEW installation package...)

[Jeremy Braden]

I agree with crelf, but I am curious why you would want to rebuild the LabVIEW development environment distrubution.

[mandres]

Repackaging software is a common practice in corps. There are no issues with vendors - seats are paid for requardless of how delivered. The repackaging is done in MSI format for a variety of reasons. The software can be advertised or pushed via sms, zen, active directory and so on. Users do not have to know how to install or configure - software installs are all customized to be installed silently and preconfigured, they cannot be altered - plus all installs are selfhealing - if something changes it is corrected auto. Also roaming profiles will selfheal from one machine to another.

[mandres]

Repackaging software is a common practice in corps. There are no issues with vendors - seats are paid for requardless of how delivered. The repackaging is done in MSI format for a variety of reasons. The software can be advertised or pushed via sms, zen, active directory and so on. Users do not have to know how to install or configure - software installs are all customized to be installed silently and preconfigured, they cannot be altered - plus all installs are selfhealing - if something changes it is corrected auto. Also roaming profiles will selfheal from one machine to another.

[crelf]

Ohhhhh - I see what you are trying to do, and I agree completely with the concept of repackaging in a corporate environment (It's particularly handy when you want to have strict control over user's software profiles, and makes unpgrading and rebuilding workstations much quicker, and with less user intervention). Unfortunately, I don't know the answer to your question - sorry 🙂 I'd get in contact with NI and see what they have to say...

Good luck!

[Dafie]

We DID contact National Instruments about packaging Labview as a .msi file to be distributed via group policy in Active Directory, and they suggested we should check these forums here, because they don't know how to do it either.. National Instruments technical support has been extremely slow to respond and very unhelpful when they do respond. I am very dissatisfied. If anyone has done it successfully, please contact me.

[AEDavid]

This can be accomplished by pushing a batch file out via SMS, using the information from Automating the Installation of National Instruments Software.

An example batch file is:

"Core Components\LabVIEW 8.2\setup.exe" LabVIEW_82.txt /r:n /acceptLicenses yes /cache:f C:\temp.txt
"Core Components\DIAdem 10.1\setup.exe" DIAdem_101.txt /r:n /acceptLicenses yes /cache:f C:\temp.txt
"Core Components\Requirements Gateway 1.0\setup.exe" ReqGateway_10.txt /r:n /acceptLicenses yes /cache:f C:\temp.txt
"Core Components\Signal Express 1.1.1\setup.exe" SigExpress_111.txt /r:n /acceptLicenses yes /cache:f C:\temp.txt
"Core Components\SwitchExecutive 2.1\distribution\setup.exe" SwitchExec_21.txt /r:n /acceptLicenses yes /cache:f C:\temp.txt
"Core Components\TestStand 3.5\setup.exe" TestStand_35.txt /r:n /acceptLicenses yes /cache:f C:\temp.txt

Message Edited by AEDavid on 12-26-2007 11:59 AM