random technology [RT]

I’ve recently encountered an interesting issue in regards to the @user.home variable used via deployed eclipse code. After some investigation – we found the @user.home was not pointing to the users home directory. In fact it was specifically pointing to the home directory of the Administrator account.

Example (the issue):
Lets assume a user by the name qa_sample was accessing the server and osgi.instance.area was set to @user.home/eclipse. We can expect any application relevant files would be written to c:/users/qa_sample/eclipse since this is a Windows Server 2008 R2 build. Instead the application running under the context of a user with non administrative rights was attempting to write to c:/users/administrator/eclipse.

Java as it pertains to @user.home:
JRE looks first at HKCU/Software/Windows/CurrentVersion/Explorer/Shell Folders/*. You should see any of the values within Shell Folders have the users name “C:\\Users\\qa_sample\\AppData\\” and not “C:\\Users\\Administrator\\AppData\\”.  Now it gets better – an obvious fix would be to correct these paths right? And perhaps just import a registry key at logon using regsvr32 /s ./path/fix.reg but unfortunately that does not work either as we get the following error.

How could this be happening? It works fine in the UAT environment (note the UAT environment is Server 2003). Could this just be a botched up build deployed via Alteris, or perhaps did the person who initially build this server use in improperly cloned/sysprepped image? The only logic I have for that is the default Administrator is renamed. “The module c:\..\shell_fix.reg may not compatible with the version of Windows that you’re running. Check if the module is compatible with an x86 (32-bit) or x64 (64-bit) version of regsvr32.exe.” As a fix to this – simply run the following command > reg add “hkcu\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders” /v “Local AppData” /t reg_sz /d “C:\\Users\\%USERNAME%\\AppData\\Local” /f/, or instead of using regsvr32, use reg import > reg import “C:\shell_fix.reg” to get past the above error.

How we fixed this issue:
At logon, we setup an alternate drive mapping and updated the config file for the application.  Here is the logon script. remember, the drive letters can be changed around as needed.
:: Logon script
md %userprofile%\ecipse
subst i: %userprofile%\eclipse
Now on the config.ini file – we simply changed the call from osgi.instance.area=@user.home/eclipse to osgi.instance.area=i:/. After the update was made, everything was corrected and the application functioned as expected.

logger.path.to.store.file=C:/myapp/,yyyy-MM-dd-HH.mm.ss.SSS z