Deploying MSI in RM CC4 Network

[Bugs]

Hiya

 

I`m in the process of deploying an MSI package on an RM CC4 network, and i`m having problems. Iv have tried packaging it as a CC3 package (with the .ini file) but it then wont install because its an MSI not an EXE. I have also tried getting it on the network using Application wizard but this doesnt seem to work correctly either (the package doesn't appear in the console)

 

So my question is how would I package a MSI program for deployment on a CC4 network?

 

Thanks

[clareq]

You should be able to import it into console directly without the use of an ini file. Have the msi and accompanying files in a folder, on the RMMC go to FILE - IMPORT - PACKAGE - CC3 PACKAGE. Select "Any File" and point it at the msi. It should then import.

[Bugs]

I did that and I get an error return code 99, could this be the MSI? or is it a problem with the Console?

[arthur231283]

What software is the MSI package for?

[clareq]

How large is the msi? That is an old error which was fixed by SR1.

[Bugs]

right I got it to upload to the console, I found a way of doing with a INI file

 

Iv now got the problem that by default the package installs a network client, and I want it to install just the full standalone version installed (which, is an option if you install it manually)

 

I have had a look at editing the msi with ORCA but I cant find where it sets the default selection

[Edu-IT]

right I got it to upload to the console, I found a way of doing with a INI file

 

Iv now got the problem that by default the package installs a network client, and I want it to install just the full standalone version installed (which, is an option if you install it manually)

 

I have had a look at editing the msi with ORCA but I cant find where it sets the default selection

Does the package provider give a list of switches that can be used? What software is it?

[clareq]

If you told us the name of the software we might be able to offer more specific help

[Bugs]

sorry its advancing physics AS and A2

[Edu-IT]

Who makes it?

[Bugs]

the Institute of Physics

[IKWeb]

You could use a transform file along with the MSI which will tell the MSI which options to use.

 

Hope this helps.

[limawhiskey]

Dropped into this thread looking for some info on deploying MSIs via CC4. I tried importing the MSI alone but got errors on assigning the package.

 

Ended up finding lots of useful info in some RM seminar notes: RM Seminars Spring 2013 - CC4 Packages without packaging (PDF) - RM.com

 

Basically, you need to create an INI file to go along with the MSI, in the form:

[font=Consolas][Package][/font][font=Consolas]Description=A description of the package and its information [/font]
[font=Consolas]Version=1.0.0.0 [/font]
[font=Consolas]OS=5.WS,6.WS [/font]
[font=Consolas]WIPackage=.msi[/font]

 

Not mentioned in the PDF is the useful AddCommand entry, which you can use to supply arguments for the MSI (you can use Orca to discover the properties which allow arguments).

 

I used this to create a package for SIMS Discover, so added this line to the INI:

[font=Consolas]AddCommand=SQLSERVER="sqlserver\sqlinstance" DATABASENAME="discover" SIMSSQLSERVER="[/font][font=Consolas]sqlserver\sqlinstance[/font][font=Consolas]" SIMSDATABASENAME="sims"[/font]

Edited May 20, 2014 by limawhiskey

[IKWeb]

Dropped into this thread looking for some info on deploying MSIs via CC4. I tried importing the MSI alone but got errors on assigning the package.

 

Ended up finding lots of useful info in some RM seminar notes: RM Seminars Spring 2013 - CC4 Packages without packaging (PDF) - RM.com

 

Basically, you need to create an INI file to go along with the MSI, in the form:

[font=Consolas][Package][/font][font=Consolas]Description=A description of the package and its information [/font]
[font=Consolas]Version=1.0.0.0 [/font]
[font=Consolas]OS=5.WS,6.WS [/font]
[font=Consolas]WIPackage=.msi[/font]

 

Not mentioned in the PDF is the useful AddCommand entry, which you can use to supply arguments for the MSI (you can use Orca to discover the properties which allow arguments).

 

I used this to create a package for SIMS Discover, so added this line to the INI:

[font=Consolas]AddCommand=SQLSERVER="sqlserver\sqlinstance" DATABASENAME="discover" SIMSSQLSERVER="[/font][font=Consolas]sqlserver\sqlinstance[/font][font=Consolas]" SIMSDATABASENAME="sims"[/font]

 

You only need the ini file if you want to bring the MSI into the CC4 Console, if you were to use a package build machine and the RM software you can just point it to the MSI and the system will create the ini file for you.

[limawhiskey]

You only need the ini file if you want to bring the MSI into the CC4 Console, if you were to use a package build machine and the RM software you can just point it to the MSI and the system will create the ini file for you.

Thanks. I'll give that a try next time. Can you also provide arguments for the installer this way? Have only ever used that process to build a package with before / after scans.