fdrietatns's Posts

Is it the same behavior for all 2.13.3 appstacks or just one in particular? Is your capture machine the same windows version (1703)? Is there anti virus running on the capture machine? Is the view agent on the capture machine?

Start Menu is finicky these days. I've reviewed a bunch of articles and this is what is working for me on 2.13.3 Win10 1709. Currently having an issue with startmenulayout customization but the menu works VMware Knowledge Base VMware Knowledge Base Correct Answerby GTCyberMike on Jul 24, 2017 10:34 AM TechGuy129 is our hero!!!!!  Thank you for the speedy suggestions! Unfortunately, re-registering the Microsoft.Windows.ShellExperienceHost and Microsoft.Windows.Cortana appX packages did NOT fix the problem for us.  However, adding your exclusion to the snapvol.cfg did.  After your suggestion, we spoke to the VMware tech support rep who worked with VMware engineers originally on this issue (months ago) and he recommended appending exclusions 2 - 4 (below) as well.  Apparently those additional ones (2 - 4) helped to eradicate this same issue months ago but had no positive impact for us now.  It seems that as Microsoft continues to make changes to their OS (e.g. deprecating the TileLayerDatabase) we anticipate needing to append new registry or path locations in the future. exclude_path=\ProgramData\Microsoft\Windows\AppRepository exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppReadiness exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel P.S.  To test the above, login to your VM, browse to the following path, append the above, then log-out-log-in - viola!  If this works, then you will need to apply this to everyone's write disks by uploading this change as a zip file into everyone's writable volume to correct this after they all log out/in. C:\SnapVolumesTemp\MountPoints\.....snapvol.cfg

It's undocumented. I disabled it entirely because it seemed to have slowed everything down. There's a thread around here somewhere about hook injection white list and Chrome. The issue you described about Firefox is reminiscent of the issue I had with Chrome on 2.13.1. Obviously I have no idea about your platform so take it for what it's worth.

The issue described in this discussion is not a showstopper by any means. It only impacts the persona management portion of AppVolumes and to that end it is not a critical impact. I've been running this in production space since for a year and a half and have had zero significant issues. It's not perfect but it's pretty close and is stellar at what it does. This has been the best product I've worked with for both application layering and persona management. It couldn't be any simpler to stand up and deploy. The product documentation is only 62 pages; you really only need about half that. I would recommend that you tear down whatever you have and deploy a fresh 2.12.0 build. 2.12.0 has been our best experience.

The work around is to use an older agent version. I went  to 2.12.1 and then had issues with zone identifier data. I had to go back to 2.12.0 which is our last stable version. All is well so far on 2.12.0 agent and 2.13.1 Console. I'm probably just going to go back to 2.12.0 since all of the compelling reasons to use 2.13 (write volume protection, enhanced office virtualization,)  in the first place don't seem to actually work. maintenance release 2.13.3 will fix the sym link issues and recycle bin issues with 2.13.1 and .2 but not ETA is given. Maybe end of Q1.

Thanks. Unfortunately 2.13 introduces other issues related to writables so I had to roll back our agent to 2.12.1 until 2.13.3 comes out. damned if you do; damned if you don't. Appreciate the heads up though. I also took the 1709 update so I'm just going through the motions now so i know how to test to make sure the things are fixed when they say they're supposed to be fixed.

Please see if this corrects the specific issue with drive redirection: VMware Knowledge Base I've used this to enable provisioning of windows 10 1709 on view agent version 6.2.1 which doesn't work otherwise.

Yes, see AV 2.13.1: Can no longer see C:\SnapVolumesTemp after updating to 2.13.1 I have to roll the agent back to 2.12.1 in order to correct this issue and various other issues this condition creates. Thanks..

Whats the impact of running agent version 2.12.1 with console version 2.13.1? I'm in testing with it now, seems fine. Issues are gone but may not have full breadth on what the impact would be at scale. Any insight would be appreciated. Thanks.