Apache OpenOffice (AOO) Bugzilla – Issue 16139
%username% not interpreted in terminal server sessions
Last modified: 2003-07-25 07:29:51 UTC
Windows 2000 terminal server environment with redirected "Application Data" places sversion.ini and workstation installation into wrong directory. The location of %username% is ignored. Example: Per group policy the default location for "Application Data" is redirected to \\enterprise02\export\%username% During setup the application proposes \\enterprise02\export\starofficeX as installation directory. The username is ignored. Accepting this location fails (unable to create the directory) Correcting the target directory manually to \\enterprise02\export\username\starofficeX allows to create the diretory, the installation completes. After the installation the file sversion.ini is placed in \\enterprise02\export\ (in the root of "Application Data") in the same level as the userdirectories. This means, that one sversion.ini is shared by all users and points to the user who was first to install the application. The structure is: <pre> \\enterprise02\export - sversion.ini - user1-dir - office-dir - user2-dir </pre> user2 would run the office from user1. OBR indicated this could be a problem in security.c I would like to see this one fixed in the coming release, i think it's essential.
Retarget to 1.1
Retarget to rc, this is a killer for citrix.
Hi *, seems to be a configuration problem of the Active Directory, Group Policy or what ever. OOo uses osl_getConfigDir which uses a standard windows function (SHGetSpecialFolderLocation) to retrieve the location of the user configuration directory. The Windows "Logo" guidelines recommending to use this method to retrieve standard user directories. In case of the special machine SHGetSpecialFolderLocation delivers exactly the directory which will be considered wrong. Kind Regards, Tino
It really appears to be a problem with AD and the local registry. The registry is out of sync. While Windows itself appears to access AD directly to get the location of the AppData-directory, we are reading the registry which contains outdated information. However, this is a Windows problem. As soon as the registry key is corrected manually, it works as expected. Closing the issue.
.