<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Theike Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Theike Tracker</description>
    <pubDate>Sat, 25 Nov 2023 10:06:36 GMT</pubDate>
    <dc:date>2023-11-25T10:06:36Z</dc:date>
    <item>
      <title>Re: Outlook 2003 ThinApp Reading Pane Issue</title>
      <link>https://communities.vmware.com/t5/ThinApp/Outlook-2003-ThinApp-Reading-Pane-Issue/m-p/345713#M472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As a side-note:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have the best experience by having Microsoft Office installed native. This as many applications do intend to integrate with office or require certain functionalities (like 'send a mail'). Having to make these functionalities available externally is quite a pain...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During migrations we often on the other hand do have to provide certialn parts of office for backward compatibility. For example access to open the 'old format' database as the new local version will intend to upgrade the DB on open, corrupting it or making it no longer accessible for the users of the old version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For outlook we in general have no real issues as long as the best practices are followed. These can be found on the link provided by Lakshman (credits to him). Just keep in mind that a 2GB mailbox will end up in your sandbox... If this is in your (roaming) profile be prepared for long login times!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Mar 2012 18:19:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Outlook-2003-ThinApp-Reading-Pane-Issue/m-p/345713#M472</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2012-03-27T18:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: ##Attributes.ini on an empty folder</title>
      <link>https://communities.vmware.com/t5/ThinApp/Attributes-ini-on-an-empty-folder/m-p/1281514#M3245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As an addition to the above correct answers:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you take into account that ThinApp does provide 2 major solutions to application deployment:&lt;/P&gt;&lt;P&gt;- Distribution as a single file container&lt;/P&gt;&lt;P&gt;- Sandboxing 'all' changes the application makes at runtime&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main reason for problems is the sandboxing. You want to prevent your system to be 'corrupted' due to an application running (like changing registry entries or altering system files), but if you type a word document you want to be able to have this file in your 'my documents'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The default folders you see are there to provide a basic usable platform. For all folders you don't see in the project folder (all the %...%-folders), the setting you specify during the post-capture snapshot are applied. Same for folders that don't have a attributes.ini in it, like %drive_C% often has as only a sub-folder is added.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You do NEED some of the folders to be available. For example, if you delete %SystemSystem%/Spool, you will not be able to print...! Similar having %Personal% as writecopy will have your documents end up in the sandbox instead of on your system. You will have to understand the workings of isolationmodes to be able to determine what the effect will be for deleting or even altering the default settings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general my experience is that the defaults are quite OK. Some things I have a different opinion about are for example the temporary internet files and normal temp files. This as it is easier to clean the system of these unwanted files and there are numerous tools doing this already, but none do this for sandboxes. Similar i want our users to share the favorites, cookies and so on with their local system, except when providing a secured browser as the users otherwise complain 'where are my' or 'why can't i'...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;Please mark the question answered if so and reward points if it helped you...&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Mar 2012 16:11:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Attributes-ini-on-an-empty-folder/m-p/1281514#M3245</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2012-03-20T16:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: Packaged with 4.6.1 and 4.6.2 same package creates a processes with a different name.</title>
      <link>https://communities.vmware.com/t5/ThinApp/Packaged-with-4-6-1-and-4-6-2-same-package-creates-a-processes/m-p/1274188#M3125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your post has not been answered yet. Unfortunatly tour problem is not realy clear, some possible hints:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First: Are you sure you did the exactly same capture...? Did you disable the Java Auto-update for example?&lt;/P&gt;&lt;P&gt;Started background services (services installed with the auto-start option, apps in the startup or in the 'run' key of the registry) might be started in the background upon application start, showing up as another 'application' in the taskmanager.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the above is not the case: have you tried re-building the original project using 4.6.2. This rules out it is a difference in&amp;nbsp; the capture/project and makes it a clear difference in the engine. Maybe also the name of the main entry point/package was changed as this the name the spawned apps are shown. Maybe they are started as well, but using a different name due to the setting "&lt;SPAN style="font-size: 10pt; font-family: arial,helvetica,sans-serif; "&gt;ProcessExternalNameBehavior&lt;/SPAN&gt;" in the package.ini.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards and good luck,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;Please remember to mark the post answered if so and reward points to those who helped you...&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Dec 2011 15:19:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Packaged-with-4-6-1-and-4-6-2-same-package-creates-a-processes/m-p/1274188#M3125</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-12-02T15:19:42Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Rosetta Stone</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Rosetta-Stone/m-p/2618540#M6807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;TCP Sockets in general are no problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be an issue is port number assignment. If the ports are defined in the service ports table (Windows-system32-drivers-etc: services-file). If changes are applied to this file (like service "myservicelistenport" on port 1234), this will not be used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ThinApp lets the OS do all socket handling. This means that services (portnumbers) and IP-assignments (hosts-file) are not honored when defined in the virtualisation layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #999999;"&gt;&lt;EM style="font-size: 8pt; "&gt;Please mark the post answered if so and reward points to those who helped you...&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Dec 2011 18:40:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Rosetta-Stone/m-p/2618540#M6807</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-12-01T18:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: Thinapp Sandbox Clean Up</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinapp-Sandbox-Clean-Up/m-p/2067026#M4971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have the same issues on several of our customers locations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we do is that we have lists of active applications, as well as 'old' applications. The sandboxes get renamed for every new release of a virtualised application (we don't re-use existing sandboxes as for example updated isolation modes would not be applied). This makes that the number of&amp;nbsp; unused sandboxes is in general larger than the number of active ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In our case we advise our customers to place sandboxes on some share using a general naming policy (in general by setting the sandbox redirect environment variable). The sandboxes are thus stored in something like \\server\share$\% username %\sandboxes\(sandboxname).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we have 2 simple scripts:&lt;/P&gt;&lt;P&gt;The first one loops through the folderstructure that matches a given naming policy. This dumps sandboxname, size and last access date&lt;/P&gt;&lt;P&gt;This can be imported i excel, access or whatever 'inteligent' tool to determine the extreme sandboxes (old (aka: unused apps), large (invalid sandbox policy applied), average size, total size/sandboxname, ...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second script is cleaning up sandboxes, matching sandboxes in the given location agains a list of sandboxnames to be cleaned. This is only used to delete ALL sandboxes for a given application (sandbox identifier). Individual sandboxes are removed only manual (for example when extreme in size due to updating the virtualised app, which should never be done by a user)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These scripts do need adaption for every location, but are simple to create yourselves. I have done similar actions in VBscript as well as Powershell and the basis should operational within a few hours for a handy scripter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #999999;"&gt;&lt;EM style="font-size: 8pt; "&gt;(Please mark the question answered if so and reward points to those who helped you)&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Oct 2011 13:43:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinapp-Sandbox-Clean-Up/m-p/2067026#M4971</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-10-28T13:43:08Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple MS Access Versions Through ThinAPP</title>
      <link>https://communities.vmware.com/t5/ThinApp/Multiple-MS-Access-Versions-Through-ThinAPP/m-p/2628028#M6924</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your problem is the association, which is one of the biggest issues in deployment land.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will not be able to get this completely right by 'just' extension association. There will always be a fight which version will catch the doubleclick. (and this is why we don't use thinreg or MSI deployment in our managed environments at the customers).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case there are 2 possible actions:&lt;/P&gt;&lt;P&gt;If you have a desktop manager in place (which handles the desktop/start menu), add a shortcut&amp;nbsp; for the users in your development team that opens the database using the 2003 thinapped version of access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise create a 'start me' shortcut next to the DB (which also starts the thinapped 2003 access) and use that one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At last: your developers should NOT use doubleclick on the db anymore!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our best practice is to provide users with managed shortcuts anyway. This way you are in control how items are opened, and the next migration allows you to specify how databases (, ...) are opened, and with what app.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;(Please mark the question answered if so and reward points to those who helped you...)&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Oct 2011 08:19:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Multiple-MS-Access-Versions-Through-ThinAPP/m-p/2628028#M6924</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-10-17T08:19:45Z</dc:date>
    </item>
    <item>
      <title>Re: Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647116#M7222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also would advise to always keep the original project (folder with package.ini and %...%-folders).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is much more powerfull and allows you to afterwards fix issues, that require updating settings (files, isolation mode, registry, settings in package.ini). The 'bit' of extra space needed with the new versions should not be the main issue btw. Switching to 'disk'-optimalisation (=compress) does have other negative effects, like additional CPU resources needed to unpack the required files. Be carefull not to pick the option that backfires in the long run...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And besides when you package tiny apps (like CMD) a few more MB for the package is not nice, but in general with nowadays storage capacities is not the biggest issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #808080;"&gt;&lt;EM style="font-size: 8pt; "&gt;Please remember to mark the question answered if so and reward points to those who helped you...&lt;/EM&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 14:40:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647116#M7222</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-09-05T14:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: How can you deploy a ThinApp version of visio without breaking the per device license?</title>
      <link>https://communities.vmware.com/t5/ThinApp/How-can-you-deploy-a-ThinApp-version-of-visio-without-breaking/m-p/334364#M427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With ThinApp 'unlicensed client' is a little vague:&lt;/P&gt;&lt;P&gt;Every user/system that starts the virtualised application requires a license, but there is no 'on forehand' limitation on this. You have to ensure you stay within the in the EULA and ordered license counts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to rephrase the question to: How do I prevent my app is used on non-company managed systems there are some ways:&lt;/P&gt;&lt;P&gt;The simplest one is to 'just' add the Domain users-group from your AD to the 'PermittedGroups'-setting in the package.ini. Please check the user manual on how to use. (tip: use the SID-value) This prevents leaking the virtualised application from your managed network (where you own licenses for)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternatively you could include some more advanced licensing tools, which check and limit the access and starting of applications. Software like the one from &lt;A href="http://www.softwarekey.com/"&gt;http://www.softwarekey.com/&lt;/A&gt; could be your solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general: Applications that require your server backend will not be 'borrowed' for home usage, as most users don't have your company infrastructure at home. It is more the 'generic' handy applications (like office, Adobe CS4,...) which tend in this direction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps. My first advise would be: add the domain users-group. We found it mostly solving the issues. Additionally we use a desktop manager which hides most of the deployment of applications from users, raising the bar of drive by borrowing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;Please remember to mark the post answered if so and reward points to those who helped you...&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2011 14:49:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/How-can-you-deploy-a-ThinApp-version-of-visio-without-breaking/m-p/334364#M427</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-08-25T14:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: Release file locks</title>
      <link>https://communities.vmware.com/t5/ThinApp/Release-file-locks/m-p/326396#M383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are several ways to prevent apps from 'locking' your system.&lt;/P&gt;&lt;P&gt;Several processes are well known in this issue, like ctfmon.exe or mdm.exe. As these are not essential to the virtualised application these can be easilly 'deactivated' by adding them to the process exclusion list, so they are always run natively.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally there might be less obvious ones, like MS Word. Initially you open a document from your virtualised application (so the native installed word runs within your virtualisation context). Next while that document is open you open a new/existing one natively (you double-click on a document from the explorer). You would expect this document is opened in a native version, but Word tries to save resources and extends the running instance to also edit the new document, so it also runs virtualised. When you close the app and the document (the initial one), your sandbox is still locked by the latest document...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The later issues can be solved by adding word to the exclusion list as well, but if plugins have to be loaded which are only available within the virtualisation context, you will have an issue...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards, Michael Baars&lt;/P&gt;&lt;P&gt;Comprehensive ICT Solutions (Weert, NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;Please remember to mark a question anserwed if so and reward points to those who helped you...&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2011 08:05:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Release-file-locks/m-p/326396#M383</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-08-15T08:05:25Z</dc:date>
    </item>
    <item>
      <title>ThinAppTemplater released</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinAppTemplater-released/m-p/2582242#M6476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Via this way I want to inform you that ThinAppTemplater has been released to public. Similar to ThinAppHelper the ThinAppTemplater is a tool that supports the ThinApp process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 weeks ago ThinAppHelper has been released with some hard needed updates. ThinAppHelper aims mainly the starting ThinApp users as all the basic settings can be altered or set using a graphical interface instead of having to edit the various textfiles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After some time using however you will notice that ThinAppHelper misses some features. One of the most anoying items in the ThinApp process is that you have to apply the same settings over and over again. The ThinAppTemplater helps in this as it allows to apply templates to ThinApp projects. This way additional settings will be merged to the project's INI-files (package.ini, ##attributes.ini) and folders will be created/files copied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Feel free to download the ThinAppTemplater from the ThinAppHelper website.&lt;/P&gt;&lt;P&gt;Website: &lt;A href="http://thinapphelper.cis.nl"&gt;http://thinapphelper.cis.nl&lt;/A&gt;&lt;/P&gt;&lt;P&gt;(Choose your language and select ''Tools')&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The download is a zip-file containing the application, releasenotes (including basic manual) and a sample template/project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know what you think about it as a reply on this post, via the contactform on the site or email (&lt;A href="mailto:thinapphelper@cis.nl"&gt;thinapphelper@cis.nl&lt;/A&gt;). Please also register for the ThinAppHelper newsletter as we will send updates about additional tools as well!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Michael Baars, Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #808080; font-size: 8pt; "&gt;(If you need support or training in the Netherlands on VMware ThinApp feel free to contact us: &lt;/EM&gt;&lt;A href="http://www.cis.nl"&gt;&lt;EM style=": ; color: #808080; font-size: 8pt; "&gt;&lt;/EM&gt;&lt;/A&gt;&lt;A href="http://www.cis.nl" target="test_blank"&gt;http://www.cis.nl&lt;/A&gt;&lt;EM style=": ; color: #808080; font-size: 8pt; "&gt; )&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jun 2011 10:26:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinAppTemplater-released/m-p/2582242#M6476</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-06-30T10:26:52Z</dc:date>
    </item>
    <item>
      <title>ThinAppHelper: New release</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinAppHelper-New-release/m-p/289809#M140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoNormal"&gt;It has been a long time since the last message regarding the ThinAppHelper. Recently however development has been picked up again. This resulted in the release of a new version of the ThinAppHelper.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;This new version is mainly a patch-up version fixing the long overdue issues. This version finally fixed the issues that prevented ThinAppHelper to be used with the latest releases of VMware ThinApp. As an extra it has received a visual makeover and easing the access to the core functionalities.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;ThinAppHelper mainly eases the configuration process for starting VMware ThinApp users. The most common configuration items can be edited using a graphical user interface instead of the various textfiles. Similar folders and registry can be reviewed and altered.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Feel free to download ThinAppHelper from the ThinAppHelper website (changed!):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="http://thinapphelper.cis.nl/"&gt;http://thinapphelper.cis.nl&lt;/A&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Also contact information has been changed. So for contacting us please use:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The contact-form on the website or&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;by email: &lt;A href="mailto:thinapphelper@cis.nl"&gt;thinapphelper@cis.nl&lt;/A&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P&gt;Of course we will continue development on ThinAppHelper again and add new functionalities. If you have feature request or find an issue we encourage you to inform us using the above methods…&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;It has been a long time since you received the last newsletter/message regarding the ThinAppHelper. Recently development has been picked up again. This resulted in the release of a new version of the ThinAppHelper.&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;This new version is mainly a patch-up version fixing the long overdue issues. This version finally fixed the issues that prevented ThinAppHelper to be used with the latest releases of VMware ThinApp. As an extra it has received a visual makeover and easing the access to the core functionalities.&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;Feel free to download ThinAppHelper from the ThinAppHelper website (changed!):&lt;/P&gt;&lt;P class="MsoListParagraph" style="text-indent: -18pt; margin: 0cm 0cm 0pt 36pt; mso-list: l0 level1 lfo1;"&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A href="http://thinapphelper.cis.nl/"&gt;http://thinapphelper.cis.nl&lt;/A&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;Also contact information has been changed. So for contacting us please use:&lt;/P&gt;&lt;P class="MsoListParagraph" style="text-indent: -18pt; margin: 0cm 0cm 0pt 36pt; mso-list: l0 level1 lfo1;"&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The contact-form on the website or&lt;/P&gt;&lt;P class="MsoListParagraph" style="text-indent: -18pt; margin: 0cm 0cm 0pt 36pt; mso-list: l0 level1 lfo1;"&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by email: &lt;A href="mailto:thinapphelper@cis.nl"&gt;thinapphelper@cis.nl&lt;/A&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0cm 0cm 0pt;"&gt;&lt;/P&gt;&lt;P&gt;Of course we will continue development on ThinAppHelper again and add new functionalities. If you have feature request or find an issue we encourage you to inform us using the above methods…&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM style="color: #808080; "&gt;Note: ThinAppHelper is created and maintained by Comprehensive ICT Solutions BV (NL) and is no VMware product. It is available for free...!&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 14:11:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinAppHelper-New-release/m-p/289809#M140</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-06-17T14:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Thinreg performance impact/benchmark</title>
      <link>https://communities.vmware.com/t5/ThinApp/Thinreg-performance-impact-benchmark/m-p/288771#M130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My advise to you would be not to use thinreg for this purpose to prevent experiencing and having to debug quite some undesired behaviour...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;A user gets both office 2007 (registering .doc and .docx) and office 2003 (only registers .doc).&lt;/P&gt;&lt;P&gt;What will happen if the user doubleclicks a .doc file...? This will depend on the order the thinregs will be performed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So apart of performance, i would advise getting some desktop managing tool. As a professional company we are using the RES Software packages for this, which also help us with the distribution of the applications using the automation manager. (But there are quite some other tools available as well, even for free)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for the performance i assume the determining which applications have to be registered wil require just as much time as the real registration. You will have to lookup the users permissions (domain group membership?) and depending on that activate the registration. Doing this for a large group of applications is quite time consuming as well, even if you have only a few applications assigned...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;(Please mark the question answered if so and reward points to those who helped you)&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jun 2011 11:57:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Thinreg-performance-impact-benchmark/m-p/288771#M130</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-06-17T11:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: How To Virtualize Xilisoft iPad Magic Software</title>
      <link>https://communities.vmware.com/t5/ThinApp/How-To-Virtualize-Xilisoft-iPad-Magic-Software/m-p/1707497#M4409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunatly the information you provide does not give enough information for a good answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How does the system you are capturing on look like (what os, installed other software)? Advise: a clean, fresh Windows XP SP3 will do. Check the 'clean system' advise in the user manual and/or this post: &lt;A href="http://blogs.vmware.com/kb/2011/06/what-is-a-thinapp-clean-machine.html"&gt;http://blogs.vmware.com/kb/2011/06/what-is-a-thinapp-clean-machine.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And what are 'all' the steps you performed... Please add some additional info including in particular the items where you made a specific choice (for example: which installation choices were made, what is the applied the isolation mode and what entry point have you activated...?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At last what is the exact message you get. And what happens when you try to open the ThinApped application on the system you installed the application on? and on 'the' clean system (aka: same as you did your capture on, set back the snapshot to just before you started the installation... or on a different machine...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At last you can start troubleshooting:&lt;/P&gt;&lt;P&gt;ThinApp has a 'log monitor' included. This generates HUGE log files but might hint you to a possible solution. And Proces monitor might help you identify the file that can't be opened...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To get a more specific answer we need more information from you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck and get back if you have further questions...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #808080; font-size: 8pt; "&gt;(Please mark the question ansered if so and reward points to those who helped you...)&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 12:47:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/How-To-Virtualize-Xilisoft-iPad-Magic-Software/m-p/1707497#M4409</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-06-14T12:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: office 2007 and plugins</title>
      <link>https://communities.vmware.com/t5/ThinApp/office-2007-and-plugins/m-p/2122968#M5356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First i want to make a side note:&lt;/P&gt;&lt;P&gt;We have found that if you are managing complete desktops it is often more practical to exclude MS Office from the virtualisation process. It is used to often by applications (apps that want to send an email message, open a calculation overview in Excel or do a document merge) which is more complicated when virtualised. Also for outlook make sure the PST-files don't end up in the sandbox if you decide to virtualise...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is possible to capture plugins. If you have a virtualised outlook (or other base application, like IE) and want a plugin to be added you will have 2 options:&lt;/P&gt;&lt;P&gt;- Include the plugin in the main capture&lt;/P&gt;&lt;P&gt;This is the most simple version and just do the post-capture after the installation of the addin.&lt;/P&gt;&lt;P&gt;- Capture the plugin as an add-in.&lt;/P&gt;&lt;P&gt;This is more flexible as you can add and remove it from the capture. Always capture a add-in on a system where locally the application (outlook) has been installed. Preferred the same installation used for capturing the application, but not required. (often a quick rebuild next-next-finish installation is sufficient).&lt;/P&gt;&lt;P&gt;Next start the capture, install the add-in (and configure if required) and post capture. This should always be done on MERGED mode as in ThinApp the thighest isolation 'wins', and you don't want to have the addin set the basic isolation (adding the addin makes the documents go to the sandbox for example).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now change the main capture (outlook) and enable the OptionalPlugins (tip: do this by default for the subfolder 'plugins' and files with extension *.DAT). In this case you would not need a rebuild if you ever want to add an addin... Just add the folder and copy the DAT!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This works similar to browser extensions and like there: if you have the application natively available you could use the addin by starting the native application via a entrypoint that starts the local application. For ouotlook i would not suggest this btw...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume you will have to do quite some testing before releasing the addin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards and good luck!&lt;/P&gt;&lt;P&gt;Michael Baars&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;(Please mark the question answered if so and reward points to those that helped you...)&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 11:00:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/office-2007-and-plugins/m-p/2122968#M5356</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-06-14T11:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: error while launching microsoft excel</title>
      <link>https://communities.vmware.com/t5/ThinApp/error-while-launching-microsoft-excel/m-p/2504580#M6005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed your question was not yet answered..&lt;/P&gt;&lt;P&gt;First a welcome to the forums as i notced this is your first post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You state that you created a Excel-capture on remote desktop. I am not sure what youdid exactly, but i assume you did not follow the basic guidelines for packaging. These steps are described rather extensively in the ThinApp user manual, here a short overview:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To begin with a capture should be performed on a system that is as clean as possible, matching the target system. In general you will like capturing on a Windows XP with service pack 3 on a virtual system, which you can reset to a snapshot in seconds. Installation of additional tools (like java, .NET 2.0, 3.x) and others should match the minimal system setting of the target (where the virtualised applications will be started), or less... Also disable all 'background tasks', like automatic updates. And NEVER install tools like virus scanners and similar (on the capture machine, obvious)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally the procedures for capturing Office 2007 have been described on the following VMware blog:&lt;/P&gt;&lt;P&gt;&lt;A href="http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html"&gt;http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars, Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #999999;"&gt;&lt;EM style="font-size: 8pt; "&gt;Please mark the post answered if so and reward helpfull posts by assigning points&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 May 2011 10:52:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/error-while-launching-microsoft-excel/m-p/2504580#M6005</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-05-31T10:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: Installing Thinapp on windows nt 4 sp6</title>
      <link>https://communities.vmware.com/t5/ThinApp/Installing-Thinapp-on-windows-nt-4-sp6/m-p/2113406#M5300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First a welcome to the forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not recently used NT4 anymore but i know the older versions (i think i used 4.0.3) do support it.&lt;/P&gt;&lt;P&gt;Maybe something broke during the later releases and i could understand it if versions are not tested on the platform.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please test using an 'older' version and if applicable file a support request...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;btw: do you get the error during the capture or when running an application? If it is during the run (start app) of an application that does work on XP, it might be the application that is not NT4 compatible... Try installing the application on NT4 locally to verify this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Add-on&lt;/STRONG&gt;: If it is just the installation of ThinApp try the following:&lt;/P&gt;&lt;P&gt;Install ThinApp on XP and copy the VMware ThinApp folder (program files) to the NT4 machine...&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #808080; font-size: 8pt; "&gt;Please mark the post answered if so and reward helpfull answers by assigning points...&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 May 2011 11:59:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Installing-Thinapp-on-windows-nt-4-sp6/m-p/2113406#M5300</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-05-19T11:59:53Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Community (Germany)</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Community-Germany/m-p/2111030#M5292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From my point of view i would rather have a more ThinApp minded focus from VMware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the moment it is more like 'a addon for view'. Yes, it is a good tool, but VMware tries to sell the bundle. Same is for events. Alle events are 'all in' events.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I am mainly ThinApp minded i would love some more focus on the specific item ThinApp (ranging from training to certification) as well as events. On the other hand: companies are free to organise specific events. My employer does so for example... And yes, if there is a nearby event mainly for ThinApp (and Germany is nearby: NL) i think i can make it there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just try to inform VMware as well and maybe they can send some represenative (pbjork?). Then i can finaly shake some hands&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just curious: are you VMware only or 'comparison to cometition' as well? aka: do you want a ThinApp based community or an ApplicationDelivery based one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Count me in, as long as you allow English content... My German is not perfect...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Add-on... Just noted the VMware logo. VMware will be in the loop then i assume...&lt;/P&gt;&lt;P&gt;And welcome on the forums as it is your first post!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 May 2011 00:37:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Community-Germany/m-p/2111030#M5292</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-05-16T00:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: Variable Entry Point</title>
      <link>https://communities.vmware.com/t5/ThinApp/Variable-Entry-Point/m-p/859552#M1654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi and welcome to the ThinApp forums...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To my opinion you are taking a slightly to complex approach on the problem.&lt;/P&gt;&lt;P&gt;A simpler solution would be having a simple entry point that takes your options (local/nw, path, formname) as parameters and launches the process itself. This way you would not have to store the settings nor 'alter' the default entry point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is always nice if an entry point is OK, but if there are dynamic properties, keep them dynamic. I'm not sure if you have some programmer resources as the issue you describe would be something to be completed on a spare afternoon. As the 'commandline' option is used parameters passed on the commandline are not forwarded to the application. If you leave out this parameter, you could just pass the given options and process them in the application. This of course can also be realised in some VB script or similar...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry i don't have a ready-fit solution for you...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM style="color: #999999; "&gt;(Please remember to mark the post answered if so and reward points to helpfull answers...)&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2011 07:37:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Variable-Entry-Point/m-p/859552#M1654</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-05-04T07:37:07Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create File during PostScan</title>
      <link>https://communities.vmware.com/t5/ThinApp/Unable-to-create-File-during-PostScan/m-p/2567879#M6378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With the latest versions of ThinApp (4.5+ i believe) the 256 character limit should be resolved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally to the relocation of ThinApp you could just select another save folder during the post capture steps. My general working steps include storing the captures to the network and i often remap that 'application working folder' containing the installation media, documentation and other files to some X:-drive.This as i hate having to browse through numerous folders before reaching the location for the installation files. And it keeps the save path simple (x:\captures) and short...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tip btw: Make a zip of the initial capture to be able to repair file corruptions later on. I noticed sometimes the files got corrupted during the processing afterwards (used some tools to move files/create patch versions, which did have the 256 char length issue)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tip 2: Install ThinApp to a (network)folder with version information, like c:\thinapp461 and keep older versions&lt;/P&gt;&lt;P&gt;If this is a location that is also available on your build systems it ensures next time the application is rebuilt with the same version of ThinApp as the version will be in the determination process (check the build.bat). We had some problems sometimes rebuilding and the latest edition of ThinApp was used which handled some items a bit different than the version captured with. Now you will have to 'upgrade' manual making you aware some aditional testing might be required...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (CIS) - Weert (NL)&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;(Please remember to mark the post answered if so and reward points to those who helped you)&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Apr 2011 13:37:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Unable-to-create-File-during-PostScan/m-p/2567879#M6378</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-04-28T13:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp package attempting to install when ran</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-package-attempting-to-install-when-ran/m-p/1738619#M4737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ThinApp does not hide the basic operating system but in general allows to run an application allowing it to see a different installbase as realy available. This is done by providing the virtualised application the real filesystem &amp;amp; registry overlayed with the differences captured during the 'install/capture' phase.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general the MS os is quite backward compatible. However if a file is missing in the capture (because tha capture is performed on a non-clean system) or in the base os (the 'target' os does no longer contain the file) it is not 'automagically' presented. Nice examples are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you capture on a system with office preinstalled, the virtualised application captured will miss all files already installed by the office installation. So running on a system that also has (the same version) of office installed works fine but on a 'clean' system the applcation could throw 'file not found' errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Same when capturing on an os and running the application on an os that has different base installations (like the dll's given by pbjork in the previous post). If the newer system no longer contains these dll's, you will have to unclude them in the package so the virtualised application still finds them...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another problem could be that files are referenced on the wrong location...&lt;/P&gt;&lt;P&gt;If a virtualised application is captured on a system with windows installed in c:\windows, and runs on a system with c:\winnt, the application might not find this file. ThinApp does detect most of these translations, but sometimes a setting is missed or a application can not handle this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So no, ThinApp is no OS hider or , but it eases deploying applications on different systems. But you still require testing and possibly patching settings. Besides that a lot of other features are available (like sandboxing, updatemanagement, keeping the system clean etc), but this is not question now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Michael Baars&lt;/P&gt;&lt;P&gt;Comprehensive ICT Solutions - Weert (NL)&lt;/P&gt;&lt;P&gt;&lt;EM style=": ; color: #999999; font-size: 8pt; "&gt;(Please remember to mark your question answered if so and reward points to those who helped you...)&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Apr 2011 14:58:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-package-attempting-to-install-when-ran/m-p/1738619#M4737</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-04-20T14:58:13Z</dc:date>
    </item>
  </channel>
</rss>

