you need to delete the package and make the reg key thing an application script type. Then "Deploy" it and set the actual application as a dependency.
Of course then you cannot uninstall it because only the last app in the chain will uninstall. The better approach is to wrap the entire thing in a script that installs the msi and enters the reg keys etc. and put it all into one application. On Thu, Jul 10, 2014 at 8:33 AM, Brian McDonald <[email protected]> wrote: > Hi Sherry - this was the first thing I tried. I opened the .MSI file using > ORCA. Couldn't find anything. Is this something that all MSI's would have? > > This is for TeamViewer 9, BTW. :) > > Thanks, > > Brian > > ------------------------------ > Date: Thu, 10 Jul 2014 06:17:57 -0700 > From: [email protected] > Subject: Re: [mssms] String an application and a package together in CM12 > To: [email protected] > > Are you sure the vendor doesn't have nice polite Public properties to set > those? aka > > AwesomeCoolThing.MSI LICENSEKEY=The-Key SETMYPREFERENCES=Yes > > if not, for a regkey with an MSI, I'd set those using a Transform, and > deploy the msi using the transform... > > Sherry Kissinger > > > On Thursday, July 10, 2014 8:13 AM, Brian McDonald < > [email protected]> wrote: > > > Is this possible. For example, I have a REG key that I need to import to > configure specific settings (such as License Activation, etc.) for an > Application (MSI installer). I have created a package including the reg key > and an application including the MSI. Both are working as expected and when > deployed together yield the desired result. However, there is no way to > chain an App and PKG (to my knowledge), in CM12. > > What is the best way to approach this? While I could use the MSI and just > create a package, I'd rather take advantage of the new features of the > Application feature in CM. > > Can someone provide some options/suggestions? I'm pretty close here. > > Thanks! > Brian > > > > > >
