FSLogix and Azure File Sync - Container Renaming Observation

%3CLINGO-SUB%20id%3D%22lingo-sub-1884400%22%20slang%3D%22en-US%22%3EFSLogix%20and%20Azure%20File%20Sync%20-%20Container%20Renaming%20Observation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1884400%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20planning%20to%20switch%20from%20a%20Windows%20IaaS%20File%20Server%20to%20using%20an%20Azure%20File%20Share%20on%20a%20Premium%20Storage%20account%2C%20we%20decided%20to%20use%20Azure%20File%20Sync%20to%20get%20all%208TB%20of%20the%20profile%20containers%20onto%20the%20new%20share%20in%20advance%20of%20a%20planned%20cutover.%3C%2FP%3E%3CP%3EFor%20the%20most%20part%20this%20has%20worked%20out%20great.%26nbsp%3B%20But%20for%20some%20profiles%2C%20I've%20observed%20what%20looks%20like%20a%20probable%20AFS%20initiated%20renaming%20scenario%20where%20either%20the%20cloud%20endpoint%20(as%20the%20name%26nbsp%3B%20%22Cloud%22)%20or%20the%20server%20endpoint's%20name%20is%20added%20as%20a%20suffix%20to%20the%20profile%20container%20name.%26nbsp%3B%20The%20end%20result%20is%20two%20different%20containers%20in%20a%20given%20users%20profile%20directory.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EExample%3A%3CBR%20%2F%3EUser%20Name%20%3D%20Joe.Cool%3CBR%20%2F%3EAFS%20Cloud%20Endpoint%20%3D%20Cloud%3CBR%20%2F%3EAFS%20Server%20Endpoint%20%3D%20Server1%3CBR%20%2F%3E%3CBR%20%2F%3EPrior%20to%20using%20AFS%2C%20each%20users%20profile%20container%20is%20simply%20named%20as%20%22Profile_Joe.Cool.VHDX%22%20given%20the%20above%20scenario.%3CBR%20%2F%3EHowever%2C%20for%20some%20users%20I%20now%20have%20the%20normally%20named%20container%20plus%20an%20additional%20one%20with%20a%20suffix.%26nbsp%3B%20This%20is%20sometimes%20%22Profile_Joe.Cool-SERVER1.VHDX%22%20or%20%22Profile_Joe.Cool-Cloud.VHDX%22.%3CBR%20%2F%3ESo%2C%20an%20affected%20users%20profile%20path%20will%20look%20like%20and%20contain%3A%3CBR%20%2F%3E%5C%5CServer%5CShare%5CJoe.Cool_%3CUSER-SID%3E%5C%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Profile_Joe.Cool.VHDX%3C%2FUSER-SID%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Profile_Joe.Cool-Cloud.VHDX%3CBR%20%2F%3Eor%3C%2FP%3E%3CP%3E%5C%5CServer%5CShare%5CJoe.Cool_%3CUSER-SID%3E%5C%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Profile_Joe.Cool.VHDX%3C%2FUSER-SID%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Profile_Joe.Cool-SERVER1.VHDX%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20assuming%20this%20may%20be%20the%20result%20of%20a%20partial%20sync%20condition%20if%20a%20user%20profile%20container%20session%20is%20attempted%20against%20an%20Azure%20File%20Share%20before%20the%20sync'd%20container%20has%20been%20completely%20updated%20by%20the%20sync%20process.%3CBR%20%2F%3EI%20have%20also%20observed%20that%20the%20interestingly%20named%20container%20is%20sometimes%20mounted%20for%20the%20user%20in%20their%20session.%3CBR%20%2F%3E%3CBR%20%2F%3EHas%20anyone%20else%20see%20this%3F%26nbsp%3B%20I%20also%20am%20curious%20about%20the%20expected%20behavior%20for%20FSLogix%20in%20this%20scenario.%26nbsp%3B%20Will%20it%20always%20choose%20the%20new%20file%20with%20the%20suffix%20until%20an%20effort%20is%20taken%20to%20merge%2Fconsolidate%20the%20two%20files%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hello,

In planning to switch from a Windows IaaS File Server to using an Azure File Share on a Premium Storage account, we decided to use Azure File Sync to get all 8TB of the profile containers onto the new share in advance of a planned cutover.

For the most part this has worked out great.  But for some profiles, I've observed what looks like a probable AFS initiated renaming scenario where either the cloud endpoint (as the name  "Cloud") or the server endpoint's name is added as a suffix to the profile container name.  The end result is two different containers in a given users profile directory.

Example:
User Name = Joe.Cool
AFS Cloud Endpoint = Cloud
AFS Server Endpoint = Server1

Prior to using AFS, each users profile container is simply named as "Profile_Joe.Cool.VHDX" given the above scenario.
However, for some users I now have the normally named container plus an additional one with a suffix.  This is sometimes "Profile_Joe.Cool-SERVER1.VHDX" or "Profile_Joe.Cool-Cloud.VHDX".
So, an affected users profile path will look like and contain:
\\Server\Share\Joe.Cool_<User-SID>\
                                                            Profile_Joe.Cool.VHDX

                                                            Profile_Joe.Cool-Cloud.VHDX
or

\\Server\Share\Joe.Cool_<User-SID>\
                                                            Profile_Joe.Cool.VHDX

                                                            Profile_Joe.Cool-SERVER1.VHDX

I'm assuming this may be the result of a partial sync condition if a user profile container session is attempted against an Azure File Share before the sync'd container has been completely updated by the sync process.
I have also observed that the interestingly named container is sometimes mounted for the user in their session.

Has anyone else see this?  I also am curious about the expected behavior for FSLogix in this scenario.  Will it always choose the new file with the suffix until an effort is taken to merge/consolidate the two files?

0 Replies