I've been trying to configure the User Layer Repair Utility to work with our environment. I was having issues where the script was able to obtain the OS layer, app layers, and user information, but It wasn't able to find the user layer sizes. We utilize Nutanix Files as the file share for App Layering, and unfortunately it doesn't support having files directly in the root directory of the share. Due to the location of the JSON files, it means we need to have our App Layering information three layers deep: \\server\folder1\AppLayeringFolder.
It doesn't seem as though the Utility accounts for this scenario. Looking at the GetUserLayers.ps1 script, Line 67 and Line 71 identify certain folders by their depth from the start of the path. I tried increasing these by 1, but still ran into issues and I imagine it's still related. When I select which user layers to find the size for, the script runs and chooses different user layers than the one I selected, and I'm not exactly sure of the reason for this.
Is there any chance of having the utility updated to meet the needs of this use case, or are we out of luck?
Question
Jordan Barnartt
Hello,
I've been trying to configure the User Layer Repair Utility to work with our environment. I was having issues where the script was able to obtain the OS layer, app layers, and user information, but It wasn't able to find the user layer sizes. We utilize Nutanix Files as the file share for App Layering, and unfortunately it doesn't support having files directly in the root directory of the share. Due to the location of the JSON files, it means we need to have our App Layering information three layers deep: \\server\folder1\AppLayeringFolder.
It doesn't seem as though the Utility accounts for this scenario. Looking at the GetUserLayers.ps1 script, Line 67 and Line 71 identify certain folders by their depth from the start of the path. I tried increasing these by 1, but still ran into issues and I imagine it's still related. When I select which user layers to find the size for, the script runs and chooses different user layers than the one I selected, and I'm not exactly sure of the reason for this.
Is there any chance of having the utility updated to meet the needs of this use case, or are we out of luck?
Thank you,
Jordan
Link to comment
10 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now