<?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>topic Re: ThinApp Isolation mode question in ThinApp</title>
    <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747894#M1006</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same Issue here, I tried with Citrix and ThinApp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any solution already, I am playing now around for 2 days.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Jan 2011 12:57:53 GMT</pubDate>
    <dc:creator>kuchi1980</dc:creator>
    <dc:date>2011-01-20T12:57:53Z</dc:date>
    <item>
      <title>ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747881#M993</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 am new to ThinApp and i have tried to virutalise Skype. The capture process is OK. A have set e default isolation mode to WriteCopy.&lt;/P&gt;&lt;P&gt;When I receive a file via Skype and I try to save it on C:\Temp, the file I saved in my sandbox, which is a normal behaviour, but when I try to save it in the&lt;/P&gt;&lt;P&gt;Root of the C drive C:\, the file is saved to the physical drive. Is it a normal behaviour and if yes, how can I prevent saveing files in the root of the virtual drive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jun 2010 14:45:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747881#M993</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-16T14:45:47Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747882#M994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you could change the isolation= to "Full" and it shouldn't allow interaction with the local file system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jun 2010 15:11:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747882#M994</guid>
      <dc:creator>mark_larson</dc:creator>
      <dc:date>2010-06-16T15:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747883#M995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is the same thing. The only difference is that i can`t see any files or folders.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jun 2010 15:13:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747883#M995</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-16T15:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747884#M996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not normal behavior. If the isolation mode of the c:\ directory is set to WriteCopy, you shouldn't be able to save any files there, they should end up in the sandbox. If your project contains a %drive_C%\##Attributes.ini make sure it specifies WriteCopy in there, if the ##Attributes.ini file isn't present check the default isolation mode in Package.ini. If it is set to WriteCopy you should open a support request so this can be investigated more thoroughly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jun 2010 20:00:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747884#M996</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2010-06-16T20:00:07Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747885#M997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So when i ThinApp Skype, i set WriteCopy isolation mode for the entire capture. Then before the build process in the build directory there is no %dirve_c%. I  manually create the virtual drive with NO ##Attributes.ini. Normally it will inherit the isolation mode from the package.ini file which is set to WriteCopy. It doesn`t work. Then i am creating a ##Attributes.ini with DirectoryIsoloationMode=WriteCopy, and rebuilding the project. Stil the sam thing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 06:47:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747885#M997</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-17T06:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747886#M998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, I'd suggest filing a &lt;A href="http://www.vmware.com/go/service-request"&gt;Support Request&lt;/A&gt; then.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 09:18:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747886#M998</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2010-06-17T09:18:25Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747887#M999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, before making SR, i will change my capture OS. Actually i am using WIN2K3, now i will try with an XP machine just to be sure it is not an OS problem. Do i have to install windows updates, or just a clean installation without any upadtes or SPs ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 09:22:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747887#M999</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-17T09:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747888#M1000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'd at least install SP3, but updating with all the fixes shouldn't be necessary.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 09:30:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747888#M1000</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2010-06-17T09:30:03Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747889#M1001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same thing when i capture skype on XP SP3 virtual machine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 11:27:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747889#M1001</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-17T11:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747890#M1002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Merged - see real and write to real&lt;/P&gt;&lt;P&gt;WriteCopy - see real but write to virtual&lt;/P&gt;&lt;P&gt;Full - see virtual and write to virtual&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you need Merged either as global setting or for some folders.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 12:17:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747890#M1002</guid>
      <dc:creator>NickOn</dc:creator>
      <dc:date>2010-06-17T12:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747891#M1003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well  i don`t want to write the the physical system. That is why i am using WriteCopy DirectoryIsioaltionMode, but it is not working as expected. As i have said before when i make a modification to C:\TEMP\file.txt, the changes are saved in the sandbox, but when i make a change on the C:\ (the root of the directory) the change is saved on the physical system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 13:53:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747891#M1003</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-17T13:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747892#M1004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try to put ##Attributes.ini file in drive folder (in the project)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 14:57:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747892#M1004</guid>
      <dc:creator>NickOn</dc:creator>
      <dc:date>2010-06-17T14:57:40Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747893#M1005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes. I am manually creating the virtual drive folder (%drive_c%), and i put in there the ##Attributes.ini file with DirectoryIsolationMode set to WriteCopy or Full. But there is now difference. I am able to write to the root of the directory and the changes are not saved in my sandbox but on the physical drive. If i create a new folder and a file in that folder, the folder and the file are saved in my sandbox. A just can understand this behaviour. It is like that for the root of the C:\ Drive the DirecotryIsolationMode is set to Merged, and for the other directories it is set to WriteCopy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jun 2010 06:34:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747893#M1005</guid>
      <dc:creator>Mishu</dc:creator>
      <dc:date>2010-06-18T06:34:20Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747894#M1006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same Issue here, I tried with Citrix and ThinApp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any solution already, I am playing now around for 2 days.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Jan 2011 12:57:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747894#M1006</guid>
      <dc:creator>kuchi1980</dc:creator>
      <dc:date>2011-01-20T12:57:53Z</dc:date>
    </item>
    <item>
      <title>Re: ThinApp Isolation mode question</title>
      <link>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747895#M1007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The same thing occurs with &lt;STRONG&gt;any&lt;/STRONG&gt; virtualized application, at least on WinXP SP2. As soon as you use the Open or File Save As... and maybe other &lt;STRONG&gt;common dialogs&lt;/STRONG&gt;, you have&lt;STRONG&gt; inconsistent write access to C:\ whatever specified directory isolation modes are&lt;/STRONG&gt;. Isolation modes for subfolders seems to be handled correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;To reproduce this inconsistent behavior:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- launch a virtualized app and open its File open or File save as... dialog box&lt;/P&gt;&lt;P&gt;- from there, go to C:\ and right click to create a new text file, don't change its name for now. Leave the dialog box open. (1)&lt;/P&gt;&lt;P&gt;- right click to create another text file, name it test1.txt. Leave the dialog box open. (2)&lt;/P&gt;&lt;P&gt;- On the virtual system, you have both files&lt;/P&gt;&lt;P&gt;- On the physical system, you have only test1.txt&lt;/P&gt;&lt;P&gt;- From the dialog box, delete test1.txt and try to rename the first text document to test1.txt&lt;/P&gt;&lt;P&gt;- Ooops, you can't&lt;/P&gt;&lt;P&gt;- Now, on the virtual system, you see only the first text document (3)&lt;/P&gt;&lt;P&gt;- On the physical system, you have only test1.txt (is has not been deleted!)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, the isolation mode for C:\ in this "Common dialog" case is just something oscillating between WriteCopy (1), Merged (2) and not-really-Full (3)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Sorry to say that, but it looks like it's definitely a bug&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jan 2011 00:06:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/ThinApp-Isolation-mode-question/m-p/747895#M1007</guid>
      <dc:creator>JohnVirtual2011</dc:creator>
      <dc:date>2011-01-21T00:06:41Z</dc:date>
    </item>
  </channel>
</rss>

