Squidly_Man's Posts

It appears this may be broken in this version of ThinApp. There are two ways to work around this: Create a drive mapping, either in a login script for the users needing this drive mapping... See more...
It appears this may be broken in this version of ThinApp. There are two ways to work around this: Create a drive mapping, either in a login script for the users needing this drive mapping, or within the ThinApp package (see the ThinApp Blog Article, "How to Map a Drive within a ThinApp Packaged App"). You'll need to reconfigure the entry point for the app within your ThinApp project's PACKAGE.INI file to use this drive mapping as well. Oh...and before you actually run BUILD.BAT, the drive needs to be mapped for ThinApp to see this file as the proper "Source". Use a Shell Wrapper such as ShellExecute.exe (download and use at your own risk) or a custom ThinApp Wrapper (not officially supported by VMware). -Dean F.
You may wish to review the recent blog article "How to Package a NON-Executable File Such as a Document or Spreadsheet". It doesn't directly talk to your issues but it does discuss similar types... See more...
You may wish to review the recent blog article "How to Package a NON-Executable File Such as a Document or Spreadsheet". It doesn't directly talk to your issues but it does discuss similar types of issues and possible resolutions. -Dean F.
Forgive me here...but I'm not quite certain I understand what you are attempting to have occur. Could you explain a bit more? Did you want the ThinApp package to register to the workstation eve... See more...
Forgive me here...but I'm not quite certain I understand what you are attempting to have occur. Could you explain a bit more? Did you want the ThinApp package to register to the workstation even though it is sitting on a UNC path (and create a shortcut to itself)? Or was there something else I missed? As for running a scripted process, ThinApp will support VBS scripting - so anything you script will fire up within a ThinApp. See the ThinApp blog articles on scripting at . -Dean F.
Well...I was going to write up the steps here...but as I began doing so I realized it was a good blog entry. So...here it is: http://blogs.vmware.com/thinapp/2010/02/how-to-package-a-non-... See more...
Well...I was going to write up the steps here...but as I began doing so I realized it was a good blog entry. So...here it is: http://blogs.vmware.com/thinapp/2010/02/how-to-package-a-non-executable-file-such-as-a-document-or-spreadsheet.html Enjoy! -Dean F.
You can't do this to the file share the ThinApps are in but you can do it to each ThinApp in the share by adding something as simple as "Domain Users" as this will keep the apps from running on a... See more...
You can't do this to the file share the ThinApps are in but you can do it to each ThinApp in the share by adding something as simple as "Domain Users" as this will keep the apps from running on any system which cannot authenticate to your network (even when executing on another A.D. domain). This is because ThinApp embedds the unique group SID and not the group name. -Dean F.
1. Create a backup of your PACKAGE.INI. 2. Edit your PACKAGE.INI file. 3. Copy one of the existing Entry Point sections (for example CMD.EXE). 4. Paste the copied text at the bottom... See more...
1. Create a backup of your PACKAGE.INI. 2. Edit your PACKAGE.INI file. 3. Copy one of the existing Entry Point sections (for example CMD.EXE). 4. Paste the copied text at the bottom of your PACKAGE.INI (Make sure there's an extra empty line between any previous section and this new Entry Point section). 5. Rename this new Entry Point (from CMD.EXE) to your desired name. 6. Remove completely, remark out with a semicolon, or modify the DISABLED= line to read DISABLED=0. EXAMPLE: [[Your_App.exe]|http://Computer Management (ThinApp).exe] Disabled=0 Shortcut=&lt;PACKAGE SOURCE FILE&gt; Source=&lt;SOURCE_PATH_AND_EXE&gt; CommandLine=&lt;SOURCE_PATH_AND_EXE_PLUS_COMMAND_LINE_SWITCHES&gt; Icon=&lt;SOURCE_PATH_AND_EXE_OR_ICO&gt;,&lt;NUMBER_TO_ICON&gt;</span> NOTE: If you wish to change the ICON, add an entry to the Entry Point section called "Icon= " (where the path/file, and numerical value refer to your icon). See the ThinApp Blog article "The PACKAGE.INI File Explained" (). 7. Rebuild your ThinApp Project by running BUILD.BAT. 8. Test the new Entry Point by executing the EXE file created. -Dean F.
Ahhh! Good catch John. I didn't even think to see how you were making your calls to modify the registry. That does make sense... :smileycool: -Dean F.
Scripts embedded within the root of a ThinApp package will always run within the context of the virtual environment (i.e. inside the virtual bubble). Modifying the ThinApp project t... See more...
Scripts embedded within the root of a ThinApp package will always run within the context of the virtual environment (i.e. inside the virtual bubble). Modifying the ThinApp project to add those registry keys as previously stated will, in this scenario, properly set the isolation levels upon those keys so that any changes made to them (whether by the app or by the embedded script) will remain within the virtual environment. Some things to remember (for anyone reading this); A ThinApp packaged application can be configured to keep all runtime modifications within the virtual bubble or allow any number or type of runtime modifications be made out on the native environment if that is desired. This is in part because ThinApp packaged applications can be configured to isolate all or some (or, if you want, even none) of the application's utilized files or registry entries by setting isolation levels upon individual registry keys and folders in the file system. Isolation levels essentially define what the packaged application can see and do on the native system (i.e. outside the virtual bubble). An anology I like to use is; think of yourself as the application and you're standing inside a bubble. You don't see the bubble but you see the effects of the bubble - the bubble being created by the ThinApp Virtual Operating System. If FULL ISOLATION is set, that means you, the app, cannot see or modify anything outside the bubble (on the native system). If MERGED isolation is set, you, the app, can not only see, but affect changes to the native system. With WRITECOPY isolation, ThinApp basically tricks the app to thinking it has complete access to the native system but actually takes a copy of that file/registry setting and writes it to the ThinApp Sandbox (which is also part of the virtual bubble) for the app to modify as necessary. So, in a sense, WRITECOPY is a read only state on the native system. Following this logic process a step further, one can also deduce that ThinApp has an order of precedence in that if a registry setting/file exists both in the virtual bubble and on the native system, the one within the virtual bubble will take precedence over that of the native setting or file. Lastly, isolation levels are set per registry key or per folder on the file system and are inheritable. Hope this helps! -Dean F.
JohnFx, You'll need to modify your ThinApp project registry hive text files (one or both depending upon the registry keys you're modifying in your script) to add the settings' parent key(s) wit... See more...
JohnFx, You'll need to modify your ThinApp project registry hive text files (one or both depending upon the registry keys you're modifying in your script) to add the settings' parent key(s) with ISOLATION_WRITECOPY or ISOLATION_FULL to the header of the registry key line. For example, if I'm writing mods to the HKLM\SOFTWARE\VMWARE key with a script, and I want these values to be stored in my ThinApp package's Sandbox vs. the native system's registry, I need to modify the HKEY_LOCAL_MACHINE.TXT file and ensure the parent key (HKEY_LOCAL_MACHINE\SOFTWARE\VMWARE) is present in the registry hive file with a value of ISOLATION_WRITECOPY (in case I wish to see what's on the native as well as what I write to the virtual registry hive) or ISOLATION_FULL (in the event I only want my app to pull settings from the virtual registry and not see what's in the native system). Alternatively, you can also try the following in your PACKAGE.INI: Read the online docs for more information on the above (see the link below). -Dean F.
All ThinApp related script examples on the ThinApp blogs can be found here: http://blogs.vmware.com/thinapp/scripts Including a THINREG Logon Script Example. -Dean F. http://pub... See more...
All ThinApp related script examples on the ThinApp blogs can be found here: http://blogs.vmware.com/thinapp/scripts Including a THINREG Logon Script Example. -Dean F. http://pubs.vmware.com/thinapp4/help