When deploying only Desktop Intelligence or Designer you can reduce the size of your package more than 85% by removing unnecessary cab files used for other install features. Designer requires … Read More

When a new user log in the machine a self-healing operation may begin. To stop this you should edit .mst file to contain the following property values: ReinstallRepain = o UIReinstalMode = o … Read More

BOXI R2 - Using Desktop Intelligence to retrieve a report with a locked down account generates an abort. This is due to a temp file trying to be created on root of C: - fixed with BO Fixpack 2.4 Read More

I needed DotNet1.1 installed as a pre requisite Read More

The Client package is supported for silent installs. I found a way to do this - use the following PROPERTIES for installing the Client (English) : CLIENTLANGUAGE=EN INSTALLLEVEL=4 INSTALLSWITC… Read More

In Order to install any of the tools associated with the XI R2 SP1 11.x suite a command may be run against the .Exe to achive a nearly fully silent install.... For a Single Client Tool: "<Pa… Read More

According to BusinessObjects documentation, an INSTALLLEVEL of 4 is enough for client tools. Read More

We have noticed that users need write access to C:\Program Files\..\BusinessObjects Enterprise 11.5\win32_x86 if you use the Import Wizard. Import Wizard creates log files under that folder. A… Read More

For your information, although BO Xi R2 is not supported on Citrix Presentation Server 4.0 (OS: W2K3 Standard Edition), we have successfully installed it on that platform, without any other cus… Read More

Had to set the INSTALLLEVEL to at least 5. The default for INSTALLLEVEL is 3, and some of the features have an install level of 4 and 5. Read More

The INSTALLSWITCH property is case sensitive. For client installations the “Client” is the appropriate setting. If specify the setting correctly you will not need to use the PIDKEY property. Read More

The INSTALLSWITCH property is case sensitive. For client installations the “Client” is the appropriate setting. If specify the setting correctly you will not need to use the PIDKEY property. Read More

Found that changing the CLIENTLANGUAGE property resolves issues with the MITMIN30.DLL file. In our instance we set CLIENTLANGUAGE to EN however there are other language versions. In the initia… Read More

The Client package is not supported for silent installs. (Although the server is.) I found a way to do this - use the following: msiexec /I "...\win32\BusinessObjects.msi" TRANSFORMS=:1033 INS… Read More

If someone wants to use the MSI file without the Setup.exe, for an example, deploying Business Objects using GPO or to run the MSI with the /qb switch? Create an MST and peform the following c… Read More

We ran into all sorts of issues getting this package to install using an MST. Here are the settings we used to create a succesful package. I. Opened the MSI using Wise Package Studio. II. D… Read More