Subject: RE: scriptable setup using configfile in multiuser XP installation
After a bit of experimenting with Multi-User R6 client installs, I learnt thatthere is a virgin data directory at
“%ALLUSERSPROFILE%\Application Data\Lotus\Notes\Data\Shared”
and a virgin notes.ini at
“%ALLUSERSPROFILE%\Application Data\Lotus\Notes\Data\notes.ini”
When each users launches the notes client for the first time, the virgin data directory
is copied to “%USERPROFILE%\Local Settings\Application Data\Lotus\Notes\Data”,
and the virgin notes.ini is copied into this new data directory, and the user is guided
through the client configuration wizard.
Next time onwards, each user gets to run notes client, with their individual data directory.
This much works fine.
The number of user interactions with the client configuration wizard can be minimized by
setting parameters in a file ( for example: config.txt ) and adding a parameter to the
notes.ini, ConfigFile=\config.txt.
I created such a file with parameters common to all users, and placed it under
C:\Documents and Settings\All Users\Application Data\Lotus\Notes\Data\config.txt
and added the following line to the virgin notes.ini
ConfigFile=config.txt
Since notes.ini and config.txt were getting copied to the user’s data directory, I was
expecting that the client configuration wizard would find it there.
However it doesn’t seem to work that way.
So I hardcoded the path as follows
ConfigFile=C:\Documents and Settings\All Users\Application Data\Lotus\Notes\Data\config.txt
This only works for Administrator, but not for normal XP users. I verified that the user is
able to open this config.txt file at the Shared data directory using Windows Explorer,
and also using cmd shell. The %ALLUSERSPROFILE%\Application Data directory is a hidden directory
in XP.
Could this be the problem why the settings in config.txt are not respected ?
I would appreciate help in solving this issue, since this problem/bug almost nullifies the
power of ConfigFile parameter, where it can be most useful.