We are attempting to test BO in an NT Terminal Server environment. In order to avoid corruption of the objects.lsi file on the server we are attempting to redirect the app to each users directories on a shared file server. So instead of the app looking for the objects file in C:\Program Files\Business Objects\Business Objects 5.0\LocData it would look out on a UNIX file server where the objects file has already been copied.
BO had instructions to change the registry setting but they were for 4.1 not 5.0. The registry structure is not the same. We tried changing HKEY_LOCAL_MACHINE\SOFTWARE\Business
Objects\Shared\General\5.0\Directories\Local Data Directory with no success.
The bad news is, you cannot set this up as part of the automated Master install. Already tried to do this, however
There is a bug wherein the client setup will be ignored for locdata / shdata locations and take on the path for the master setup AND 2. With version 5.0 they removed the ability to the location and settings of these
What you need to do is after each client installation, run locally to the client and
Ensure the Objects file is local not shared 2. Modify the directory path of LocData to the server, making sure you manually create the appropriate directory structure on the server first
You CAN modify the default settings for a master install for V5. Check the Security.key file. You certainly don’t need (and definately don’t want) to modify every client after an install. You are, as far as I remember, correct in that you can’t do it directly through the automated install though.
Regards
Jonathan
Project Leader
Group Medical, Regulatory and Product Strategy IS.
What kinds of problems have you had with the Master Installation on v5.0? I haven’t encountered anything like you’re describing below. I also have Article #1684 at Online Customer Support (http://www.techsupport.businessobjects.com). It explains how to modify the setup files in order to customize the client installations.