VMware Horizon Community
EricNichols
Hot Shot
Hot Shot
Jump to solution

View 5.2 Persona Management "Files and folders excluded from roaming" wildcards and special characters

We want to exclude AppData\Roaming\test_*.doc or AppData\Roaming\Macromedia\Flash Player\#SharedObjects from the persona and we have added these to the list of exclusions but they keep ending back up in the repository. Other exclusions are working as expected. What should we expect?

If wildcards work, it would also be nice to be able to exclude AppData\Roaming\Mozilla\Firefox\Profiles\*\minidumps

1 Solution

Accepted Solutions
ErikTatum10
VMware Employee
VMware Employee
Jump to solution

Hi Eric,

Persona does not currently support the use of wildcards in any of the configuration options.  So, "AppData\Roaming\test_*.doc" and "AppData\Roaming\Mozilla\Firefox\Profiles\*\minidumps" will not work.  However, I tested "AppData\Roaming\Macromedia\Flash Player\#SharedObjects" myself with 5.2 and it works fine.  Please note that "Files and folders excluded from roaming" will not remove any existing files from the remote folder.  It simply prevents the files in the remote folder from being created in the local folder during logon and it prevents any changes in the local folder from replicating to the remote folder.  This allows you to disable the setting and go back to the original data if you need to.

Please let me know if you have any further questions.

Thanks,

Erik

View solution in original post

Reply
0 Kudos
3 Replies
ErikTatum10
VMware Employee
VMware Employee
Jump to solution

Hi Eric,

Persona does not currently support the use of wildcards in any of the configuration options.  So, "AppData\Roaming\test_*.doc" and "AppData\Roaming\Mozilla\Firefox\Profiles\*\minidumps" will not work.  However, I tested "AppData\Roaming\Macromedia\Flash Player\#SharedObjects" myself with 5.2 and it works fine.  Please note that "Files and folders excluded from roaming" will not remove any existing files from the remote folder.  It simply prevents the files in the remote folder from being created in the local folder during logon and it prevents any changes in the local folder from replicating to the remote folder.  This allows you to disable the setting and go back to the original data if you need to.

Please let me know if you have any further questions.

Thanks,

Erik

Reply
0 Kudos
EricNichols
Hot Shot
Hot Shot
Jump to solution

We were able to finally get the #SharedObjects folders to go away but only after gpupdating the golden image and recomposing the pool. It looks like the Persona GPO only gets applied 100% of the time during compose/recompose and that changes to the Persona GPO namely exclusions after that are not inherited reliably? This is evidenced by what we read about what exceptions/exclusions were applied in vmwvvp.txt.

Reply
0 Kudos
ErikTatum10
VMware Employee
VMware Employee
Jump to solution

There shouldn't be anything specific about our policy that would cause this behavior.

Reply
0 Kudos