<?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: Visual Studio 2017 in App Volumes - Capture Licensing? in Dynamic Environment Manager</title>
    <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/2810678#M6446</link>
    <description>&lt;P&gt;Sadly adding those lines to the startup.bat doesn't seem to work for my VS 2019 Pro. &amp;nbsp;The strange thing is, if I right click the file and run as administrator after logging into the VM, it does license it successfully..&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Nov 2020 16:27:16 GMT</pubDate>
    <dc:creator>pchapman</dc:creator>
    <dc:date>2020-11-18T16:27:16Z</dc:date>
    <item>
      <title>Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831946#M3762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;App Volumes 2.18, Horizon 7.10, Win10 x64 1803, using Instant Clones. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to get an App Vol of Visual Studio 2017 installed and the only issue I have is with licensing. The guide states that after the AppVol is built, the user should be able to launch the app and insert the serial; however, 'unlock with serial' is never given as an option to the user. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I created a batch file that uses PID.exe to insert the right license, but it resets with every session since we use Instant Clones. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know where that Reg Key is stored so that I can set a UEM/DEM capture for it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2020 17:51:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831946#M3762</guid>
      <dc:creator>VirtuallyANewb</dc:creator>
      <dc:date>2020-06-17T17:51:48Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831947#M3763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a Visual Studio config file available from the community --&amp;gt; &lt;A href="https://communities.vmware.com/docs/DOC-36381"&gt;Microsoft Visual Studio.zip&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure if this matches your VS version, but you can try it out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise, you can use tools like RegShot (&lt;A href="https://sourceforge.net/projects/regshot/" title="https://sourceforge.net/projects/regshot/"&gt;https://sourceforge.net/projects/regshot/&lt;/A&gt;) or ProcMon (&lt;A href="https://docs.microsoft.com/en-us/sysinternals/downloads/procmon" title="https://docs.microsoft.com/en-us/sysinternals/downloads/procmon"&gt;https://docs.microsoft.com/en-us/sysinternals/downloads/procmon&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RegShot does a before/after comparison, which is easy to use.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2020 15:26:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831947#M3763</guid>
      <dc:creator>ijdemes</dc:creator>
      <dc:date>2020-06-18T15:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831948#M3764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've found this document which states the only supported scenarios for deploying VS with App Volumes is to use writables (yuck!)&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2149369" title="https://kb.vmware.com/s/article/2149369"&gt;VMware Knowledge Base&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm working on this myself for 2019.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I first tried this method:&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/565635"&gt;Visual Studio 2015 in standard appstack&lt;/A&gt;&amp;nbsp; however these commands resulted in unlicensed visual studio (not sure why...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And then I tried just capturing without using those commands, and somehow it's magically licensed at every login.&amp;nbsp; I need to talk to the person who built the offline installer to see if they somehow baked the license key into the installer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck, I'll update if I figure out what's goin on in my environment. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2020 17:30:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831948#M3764</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-06-18T17:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831949#M3765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;pchapman's link to the other forum post worked for me. I was able to embed the following commands into the startup.bat for that AppVolume's MountPoint:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\DDConfigCA.exe"&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\StorePID.exe" [product key including the dashes] [MPC]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2020 21:11:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/1831949#M3765</guid>
      <dc:creator>VirtuallyANewb</dc:creator>
      <dc:date>2020-06-18T21:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2017 in App Volumes - Capture Licensing?</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/2810678#M6446</link>
      <description>&lt;P&gt;Sadly adding those lines to the startup.bat doesn't seem to work for my VS 2019 Pro. &amp;nbsp;The strange thing is, if I right click the file and run as administrator after logging into the VM, it does license it successfully..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 16:27:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/Visual-Studio-2017-in-App-Volumes-Capture-Licensing/m-p/2810678#M6446</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-11-18T16:27:16Z</dc:date>
    </item>
  </channel>
</rss>

