VMware Horizon Community
Carlos009
Contributor
Contributor

Hello, I am experiencing an issue with the <username>.<domain>.v2 folder creating a duplicate appdata folder inside a hidden folder {string of characters}.

Recently we were experiencing high log on times and frequent renaming/deleting of user's View Persona related folders. I have seen a users Persona folder create duplicate AppData folders. It would creat it insode the VIew Persona folder where the original AppData is located. It would create it in a hidden folder with a name like {string of characters}, for example. Weare on version 5.3.0 of View. Has anyone experienced something similar?

Reply
0 Kudos
3 Replies
Gaurav_Baghla
VMware Employee
VMware Employee

Hello Carlos,

Could you please check if Client Side Caching is Enabled or Disabled.

Use this Article below

http://kb.vmware.com/kb/2016416

Regards Gaurav Baghla Opinions are my own and not the views of my employer. https://twitter.com/garry_14
Reply
0 Kudos
Carlos009
Contributor
Contributor

Thanks for the reply.

I had already configured that setting on the initial gold/parent image creation.

another thing that is occurring, the same folder name with the string {d24f2895-651a-40cc-8e5c-c037b9994104} is being created on all users with the duplicate appdata folder.

Does this sound familiar?

Reply
0 Kudos
ErikTatum10
VMware Employee
VMware Employee

Hi Carlos,

The {d24f2895-651a-40cc-8e5c-c037b9994104} folder is a temporary folder that is created during each replication cycle.  It's used to cache the changes that are being replicated to the central profile store.  Replication is done is two phases, upload and commit.  Once all the changes are uploaded to the {d24f2895-651a-40cc-8e5c-c037b9994104} folder the upload phase is complete and the changes are then committed to the profile.  Once the commit phase is complete the {d24f2895-651a-40cc-8e5c-c037b9994104} folder and its contents are deleted.

Sometimes certain failures can result in the {d24f2895-651a-40cc-8e5c-c037b9994104} folder sticking around after the replication cycle has ended.  The purpose of this folder and how it's managed is to ensure your profile remains in a crash-consistent state, which means your data does not become corrupt or lost due to a replication failure.

So, given that background, does this answer your question or you do feel like you are experiencing some sort of replication failure and the {d24f2895-651a-40cc-8e5c-c037b9994104} folder is staying beyond the replication cycle?

Thanks,

Erik

Reply
0 Kudos