R
rhildebrand18
Guest
Hello Support,
When attempting to package Visual Studio 2017 within AppVolumes for deployment on VMware VDI systems, the license key entered during the packaging does not appear to be saving. After the installation completes, a volume license key may be entered into the application and the application reports that the license is good. This a verified after restarting the application as well as restarting the VM itself. However, after the AppStack is finalized and provisioned to a user, the application comes up with an expired trial license and there is no option to enter a product key to activate the product.
Where is the volume license key, when entered during installation, being stored? Can it be captured as part of the AppStack?
Is there a method that the user can utilize to enter a license key within their own profile that will remain good and persist between sessions?
Thanks,
Robert
Continue reading...
When attempting to package Visual Studio 2017 within AppVolumes for deployment on VMware VDI systems, the license key entered during the packaging does not appear to be saving. After the installation completes, a volume license key may be entered into the application and the application reports that the license is good. This a verified after restarting the application as well as restarting the VM itself. However, after the AppStack is finalized and provisioned to a user, the application comes up with an expired trial license and there is no option to enter a product key to activate the product.
Where is the volume license key, when entered during installation, being stored? Can it be captured as part of the AppStack?
Is there a method that the user can utilize to enter a license key within their own profile that will remain good and persist between sessions?
Thanks,
Robert
Continue reading...