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
Andrew.wheeler
shared this idea
25 comments
-
Jake Ives
commented
This is a big issue and Microsoft need to release a fix. It's gone on for too long.
-
Anonymous
commented
I will second the need for a (Omit or Disable Shortcut Sync) option. Our users migrate around to many different devices and complain about having multiple copies of the same desktop shortcut appear. Very confusing and inconvenient.
-
Neville Billingham
commented
It needs a fix.
We deploy shortcuts by GP that are user specific and with every different PC the user logs into another set are created.
Please add a tick box "Omit Shortcuts" in the client as a global setting or for each of the folders in manage back-up screen. Also add it to the GP template so it can be controlled.
It will make such a difference.
-
Anonymous
commented
I have workplace of 9000000000 users. WTF Microsoft?
-
Anonymous
commented
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.
-
Anonymous
commented
Same here. Our shortcuts created from login script stored in DC server.
-
Anonymous
commented
Major headache duplicate link
-
Anonymous
commented
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.
-
MikaelJones
commented
Major headache for our Enterprise Customers with thousands of licenses. Has this been acknowledged by Microsoft?
-
Rob
commented
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.
-
os
commented
I too am having the same issue with Edge and Teams shortcuts created on user desktops. Please fix this issue.
-
Evangeline
commented
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?
-
Anonymous
commented
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
https://www.adamfowlerit.com/2020/01/onedrive-pc-folder-backup-and-desktop-shortcut-duplicates/
-
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:
https://admin.onedrive.com/?v=SyncSettings
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
-
Anonymous
commented
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:
@echo off
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.
-
Anonymous
commented
There should be a fix for this problem. It's really annoying to have al the duplicates on the desktop for so many users.
-
Dan
commented
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.
-
Joe
commented
Aside from the ideas already in the threat, has anyone else come up with a good workaround?
