Hello,
Each host pool has a different fslogix share. But the share path is mandatory in the fslogix path.
This makes the fslogix profile unusable.
Expected behavior.
Fslogix profile for production environment: fslogix version set, fslogix registry - set, etc
Fslogix profile for test environment: fslogix version set, fslogix registry - set, etc
Each host pool has a unique fslogix share, so having it in the fslogix profile makes no sense.
When I decide to change the fslogix version or registry setting in the test environment, it should be possible with one profile update.
Now I need to go through every host pool configuration.
fslogix profile - exclude storage path
2
Hi Marek Sokół - thanks for this suggestion. I agree, this seems like something we should provide more flexibility for. For 6.5, we are introducing the ability to override certain aspects of an Auto Scale profile, I think we could in future introduce the ability to override the share on a per host pool basis. I also think it may be worth allowing FSlogix profiles to be cloned, as we do with Auto Scale profiles. Thanks again!
Hi Toby Skerritt - thank you for implementing that in v7.
Also like the when use override, nerdio remembers previous individual setting for share (so not need to set it from scratch).
We are using override for each host pool, because of that we can not use massive profile assignment for fslogix:
Thanks Marek Sokół ! I'm glad its working for you. If you have any questions or concerns please let me know and I will ask on of our AVD PM to respond. Thanks!
Toby Skerritt the next level would be to apply fslogix profile at scaly (by this wizard from previous msg), and to keep individual share path for each host pool. So missing option named “keep current share setting from host pool as override”
HI Marek Sokół, we will investigate adding an option to the Add profile assignments wizard to keep the custom/override share path.
Please sign in to leave a comment.
Comments (5 comments)