Solution
在一个4。x与弹性分层ena Unidesk机bled, there are two registry keys that define how it interacts with the file share:
Key: HKLM\SOFTWARE\Unidesk\ULayer
Value: RepositoryPath
Type: REG_SZ
Data: your path of Repository
Key: HKLM\SOFTWARE\Unidesk\ULayer
Value:AssignmentFile
Type: REG_SZ
Data: your path of assignment file
The AssignmentFile is a the JSON file which identifies which app layers belong to which users/groups, and should be set to "ElasticLayerAssignments.json". The RepositoryPath is the file share where both thelayers and the JSON file can be found, for instance "\\myserver.domain.com\share1\Folder". If a customer wants to use some kind of distributed file share, and point machines to a different share at boot time, they absolutely can, just by editing the RepositoryPath. (While editing AssignmentFile is also permitted, it's not nearly as clear why you would. So don't.)
See the attached "ADM" file for a GPO that can help with this. You would put the GPO in an OU in which all the machines booting from this published image would be placed. The GPO is applied at machine boot time, and would be ready before a user tried to login. We only look at the share when a user tries to login.
Note, if you want to use different shares for your User Layer disks, that feature is in the Management Console itself (as of App Layering 4.3) where you specify User Layer shares based on AD groups. This only affects User Layers, and does not affect Elastic Layers.
Key: HKLM\SOFTWARE\Unidesk\ULayer
Value: RepositoryPath
Type: REG_SZ
Data: your path of Repository
Key: HKLM\SOFTWARE\Unidesk\ULayer
Value:AssignmentFile
Type: REG_SZ
Data: your path of assignment file
The AssignmentFile is a the JSON file which identifies which app layers belong to which users/groups, and should be set to "ElasticLayerAssignments.json". The RepositoryPath is the file share where both thelayers and the JSON file can be found, for instance "\\myserver.domain.com\share1\Folder". If a customer wants to use some kind of distributed file share, and point machines to a different share at boot time, they absolutely can, just by editing the RepositoryPath. (While editing AssignmentFile is also permitted, it's not nearly as clear why you would. So don't.)
See the attached "ADM" file for a GPO that can help with this. You would put the GPO in an OU in which all the machines booting from this published image would be placed. The GPO is applied at machine boot time, and would be ready before a user tried to login. We only look at the share when a user tries to login.
Note, if you want to use different shares for your User Layer disks, that feature is in the Management Console itself (as of App Layering 4.3) where you specify User Layer shares based on AD groups. This only affects User Layers, and does not affect Elastic Layers.
Additional Resources
//m.giftsix.com/blogs/2017/09/19/citrix-app-layering-tips-and-tricks/