Issue 23780

I run roaming profiles in my Windows-network, and the roaming profile's path 
is "connected" to the Windows %USERPROFILE% variable.  I see OpenOffice uses 
the sversion.ini file to tell where OO is installed. However, this might not be 
a good solution, considering that the Profile dirname might change. This is due 
to the fact that sometimes Windows have another profile with the same name, 
which might be an old profile "hanging around", e.g. the old user lost it 
connection to the server during synchronization with Roaming Profile network 
container.   Or maybe there are several duplicate usernames, but all are from 
different thrusted domains..  Windows then uses e.g. C:\Documents and 
Settings\username.DOMAIN  to sort them out..    

OpenOffice should be as any other Windows application; trust the %USERPROFILE% 
variable.

So, how about activating some kind of %USERPROFILE% variable-support in 
sversion.ini ?  It would certainly help me and all my desktops. Now I have to 
make some kind of user-loginscript that alters this sversions.ini EVERY time a 
user logs in (vbscript that gets the profile dir and fixes the sversions). This 
is really not the best choice for me, who live in an environment where my users 
are also managed by other domain-admins in other trusted domains, where i have 
no control over loginscripts (yes we are a BIG domain with tens thousands of 
users).