Hi,

We have been using AVD for some time now but we have been experiencing some inconsistencies with the way profiles are created and managed on the session hosts.

Originally when a user logged in they  would have the “roaming” profile copied to C:Usersusername and have another temporary folder C:Userslocal_username created. Upon logout the “local_username” folder is removed.

I have another server in the host pool where no “local_username” folder is created, but the C:Usersusername remains. Everything seems to work ok though.

I have introduced a new server into the pool ( due to Teams issues on a previous host ) , built from a MS supplied AVD image. For this server the C:Usersusername folder is created and removed on each login. As a result we have slow logins as the profile is copied back and forth upon every login.

My question is what it the correct behaviour and am I misconfiguring FSLogix somehow for the newly introduced session host ?

​Hi, We have been using AVD for some time now but we have been experiencing some inconsistencies with the way profiles are created and managed on the session hosts.Originally when a user logged in they  would have the “roaming” profile copied to C:Usersusername and have another temporary folder C:Userslocal_username created. Upon logout the “local_username” folder is removed. I have another server in the host pool where no “local_username” folder is created, but the C:Usersusername remains. Everything seems to work ok though. I have introduced a new server into the pool ( due to Teams issues on a previous host ) , built from a MS supplied AVD image. For this server the C:Usersusername folder is created and removed on each login. As a result we have slow logins as the profile is copied back and forth upon every login. My question is what it the correct behaviour and am I misconfiguring FSLogix somehow for the newly introduced session host ?    Read More

​