- #ONEDRIVE FOR BUSINESS SYNC CLIENT INSTALLER HOW TO#
- #ONEDRIVE FOR BUSINESS SYNC CLIENT INSTALLER CODE#
- #ONEDRIVE FOR BUSINESS SYNC CLIENT INSTALLER WINDOWS#
First Release customers will begin seeing it in the next few months, and remaining customers will be rolled out in early 2017 (which is later than originally promised, but at this point I’m just glad to see it finally happening). Using the legacy OD4B client (also known as groove.exe) has been a long-running source of frustration, with every attempt to work on files in the library requiring a troubleshooting session for sync and auth problems.Īt Ignite 2016 Microsoft has finally announced that SharePoint library sync has arrived (in Preview form) for OneDrive for Business. This also meant that synchronizing with files in Office 365 Groups was not possible, which for me personally was an annoying feature gap because we use an Office 365 Group to collaborate on writing and updating Office 365 for IT Pros.
#ONEDRIVE FOR BUSINESS SYNC CLIENT INSTALLER CODE#
Here is a dead simple example code you can use, just change the $DomainGUID to your own To solve this, you should wrap up the script as a win32 app, deploy it as a required app to a relevant device group and make it required as part of the autopilot ESP. While this might sound like a perfect use case for Endpoint analytics Proactive Remediations, you will run into a chicken-egg problem when a user starts up a brand new device, namely that the user has most likely logged into to a new device before the proactive remediation has run. The method described in this blog post is a nice stop-gap until you can set those up. Now before we celebrate, we need to make a note that ideally you should be using conditional access and compliance policies to control access to corporate data. I do have to point out that there are security concerns with this reg key: the domain GUID on the device and in the SharePoint service must match, but effectively the device is allowed to create the domain GUID and is allowed to sync if it matches Sync a SPO site on the test AADJ machine, the test machine should be able to sync.
Add the same GUID to SPOTenantSyncClientRestriction / OneDrive admin center to allow the test machine for SPO.Set the GUID for policy AADJMachineDomainGuid under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\OneDrive and apply it to the test AADJ machine.Ensure build 19.192+ of Sync client is installed (which was released in november 13, 2019).
#ONEDRIVE FOR BUSINESS SYNC CLIENT INSTALLER HOW TO#
Here are instructions for how to add Azure AD Join devices to your OneDrive for Business tenant restrictions.
#ONEDRIVE FOR BUSINESS SYNC CLIENT INSTALLER WINDOWS#
Needless to say this was worrying since we were knee deep in migrating all new devices to AzureAD The Solutionīut lo and behold, a golden savior appeared on the windows admins discord, a swell fellow called Configmatt commented: Our Legacy AD joined devices were fine, but all of our Azure AD joined devices got the above error. Which resulted in this message on my corporate device which effectively blocked my AzureAD device ? I later learned that my endpoint administrator, Adam Gross, had enabled Allow syncing only on computers joined to specific domains in the OneDrive admin portal. So I was walking on the beach and noticed that OneDrive wasn’t syncing anymore on my AzureAD joined laptop.