Purpose
This guide helps users confirm that all content is fully synced and update their local OneDrive folder names after a SharePoint folder is renamed.
Before You Begin
Follow these steps when a SharePoint folder has been renamed, and your local computer still displays the older folder name.
Step 1: Confirm All Content is Synced
Windows
- Open the OneDrive menu from the taskbar.
- Ensure the status shows "Up to date".
- Open the folder and verify that no files show sync arrows, errors, or pending uploads.
Mac
- Open the OneDrive menu from the menu bar.
- Ensure the status shows "Up to date".
- Review the folder and verify that no files have conflicts or errors.
Step 2: Disconnect the Current Sync
- Open the OneDrive menu.
- Select Settings → Account.
- Under "Sites you're syncing," locate the client folder.
- Select Stop sync and confirm.
This stops the local sync only. Files remain safely in SharePoint.
Important Before Continuing
Do not delete your local folder until the previous steps are fully completed. Confirming sync status and stopping the OneDrive sync first prevents data loss, missing files, or sync conflicts. Only proceed once you are certain everything has successfully synced, and the connection has been properly disconnected.
Step 3: Delete the Local Copy
- Open File Explorer or Finder.
- Locate the old client folder.
- Delete the folder from your device.
Step 4: Resync the Renamed Folder from SharePoint
- Open the client's SharePoint site in your browser.
- Navigate to the renamed folder.
- Select the Sync option.
- Approve the prompt to open OneDrive.
OneDrive will create a new local folder with the updated name and begin syncing files.
Troubleshooting Tips
- Restart OneDrive if syncing does not begin automatically.
- Try a different browser if the Sync button does not appear.
- Use the OneDrive Troubleshooter in OneDrive → Help & Settings → Troubleshoot.
IT Support Contact
If you need additional help, contact:
Email: itsupport@insourceservices.com
Subject Line: Include "SharePoint Sync Issue"
``
Comments
0 comments
Article is closed for comments.