I thinstalled an application using v4.6 and I am able to launch and run the captured application. ![]()
But the application creates some log files at:
c:\program files\ensembleProAgent\LOGS\
So can I access these on ThinApp's the virtual drive?
If so, any assistance is appreciated, I don't know where the virtual drive is or how I can access/ browse it.
Thanks
Joel
Hi
A virtual drive in the world of ThinApp means a drive that you have virtualized so it will be present for the virtualized application. If you mean by the word virtual drive where we keep changes not applied to the physical environment are you talking about what we call the Sandbox. Default location would be in the users Roaming Profile and in a folder called Thinstall (ThinApp used to be called Thinstall before VMware acquired the product).. Fastes method to get to the Sandbox would be to hit Start - Run on your client and enter %AppData% and click on OK..
Hi
A virtual drive in the world of ThinApp means a drive that you have virtualized so it will be present for the virtualized application. If you mean by the word virtual drive where we keep changes not applied to the physical environment are you talking about what we call the Sandbox. Default location would be in the users Roaming Profile and in a folder called Thinstall (ThinApp used to be called Thinstall before VMware acquired the product).. Fastes method to get to the Sandbox would be to hit Start - Run on your client and enter %AppData% and click on OK..
Would it be better if application saves LOGS into native system?
If so, you need to change isolation mode in your ThinApp Project. Look into ThinApp project, go to directory %ProgramFilesDir%\ensembleProAgent\LOGS\ (just create it if it doesn't exists) and create file in it called ##Attributes.ini with following content:
[Isolation]
DirectoryIsolationMode=Merged
Rebuild project and your log files will be created on native system instead od sandbox.
Have a nice day,
Hi,
In this situation i would not advise to save the files to the native file system.
In general your answer is correct to try to store temporary or logging files tothe native system as it prevents the sandbox from exploding due to continiously growing disk space usage. For example having 25 MB of temp files for 1000 users is quite some space. Especially if this is for 100+ apps. Cleaning a single TEMP-folder in the profile is simpler than cleaning 100 sandboxes temp folder, for 100 applications... And there are common tools for doing that.
In this case however the logging is stored to the program files folder, which is protected (read only) for normal user accounts (non local admin) on vista and win7. So the application could throw errors to the user when saving the files there or the user must have specific permissions (which is not advised to be able to simply deploy the app).
It would be best to redirect the logging either to a networkdrive or a personal (profile) folder like %appdata%/enteryourpathhere... If possible of course.
And make sure that folder is in merged mode like Cievo stated...
Kind regards,
Michael Baars - Comprehensive ICT Solutions (Weert NL)
(Please remember to mark the post answered if so and reward points to those who helped you...)
This is EXACTLY what I needed. Yes, I meant the sanbox and not virtual drive. I found my logs and I thank you for the very fast and informative response.
