Don’t forget to update your App Volumes Provisioning VM with the App Volumes Agent. The other and personally my preferred way to get it work is to update the App Volumes environment (Manager, Templates and Agent) to at least version 2.17. Solution 2 for App Volumes 2.17 (and later):
If you want you can also be more specific in the path depth, but pity enough by default all Autodesk products adds a year name in the installation folder, so you need to change your snapvol.cfg after every major release of the Autodesk products. This means that all your AppStacks and/or Writable Volumes must include the two following lines inside the snapvol.cfg:Įxclude_process_path=\Program Files (x86)\AutodeskĮxclude_process_path=\Program Files\Autodesk To fix this behavior you need to edit or copy the AppStacks template by following the procedure ( here), this sample is for a writable volume, but it’s almost the same for the AppStack template. If no AppStacks are mounted (no assignments and attachments), the launch time of DWGTrueView and AutoCAD is the same as a non virtual desktop. If one or more AppStacks are mounted (even if no Autodesk product is in the AppStack), the launch time of DWGTrueView is still +/- 10 minutes. AutoCAD on the other hand is an expensive product, so we will have no choice to flag it as unusable in a virtual desktop when AppStacks and/or Writable Volumes are used with version 2.16. When App Volumes 2.16 (Agent) is used we couldn’t make it work and decided to place DWGTrueView in the Windows 10 golden/base/master image, because it’s free for download and use. Solution 2 for App Volumes 2.16 (and maybe lower?): I’ve tried to implement this solution on my App Volumes 2.16 AppStack template, but it looks like the App Volumes Agent doesn’t process the “reverse_replicate_registry_key” entry in the snapvol.cfg. VMware has a KB-article ( here) for applications which launches or run slow when an AppStack is attached.
0 kommentar(er)
