VMware Horizon Community
DavidCraypo
Contributor
Contributor

AppVol 2.12 win10 LTSB 2016 writeable volume attaches but most of the user data is missing after a period of time

-Appvol 2.12 running on sever 2012 r2 data center

-connected to separate SQL 2012 SP2 database

-linked clones, refresh on log out

-horizon 7.0.3

-all brand new installs, nothing upgraded

-Windows 10 2016 LTSB

-Using the default template provided by appvolumes for writable storage (user installed programs and profile data)

SO this is what we are seeing

The user's writable volumes attaches properly and stores their data as expected.  Randomly, whether it is 3 days later or a month later after the initial creation of the user's writable, the writable volume will show as attached on the VM and in the appvol manager portal BUT the user is missing all of their saved data (favorites, onenote pins etc...)  Sometimes a reboot will fix the issue but eventually after each log in the data will be missing their information and we have to delete their writable and build again.  We've gotten to the point where everyday we are rebuilding another user's writable volumes.  Needless to say it is getting frustrating.

Has anyone else seen this?  We have a ticket open with support but they said they have never seen this issue before so I am curious if anyone else has seen this OR if things have been working well for you.

Thanks!

Reply
0 Kudos
2 Replies
Ray_handels
Virtuoso
Virtuoso

Yes we did see this issue, the exact same issue you are referring to but this was with version 2.11 of appvolumes.

What happened there is that after 4 to 5 logons the writable would simply break.

We are using 2.12 with W10 Anniversary update although not the LTSB version but the "normal"  version stripped with OS Optimization tool. Afetr upgrading to 2.12 and recreating the writables that were broken (still in test fase) we didn't see this issue reoccur. We had users logging in for more than 50 times and they still had their settings intact.

Looking at your configuration it seems to be allright with linked cloan floating and refresh after use. Did you test it with the "normal" version?

And when you attach the writable to a machine that doesn't have appvolumes installed can you see the entire profile directory inthere? Or only parts of it?

Reply
0 Kudos
DavidCraypo
Contributor
Contributor

Initially we were on 2.11 for testing with win10 standard.  When 2.12 came out we did a brand new install and used win10 2016 LTSB instead since it is a "stripped down" version of windows.

Once attached we can see the contents but using the WinDirStat application PLUS we can see that the writable is much larger than recorded in the appvolume manager.  Some writables show up as big as 40 gigs.  Working with VMware support it's like the temp directory is replicating itself over and over.  I have been told this issue has never seen before and engineering is looking into it.

Reply
0 Kudos