One Drive Known Folder Move
Do not sync shortcuts (.lnk) from Desktop Folder to onedrive when using Known Folder Move This causes duplicate shortcuts if you set up a new device and sync. If you have the same shortcuts on the desktop as your original machine you will then get a "Copy" shortcut from the sync
I have workplace of 9000000000 users. WTF Microsoft?
Any Solution yet? If I block .lnk sync via https://admin.onedrive.com/, user will get error messages and are confused.
I hope there will be a solution as soon as possible.
Same here. Our shortcuts created from login script stored in DC server.
Major headache duplicate link
Fix edge and Teams to not do shortcuts per User and/or fix this duplicate short cut nonsense. This request should’ve been handled by now.
Major headache for our Enterprise Customers with thousands of licenses. Has this been acknowledged by Microsoft?
Same issue, preventing me from wanting to deploy this into our organisation. While I appreciate all the development the team are doing, this just seems like something that should not have been missed and\or resolved before trying to incorporate other bigger stuff.
I too am having the same issue with Edge and Teams shortcuts created on user desktops. Please fix this issue.
This is such a terrible UX. I have more than 10 copies of Teams, EDGE, Chrome, etc on my desktop and similarly in other redirected folders. When is Microsoft resolving this issue that has been known for over 6-8 months now?
any update on this Microsoft?
Adam Fowler commented
I wrote up a quick blog post on the best workaround I could come up with on this - involves Group Policy and using the Public Desktop location, but agree there needs to be a better solution
Michael Mutch commented
You can always use the sledgehammer approach and just prevent all .lnk files from syncing to onedrive.
Go to the onedrive admin centre:
and simply block the syncing of specific file types 'lnk' as pictured below. The users will see an error that the file couldn't be synced but it's better than having multiple copies of the same link
This is a very annoying issue. I ended up writing a batch file that runs at user logon to work around until Microsoft can implement a fix:
if exist "%onedrive%\Desktop" del /f /q "%onedrive%\Desktop\*- Copy.website"
if exist "%onedrive%\Desktop" del /f /q "%onedrive%\Desktop\*- Copy (*).website"
if exist "%onedrive%\Desktop" del /f /q "%onedrive%\Desktop\*- Copy.lnk"
if exist "%onedrive%\Desktop" del /f /q "%onedrive%\Desktop\*- Copy (*).lnk"
if exist "%onedrive%\Desktop\Desktop (1).ini" del /f /q "%onedrive%\Desktop\Desktop (*.ini"
Ross Young commented
Of course, there is the option of moving the .lnk files to the Shared Desktop location if that is applicable.
There should be a fix for this problem. It's really annoying to have al the duplicates on the desktop for so many users.
The best workaround i could figure out was to create a GPP removing the file using %onedrive%\desktop\microsoft teams.lnk. It won't remove it on first login/profile creation since Teams starts a bit after the GPP is processed the first time. But upon the next GPO update cycle it is removed. Not really clean but it will do for now.
Aside from the ideas already in the threat, has anyone else come up with a good workaround?
I am also coming across the same issue when using KFM for a 3,00 user deployment. I thought deleting the duplicates, then blocking the .Lnk files via the OneDrive Sync Admin console would resolve the issue. I can though see the issue come back for the every desk move, after testing the outcome. There should be an additional OneDrive feature added to the new Admin Template profile in Intune, to resolve this issue :(
Scott Meyer commented
The issue with .lnk files duplicating is preventing a rollout of OneDrive/KFM at my workplace of 60,000 users.
I attempted to work around the issue by adding an exclusion to OneDrive restricting the syncing of .lnk files. The restriction prevents the duplication of .lnk files on the desktop but the client generates an error and the user is then notified that the lnk files won't sync due to restrictions. I don't know which problem is worse.
We also have the same issue. We have a number of multi-user machines in our labs that our techs can access as needed. With 20 machines and 60+ techs, you can imagine the number of duplicates that occur.
We need additional group policy control to prevent these issues. I suggest the following policies that allow the following:
1) Exclude/Include known folder policy control. This should allow all known folders to be included or excluded and should be a list type setting where a folder can be added or excluded, but can set to:
Known Folder Name - Value
Known Folder Name would be the following known folders:
Desktop, Downloads, Documents, Music, Pictures, Videos
Value should be as follows:
0 - Include and lock down, user cannot modify
1 - Include by default, user can modify
2 - Exclude and lock down, user cannot modify
3 - Exclude by default, user can modify
Behavior of “Silently move Windows known folders to OneDrive” would be:
- Folders with values of 0 would sync automatically and user cannot exclude them.
- Folders with values of 1 would sync automatically by default, but user can change this and exclude these folders if desired
- Folders with values of 2 would be excluded from syncing and the user cannot include them.
- Folders with values of 3 would be excluded from syncing by default, but user can change this and include these folders if desired
Behavior of "Prompt users to move Windows known folders to OneDrive" would be:
- Folders with values of 0 would be shown at the prompt screen as selected, but grayed out where the user cannot deselect them.
- Folders with values of 1 would be shown at the prompt screen as selected, and the user can deselect them if desired.
- Folders with values of 2 would be shown at the prompt screen as deselected, but grayed out where the user cannot select them.
- Folders with values of 3 would be shown at the prompt screen as deselected, and the user can select them if desired.
2) Excluded files from OneDrive sync
A policy that allows files to be defined that are excluded from sync. This would be a list format setting such as:
Folder - Filename
Folder value - would be explicit foldername or wildcard. "*" that would exclude the file from all known folders, or the known folder name such as "Desktop"
Filename - Would be explicit filename or wildcard. E.g. "Microsoft Edge.lnk", "*.lnk", "*.url", "Google Chrome*.*"
Wildcard control is critical so that duplicate links with "- Copy" or "(2)" would also be excluded without having to explicitly define each.
3) Duplicate file handling
A policy that should define how duplicate files are handled. This could be done in the following ways:
a) Prompt - Ask user what they want to do - Overwrite, Keep old, Keep both (add - Copy to filename) - Similar to a Windows Explorer file copy
b) Silently overwrite with newest file
c) Silently keep both and add "- Copy"
d) Silently keep old file