Sign up today to participate, stay informed, earn points and establish a reputation for yourself!Sign up! or login
If you would like to use the MSI you could say, msiexec.exe /i ...\businessObjects.msi LICENSEDIR="..." ADDLOCAL=bo,.. ALLUSERS=1/MIGRATION=0/INSTALLVBA=1 TRANSFORMS=...mst /qb
I have to disagree with comments about needing to repackage this native MSI. The MSI does have thousands of CAB files (3 CD's worth) but it works perfectly well. Using a Transform to add my required license and Bomain keys etc I used the vendors different feature levels with complete sucess to perform the /QB level install I wanted. Depending on how you are deplying, ensure you copy your license keys to the machine before the BO custom action which checks for them. The property for the license key location is LICENSEDIR.
Although BO 6.5.1 comes with a msi, it's best to repackage the app (if you install only on one kind of OS). The vendor msi is filled up with cabfiles and file references to it. also the language versions are very hard to delete (if you only need the UK version) I repackaged with Wise package studio. Remove the following files/keys. everything under the user: My Documents\My business Objects.... everything under windows\profile All current user registry keys. You can capture the regkey for the registration and add this to the installation.(I put also an active setup exe for this key in the package (search for active setup on the forums)) BusinessObjects has his own repairfunctons for the usersettings so don't include them in youur package. if you do you end up with msi repairing BO and BO repairing msi. Also the APC62.DLL gave me some errors on XPPro removing this component was the solution. Cheers! SV
View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.