Forum Discussion
SharePoint Online Team Sites - AutoMount
- Jan 11, 2019Hi!
Still on the Microsoft 365 Roadmap as in development
https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=Onedrive%2Cfor%2CBusiness
Featured ID: 27031
Added to Roadmap: 5/21/2018
Last Modified: 1/10/2019
Tags: OneDrive for Business, All environments
Hope that answers your question!
Best, Chris
Howdy!
I've been working with Microsoft and finally got this figured out today, and working consistently. Please see below for instructions to get this working:
Pre-Requisites:
Tenant ID (A):
- First, get your tenant ID using the steps in the following document:
- https://docs.microsoft.com/en-us/onedrive/find-your-office-365-tenant-id
- Copy this address somewhere like notepad, it will be in a format of XXXXXX-XXXXX-XXXXX......
- Next we need to replace the dashes with their HTML format: %2D
- For example: 11111-11111-11111..... should become:
- 11111%2D11111%2D11111.....
- Make note of this newly formatted ID
Library ID:
- Navigate to the library you are trying to sync
- Press "Sync"
- Press "Copy library ID"
- Press "Allow Access" if it pops up
- Paste the ID somewhere like notepad.
Formatting the URL (B):
- In the library ID look for the following line and paste it in another location in notepad:
- webUrl=https%3A%2F%2Fyourdomain%2Esharepoint%2Ecom%2Fsites%2Fsitename
- We now need to un-format this from HTML and put it as a regular URL. So, the line above would become:
- webUrl=https://yourdomain.sharepoint.com/sites/sitename
- Make note of the newly formatted URL.
Putting it all together:
Now we need to take all of the information we gathered and create the final library ID.
- Find your un-edited Library ID.
- Make the following changes to the URL:
- tenantId=<Your updated tenantId> - (A) listed above.
- webUrl=<Your updated URL> - (B) listed above.
- Your final result should look like below:
- tenantId=XXXXXXXX%2DXXXX%2DXXXXX.....&siteId=.....&webId=.....&listId=.....&folderId=.....&webUrl=https://yourdomain.sharepoint.com/sites/sitename&version=1
Creating the GPO:
Now follow the steps in the the "Use Group Policy to control OneDrive sync client settings" document to create your group policy (Mine is based on User):
https://docs.microsoft.com/en-us/onedrive/use-group-policy
- Deploy the GPO to your test machine(s)
- Ensure that the registry gets successfully updated
Waiting:
This will not work right away, no matter how much rebooting, closing/opening OneDrive, refreshing group policy you do. After some time passes, something will trigger the sync and the folder (should) will magically appear for you. For me; it took 2 hours from when the GPO was applied, to when it decided to sync itself.
My config:
OS: Windows 10, 1903
OneDrive: 19.123.0624.0005
Hope that helps!
- pgawronskiAug 26, 2019Brass ContributorColachoMendoza what version of OneDrive you have if you don’t mind me asking as maybe they have fixed this with the latest client release.
- ColachoMendozaAug 26, 2019Brass Contributorright now 19.123.0624.0005 I don't think thre's been many updates but certainly may be this is the latest.
as this is what they have up for Download OneDrive for Windows - 19.103.0527.0003 (July 15, 2019)
https://support.office.com/en-us/article/onedrive-release-notes-845dcf18-f921-435e-bf28-4e24b95e5fc0?ui=en-US&rs=en-US&ad=US- pgawronskiAug 26, 2019Brass Contributor
ColachoMendoza , yeah I am on the same version, it is syncing fine on my end just thought it may be the case for the quicker update/sync on the endpoints.
ColachoMendoza Also, have you re-formated the library ID as per above post suggestion? with clean WebURL?
- Chris ShaldaAug 26, 2019Brass ContributorColachoMendoza, I don’t suspect that an AD replication issue is occurring here, whereby it took a couple hours for the auto-mount config to work on the endpoint after applying the GPO. It is very clear in the auto mount team sites policy config documentation that the config may take up to 8 hours to take effect, which is by design to balance the load of the requests.
I saw a similar time delay even when creating the respective registry keys manually, which is all the GPO is doing.