Roxio Creator Silver 10
I am trying to follow the info found here http://itninja.com/link/microsoft-msde-home5 for packaging & deploying Roxio. I modifed the 1033.mst transforms to all run with REBOOT=REALLYSUPRESS. I also modifed the transform for EMC_101 to run without calling setup. The EMC_101\Roxio Creator Silver 10.msi runs just fine from the command line with the following command msiexec /i <path>\EMC_101\Roxio Creator Silver 10.msi TRANSFORMS=EMC_101\<updated transform> /qn. However, I receive a missing certificate error when I packaged it and deployed via CM/Radia Publisher. I am also getting an error about missing the MainENU.dll with the BCP_Easy Archive component install. Do these components need to install in a particular order? If so, would someone be able to provide the order? Thanks.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
ORIGINAL: luvwarmthUnlikely. I don't know the package at all but my intial thought would be: is the certificate installed for the currently logged-in user only? If so, maybe there's some condition or something which is preventing it being installed when deployed, rather than run from command-line, bearing in mind that most deployment mechanisms work under the context of the Local System account, rather than the logged-in user's account.
Do these components need to install in a particular order?
Posted by:
luvwarmth
15 years ago
Does anyone know the command line switch to prevent the installation of the Update Manager component? I have tried the following:
I have also created an updated 1033.mst for the UM.msi with the following settings:
Unfortunately, the update manager component is still installing when I run setup.exe /qn RX_EULA_ACCEPTED=1 REBOOT=REALLYSUPPRESS ADDLOCAL=ALL
- setup.exe /qn RX_EULA_ACCEPTED=1 REBOOT=REALLYSUPPRESS ADDLOCAL=ALL REMOVE=UPDATEMANAGER
- setup.exe /qn RX_EULA_ACCEPTED=1 REBOOT=REALLYSUPPRESS ADDLOCAL=ALL REMOVE=UpdateManager
- setup.exe /qn RX_EULA_ACCEPTED=1 REBOOT=REALLYSUPPRESS ADDLOCAL=ALL REMOVE=UpdateService
I have also created an updated 1033.mst for the UM.msi with the following settings:
- Property table - Added INSTALLLEVEL with value of 1
- Feature table - Changed value of Level from 1 to 5.
Unfortunately, the update manager component is still installing when I run setup.exe /qn RX_EULA_ACCEPTED=1 REBOOT=REALLYSUPPRESS ADDLOCAL=ALL
Posted by:
anonymous_9363
15 years ago
You can't specify ADDLOCAL and REMOVE on the same command line. What you need to do is enumerate all the features you DO want, leaving out the one you don't, as in:
setup.exe /qn ADDLOCAL=Feature1, Feature2, Feature3,Feature4 [other command-line arguments]
Remember that feature names are case-sensitive so FEATURE1 is different to Feature1. To save typos creeping in, I generally copy the contents of the 'Feature' column in the 'Feature' table, editing out what I don't want.
setup.exe /qn ADDLOCAL=Feature1, Feature2, Feature3,Feature4 [other command-line arguments]
Remember that feature names are case-sensitive so FEATURE1 is different to Feature1. To save typos creeping in, I generally copy the contents of the 'Feature' column in the 'Feature' table, editing out what I don't want.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.