<?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: Program install fails during provisioning in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426376#M5815</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Windows 10 1809 build is not a supported client OS with 2.14 release. As per the install guide, 1803 is supported. &lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-App-Volumes/2.14/App-Volumes-Install-Guide-2-14.pdf" title="https://docs.vmware.com/en/VMware-App-Volumes/2.14/App-Volumes-Install-Guide-2-14.pdf"&gt;https://docs.vmware.com/en/VMware-App-Volumes/2.14/App-Volumes-Install-Guide-2-14.pdf&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Jan 2019 07:49:25 GMT</pubDate>
    <dc:creator>Lakshman</dc:creator>
    <dc:date>2019-01-04T07:49:25Z</dc:date>
    <item>
      <title>Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426374#M5813</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;running VMware AppVolumes v2.14.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a vm of Windows 10 (v1809)&amp;nbsp; that is nice and clean, except I have the AppVol agent on it as this machine is used for provisioning.&lt;/P&gt;&lt;P&gt;There is an application (bartender 9.3) that I need to create an app stack for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i start to the provisioning on the app vol machine, and on the Win10 machine, when the little appvol box pops up, I start the install for Bartender.&lt;/P&gt;&lt;P&gt;Install goes without issue.&amp;nbsp; It fails upon starting the program with a 'side-by-side' error.&lt;/P&gt;&lt;P&gt;yet if I revert to the clean snapshot (appvol agent is still installed but I did not start provisoning) teh program installs and runs just fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 18:01:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426374#M5813</guid>
      <dc:creator>JohnFLi</dc:creator>
      <dc:date>2019-01-03T18:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426375#M5814</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, I tried installing Bartender during the provisioning process and completed it as normal.&lt;/P&gt;&lt;P&gt;Assigned teh app stack.&amp;nbsp;&amp;nbsp;&amp;nbsp; THe user that it was assigned to gets teh same error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Activation context generation failed for "C:\Program Files (x86)\Seagull\BarTender Suite\bartend.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762" could not be found.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2019 19:04:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426375#M5814</guid>
      <dc:creator>JohnFLi</dc:creator>
      <dc:date>2019-01-03T19:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426376#M5815</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Windows 10 1809 build is not a supported client OS with 2.14 release. As per the install guide, 1803 is supported. &lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-App-Volumes/2.14/App-Volumes-Install-Guide-2-14.pdf" title="https://docs.vmware.com/en/VMware-App-Volumes/2.14/App-Volumes-Install-Guide-2-14.pdf"&gt;https://docs.vmware.com/en/VMware-App-Volumes/2.14/App-Volumes-Install-Guide-2-14.pdf&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2019 07:49:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426376#M5815</guid>
      <dc:creator>Lakshman</dc:creator>
      <dc:date>2019-01-04T07:49:25Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426377#M5816</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Besides the fact that it is unsupported I would try and install all VC Redist versions (and at lest the one you are using now) on the golden image.&lt;/P&gt;&lt;P&gt;Also, when creating a packaging machine I would suggest cloning the golden image and removing unnecessary software and agents (Horizon VIew agent and UEM agent being one of those) and package using that machine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even though it is unsupported I think it should still work. This is just a VC Redist issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jan 2019 08:26:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426377#M5816</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2019-01-04T08:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426378#M5817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, spent the day creating a Win10 1803 install.&lt;/P&gt;&lt;P&gt;Much to my surprise, that after installing, it ran without issue with appVol running.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So i then applied the app Stack to a system, and it looked like all was good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Issue now is, when clicking on it to run.....noting happens.&lt;/P&gt;&lt;P&gt;so i tried running it as admin.....&lt;/P&gt;&lt;P&gt;it gives me a window saying "This app has been blocked by your system administrator"&lt;/P&gt;&lt;P&gt;Which is not the case.&amp;nbsp; There isn't any GPO that blocks this application.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 Jan 2019 00:05:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426378#M5817</guid>
      <dc:creator>JohnFLi</dc:creator>
      <dc:date>2019-01-05T00:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426379#M5818</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could you please post a printscreen of the shortcut properties? Could it be that it points to a location where files cannot be stored within the appstack (%APPDATA% for example) or maybe a smart shortcut (or whatever it is called) in which it only point to the application name and not the actual executable?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jan 2019 08:48:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426379#M5818</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2019-01-07T08:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426380#M5819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the shortcut that it creates when clicking on the 'start' button points to c:\programdata\microsoft\windows\start menu\programs\bartender9.3&amp;nbsp;&amp;nbsp;&amp;nbsp; which i think is what you meant by a 'smart shortcut'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the actual exe itself is in c:\program files (x86)\seagull\bartender suite. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no matter which way i try it, it ignores me....(what am I married to this?&amp;nbsp;&amp;nbsp; lol)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what I did today was to create a new pool of machines (1803) and did NOT do the &lt;A href="https://labs.vmware.com/flings/vmware-os-optimization-tool" title="https://labs.vmware.com/flings/vmware-os-optimization-tool"&gt;VMware OS Optimization Tool&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and now the app starts just fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jan 2019 23:08:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426380#M5819</guid>
      <dc:creator>JohnFLi</dc:creator>
      <dc:date>2019-01-07T23:08:43Z</dc:date>
    </item>
    <item>
      <title>Re: Program install fails during provisioning</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426381#M5820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My guess is that it is not the application that fails but mostly my guess is that there is an issue with a service being disabled by OSOT or a task being removed.&lt;/P&gt;&lt;P&gt;If it does work without running OSOT I would suggest looking into OSOT and seeing which services are being disabled and when the application stops working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking the the vcredist it might well be the Windows Modules Instaler service that needs to be enabled (just wild guessing here though) but that's worth a shot.&lt;/P&gt;&lt;P&gt;I would not suggest going into production without at least having 70 to 80% of settings suggested by OSOT implemented. Windows 10 is quite "memory hungry" in comparison to W7...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2019 10:21:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Program-install-fails-during-provisioning/m-p/1426381#M5820</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2019-01-08T10:21:31Z</dc:date>
    </item>
  </channel>
</rss>

