<?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 2019 - Cannot check for updated license in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831000#M4155</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have a writable and was there an update to it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Sep 2020 20:14:45 GMT</pubDate>
    <dc:creator>domdsouza</dc:creator>
    <dc:date>2020-09-03T20:14:45Z</dc:date>
    <item>
      <title>Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1830998#M4153</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am getting an error when trying to use Visual Studio 2019 community version on our VM/appstacks.&lt;/P&gt;&lt;P&gt;I am able to run VS2019 on our physical machines without having this issue.&amp;nbsp; This is after a fresh install.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/21912i9BC54DA8F0E7C09A/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 10 x64 1909&lt;/P&gt;&lt;P&gt;View agent 7.12 &amp;amp; vcenter 7&lt;/P&gt;&lt;P&gt;Appvol agent 2.18.4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did use the VMware OSOT which disabled NCSI.&amp;nbsp; I re-enabled that and set the reg keys in HKLM\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator back to 0.&amp;nbsp; I thought maybe the issue with Windows thinking it had no internet access was the issue but even with the taskbar icon showing Connect &amp;amp; Internet Access now I still get the same error when trying to update the visual studio license.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can sign in fine and it recognizes my account, but trying to "update license" always results in the same error "We could download a license, check internet connection and proxy settings"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else had this or similar issue?&amp;nbsp; Is there some other network setting I may need to re-enabled that was turned off using the OSOT?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not tried to install it on a fresh plain base image yet but that will be next on the list for tomorrow.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2020 23:02:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1830998#M4153</guid>
      <dc:creator>khamilton2</dc:creator>
      <dc:date>2020-07-27T23:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1830999#M4154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A bit of follow up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I went ahead and installed it on the base Image.&amp;nbsp; It works fine there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also was able to use it without any errors while it was being provisioned on the appprov machine.&amp;nbsp; As in I updated the appstack, while it was provisioning opened VS2019, signed in and grabed the license without issues.&amp;nbsp; However when I captured it again and attached it to a pool it was still giving the original error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That leads me to believe its something related to appvolumes but I am not sure what right now.&amp;nbsp; We previously had VS2017 working on a appvol 2.15 appstack and windows 1803.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Jul 2020 00:54:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1830999#M4154</guid>
      <dc:creator>khamilton2</dc:creator>
      <dc:date>2020-07-28T00:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831000#M4155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have a writable and was there an update to it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2020 20:14:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831000#M4155</guid>
      <dc:creator>domdsouza</dc:creator>
      <dc:date>2020-09-03T20:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831001#M4156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have not been able to get it working but this has got nothing to do with Appvolumes but with how Visual Studio works in general.&lt;/P&gt;&lt;P&gt;Even if you have a free version (which community is) it will create the license based on a hash of the computer name (or so it seems). We have tried community, professional and enterprise and all have the same issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Seems as if Microsoft doesn't want you to use Visual studio in a non persistent environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Sep 2020 06:22:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831001#M4156</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2020-09-04T06:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831002#M4157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So one can use DEdicated Instant clone pools where the pc name remains the same ?... ie not floaters . ?&lt;/P&gt;&lt;P&gt;thx .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Sep 2020 23:14:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831002#M4157</guid>
      <dc:creator>Douglas42Adams</dc:creator>
      <dc:date>2020-09-08T23:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831003#M4158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can regenerate the hash that Ray mentioned by doing the following: &lt;A href="https://docs.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2019" title="https://docs.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2019"&gt;https://docs.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2019&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2019" title="https://docs.microsoft.com/en-us/visualstudio/install/automatically-apply-product-keys-when-deploying-visual-studio?view=vs-2019"&gt;Automatically apply product keys - Visual Studio | Microsoft Docs&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We elevated both the StorePID.exe and DDConfigCA.exe with DEM and run a post-import task. This can probably be replaced with an elevated task in DEM 2006.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can post our script if you need help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Oct 2020 01:05:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831003#M4158</guid>
      <dc:creator>jhol5</dc:creator>
      <dc:date>2020-10-23T01:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831004#M4159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Were you able to get it to work within an Appstack with this reactivation? Or do you still need to install it on the base image?&lt;/P&gt;&lt;P&gt;Because if that is the case for us it is still a no go unfortenately. We do not want Visual Studio within our GI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2020 07:21:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831004#M4159</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2020-10-29T07:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831005#M4160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have it in a AppStack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the script:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="javascript" __jive_macro_name="code" class="_jivemacro_uid_16039789304746047 jive_macro_code jive_text_macro" data-renderedposition="92_8_1232_272" jivemacro_uid="_16039789304746047"&gt;&lt;P&gt;@echo off&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if exist "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\DDConfigCA.exe" (&lt;/P&gt;&lt;P&gt;&amp;gt;%USERPROFILE%\vs2017.txt (&lt;/P&gt;&lt;P&gt;timeout 3 /nobreak &amp;gt;nul&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\DDConfigCA.exe"&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\StorePID.exe" "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" "08860"&lt;/P&gt;&lt;P&gt;echo error level: %errorlevel%&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if exist "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\DDConfigCA.exe" (&lt;/P&gt;&lt;P&gt;&amp;gt;%USERPROFILE%\vs2019.txt (&lt;/P&gt;&lt;P&gt;timeout 3 /nobreak &amp;gt;nul&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\DDConfigCA.exe"&lt;/P&gt;&lt;P&gt;"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\StorePID.exe" "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" "09260"&lt;/P&gt;&lt;P&gt;echo error level: %errorlevel%&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2020 13:42:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831005#M4160</guid>
      <dc:creator>jhol5</dc:creator>
      <dc:date>2020-10-29T13:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831006#M4161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is this path in your install for Visual Studio Community 2019 build?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C:\Users\&amp;lt;userid&amp;gt;\AppData\Local\Microsoft\VisualStudio\16.0_xxxxxxxxx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I may have a fix for this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2020 13:57:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831006#M4161</guid>
      <dc:creator>domdsouza</dc:creator>
      <dc:date>2020-10-29T13:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831007#M4162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just out of curiosity, is this with the Community edition because for as far as I know it does not have a PID key that I can enter. &lt;/P&gt;&lt;P&gt;Or is it like the KMS key that is freely available online?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My guess is that during packaging you should not activate the product, right?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Oct 2020 06:57:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831007#M4162</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2020-10-30T06:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831008#M4163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Oh right, we are deploying enterprise so the lines containing "StorePID.exe" can be left out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Oct 2020 15:52:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/1831008#M4163</guid>
      <dc:creator>jhol5</dc:creator>
      <dc:date>2020-10-30T15:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/2810636#M8234</link>
      <description>&lt;P&gt;Is there anything else beyond running this script and adding those two items to privilege elevation you had to do to get this working?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I added privilege elevation for the two tasks, put the contents of your script in a file and set it to run as a post-import task. &amp;nbsp;The log file is created showing the ddconfigca.exe running and the error level 0 from storepid.exe, but when I launch VS2019 pro it says pre-release software etc. &amp;nbsp;If I run the commands manually from an admin command prompt they work as expect. &amp;nbsp;I'm stumped.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2020 14:27:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/2810636#M8234</guid>
      <dc:creator>pchapman</dc:creator>
      <dc:date>2020-11-18T14:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Studio 2019 - Cannot check for updated license</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/2811223#M8238</link>
      <description>&lt;P&gt;We had the exact same issue that you are seeing. Apparently elevated commands cannot be run post import. What we did is create an elevation for both applications and created a shortcut in the startup menu folder that executed the script, this does work as intended.&lt;/P&gt;&lt;P&gt;Do keep in mind that it could take a while for the appstack to be assigned. I would suggest adding a pause in the script for executing or creating a loop for checking if both files exist.&lt;/P&gt;&lt;P&gt;We are using Visual Studio now as intended.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2020 06:21:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Visual-Studio-2019-Cannot-check-for-updated-license/m-p/2811223#M8238</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2020-11-20T06:21:59Z</dc:date>
    </item>
  </channel>
</rss>

