![]() ![]() The home folders contained Known Folders using the (filesystem) English naming convention. This journey started in a tenant where user-data was moved from home folders to OneDrive using SharePoint Migration Tool (SPMT). ![]() ![]() Please visit his blog, the only place on the entire internet (according to Google) where these properties are mentioned. Note: a big thank you goes out to Patrick Lamber for pointing me in this direction. The following properties will point to a folder-object. Their names will be used (or created) during KFM: The Documents-list (not to be confused with your “Documents”-folder which is actually a folder inside this list… you know, just to keep you on your toes) contains some metadata telling a connecting OneDrive-client which folders in its dataset are ‘Known’. So, can we simply create folders with the same name? Nope, this mechanic is smarter than that. Sure, you’ll still see the same LocalizedResourceName, but the folder name on your filesystem will have changed. That change is simply synchronized to your client(s) without any issue. You can (kind of) see this tight coupling in action: just rename your “Documents”-folder via the OneDrive-portal. If so, any connecting client will follow the naming of these cloud folders. Turns out, there’s a mechanic at work which allows KFM to determine if there are already Known Folders present in its cloud-data. Our users didn’t set a PreferredLanguage, and the display language was the same now, so why were there still differences between users? My dear reader, you may have already noticed the mother of all we made… We assumed existing data in OneDrive was irrelevant. KFM then ‘redirects’ the local folders to the OneDrive folders. Even when the user has set a different PreferredLanguage.Īfter the client has determined the folder names, they are created in OneDrive. If SOFTWARE\Policies\Microsoft\OneDrive\KfmForceWindowsDisplayLanguage is set to 1 (in HKLM or HKCU), the default behavior (display language) is enforced.If the user has set a PreferredLanguage in (Azure) AD or the portal, OneDrive will follow that instead of the display language.When you use an English ISO, you get English folders (“Desktop”, “Documents”) and when you use a Dutch ISO, you get (duh) Dutch folders (“Bureaublad”, “Documenten”). By default, the Windows display language is used.While provisioning Known Folders in OneDrive using Known Folder Move (KFM), it evaluates a couple of things to determine which language to use: However, OneDrive’s Known Folder Move (KFM) fancies itself a bit of a multi-national and likes to create folders in different languages. The folders (and it’s Quick Access counterpart) are configured in registry ( HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders).A (hidden, system) desktop.ini-file is placed to configure display name ( LocalizedResourceName), icon ( IconResource) and other ‘special’ configuration.Folders are always created using English names (such as “Desktop” and “Documents”).Time to hit the docs (because who reads the manual first)! First, just to be sure, I refreshed my memory about how Known Folders are created by Windows: The version here will stay, forever reminding me of my roots. This post was re-published there (albeit in slightly redacted form). Since embarking on my first adventures in blogging, with the gracious help of Oktay, I’ve created my own blog: threeisacloud.tech. The folder names seemed to be unaffected by the image language. It didn’t make any difference whatsoever. We installed the exact same image (and language) on all devices and lo and behold… I couldn’t, for the life of me, see the logic in it.Īt first Oktay and I figured it had to be related to the Windows image or to be specific: its language. Somehow, some users had English folder names, while others showed Dutch folder names. In this case, there appeared to be a disconnect between the naming of Known Folders in OneDrive across users. Sometimes I stumble upon app behavior that intrigues me. ![]()
0 Comments
Leave a Reply. |