- #DOWNLOAD NEW ONEDRIVE FOR BUSINESS SYNC CLIENT FULL#
- #DOWNLOAD NEW ONEDRIVE FOR BUSINESS SYNC CLIENT DOWNLOAD#
I just moved mine to a different folder out of the way. You won’t be missed, groove.exe.Īt this point you should make a backup of the files left on your local disk. Select each of the libraries you’re synchronizing and choose Stop syncingĪs a final act of annoyance my legacy OD4B client crashed when I removed the last synchronized folder.Right click the system tray icon and select Stop syncing a folder.
As you’ll see, they’re not steps that would be convenient to run through for every user in your environment, but for your own testing purposes and to see how the new features behave before they are rolled out to your clients you might want to try the preview on your own computer or with a few tech savvy users.įirst, disconnect existing synced libraries from the legacy OneDrive for Business client: To get access to the preview of the new features, follow the directions here.
#DOWNLOAD NEW ONEDRIVE FOR BUSINESS SYNC CLIENT FULL#
A list of other improvements is also included in the announcement, which you can read in full here. 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. That’s something to keep in mind.When the OneDrive for Business Next Generation Sync Client (which I’ll just refer to as OneDrive for Business) began rolling out, one of the missing features was the ability to synchronize content with SharePoint document libraries. When a user is logged on through RDP, the UserName property will be empty.
The UserName property is only populated with a value if the user is logged on locally (console). On a side note, the script below gets the logged on user name from the Win32_ComputerSystem class. Remember to define the minimum required version in the script from below, that you want to support. When the detection method is invoked prior to installing the application, if the OneDrive.exe file doesn’t exist it shouldn’t output anything which is interpreted by ConfigMgr as Not Installed. Remember, the script detection method should only output to the STDOUT (done by returning data to the pipeline in PowerShell) if the OneDrive.exe file exists. When the correct user profile path has been determined, it then validates the if the OneDrive.exe exists and is of the specified version. This script gets the current logged on user and determines the profile path by matching the user name with the SID information in the UserProfileList registry keys. The OneDrive Next Generation sync client can be downloaded from the following site:īelow is my take on how the script detection method used for the OneDrive Next Generation sync client should look like.
#DOWNLOAD NEW ONEDRIVE FOR BUSINESS SYNC CLIENT DOWNLOAD#
Download the OneDrive Next Generation sync client This got me writing this post, so that administrators out there can be successful in their OneDrive Next Generation sync client deployments with ConfigMgr. It has a few flaws, for instance it doesn’t check the version of OneDrive.exe in addition to that it doesn’t determine the correct user profile path. Microsoft has provided a short guide for how this new version can be deployed with ConfigMgr, however the method they’ve shared for the script detection method is not something that I’d recommend to my customers. The OneDrive Next Generation sync client offers end users to add both personal accounts and work accounts, all in the same sync client. Yesterday, Microsoft released a new version of the OneDrive Next Generation sync client (.0509) with improvements to the deployment experience for administrators.
It offered a lot of improvements, but was it demanded custom installations wrappers to deal with various command and registry keys. A while back, the released what’s referred to as the OneDrive Next Generation sync client. It’s unfortunately well known that this client had it’s drawbacks and Microsoft have been aware of this for some time now. For businesses and organizations that have taken the path to cloud with Office 365, have most likely heard about the OneDrive for Business sync client.
0 kommentar(er)
