This message was deleted.
# microsoft-fslogix
s
This message was deleted.
h
btw we are going to be doing a poc of Liquidware Profile Unity which should solve this in the future, but Im looking for anything we can do now without it.
👍 1
j
Just change the name of the container? Sid will be the same so permissions should be fine?
h
I haven't tried that yet TBH, but I was under the presumption that this wouldn't work well because of things in the registry that are referencing the old username vs. using %username%. I will give it a go to see if it does okay or not.
So I tried this and it worked with some caveats and coaxing. First oddity is the the c:\users\ username folder still reflects the old username, but the profile is in use none the less. Second is that we use WEM to apply folder redirection stuff and (beyond), and so I had to clear the WEM settings cache stuff from the registry to get all settings to be re-applied to correct for the new username. (as per https://support.citrix.com/article/CTX219086/some-upm-or-wem-agent-parameters-may-not-[…]m-gpo-settings-to-workspace-environment-management-settings)
I still plan to test this further as my first victim didn't have much in the way of user customization such as start menu tiles and the like. I want to see if anything is still broken.
I do feel like this leaves behind some administrative burden in terms of leaving the profile path folder name mismatched from the username.
j
I guess there was some logic in FSLogix using SID in their path names 🙂
👍 1
h
yeah
but using username makes it so much easier to support
j
100% agreed