- #ONEDRIVE SYNC CLIENT FOR SHAREPOINT OFFLINE#
- #ONEDRIVE SYNC CLIENT FOR SHAREPOINT WINDOWS#
The EnableDisableSiteSync function takes two parameters site url and action, if you need to run disable or enable all sub sites under the given URL then you can iterate through all sub sites and perform the required action.
I am sharing a PowerShell script which could be helpful enabling or disabling sync at the site level.
Enable / Disable Sync for a Site using PowerShell Libraries in the site, you verify that be visiting any of the document library This will disable the sync option from all document
#ONEDRIVE SYNC CLIENT FOR SHAREPOINT OFFLINE#
Option for “ Offline Client Availability” (check screenshot at top)
Click on “ Search and Offline availability option” listed under “ Search”. Enable / Disable Sync for a Siteįollow the below steps to enable / disable sync button for a Would be very helpful if you trying to disable sync on multiple sites or forĪll sub sites under a site or site collection. I will be sharing two different ways for achieving this jobīy enabling/disabling from site settings and PowerShell. And there could also be requirements where site administrator require to disable offline availability of all content from a site. Even if it is just installing OneDrive on a server/VM then making sure it is getting targeted by your regular backup software.There are requirements for some specific content where site administrators require to disable document syncing on some of the document libraries ( check this this blog post to learn about enabling and disabling sync on a document library). Thankfully it was immediately obvious and we were able to recover using the inbuilt recycle bin.Įnd of the day it works but I would suggest looking into a backup solution. As best we can tell it hopped between which drive/s it saw as "active" and made OneDrive delete everything. We did have one extremely weird case where a person who had a raid setup on their home machine had their array degrade. Maybe a call from a client every month or two because of some weird edge-case (like their firewall blocking OneDrive because they clicked the wrong button, or OneDrive just not loading after boot). Having said this though, once we got the file/folder names sorted, and people upgraded machines/internet connections it works. This is somewhat resolved by the Files on Demand feature, but these people with 64GB of EMMC storage are often the same ones with bad internet connections.ģ) Invalid names causing OneDrive to get stuck. The biggest issues we've seen clients run into with OneDrive have been because of:ġ) Slow internet connections - people don't grasp that their $10/month internet connection running at 1kbps because they are 5km away from the phone exchange just can't handle even a few GB of data.Ģ) Lack of local drive space. This will be a painful migration, but I am thankful our users have started to see the benefits of SharePoint, and more willing to put up with this pain because the end result will be better. But since we have started the process, we must finish. I am frustrated at everything, and everyone, but also understand where they are coming from. Or users thinking that the sync client should be able to sync all files from every department like before, all the way back to 2005. #ONEDRIVE SYNC CLIENT FOR SHAREPOINT WINDOWS#
"well it let me save it, so it must be fine." No, it's not and just because windows didn't tell you no, doesn't mean there won't be problems down the road. "Department\Documents\Department Documents\ Important Department Documents\ ,Important Department Documents\ ,Important department documents\ ,\Important Department Document name with half the contents of the file in the name with a truncated endi~.docx" and then every file in a new folder like this. We're moving forward.Īnd our users love making files paths like this abomination: So, even without my mistakes I think it would have just been a sh%tshow anyway. Where I am, users throw their hands up and say "I don't have time to learn", "I don't care", I'll just use the sync client forever, etc.
I made mistakes too, and no system is perfect. I wish I had the manpower to make fantastic training, or have simply done better. I would have liked for the organization I work at to understand department sites and sync client limitations, and proper sharing. Microsoft has made it extremely clear this is the way forward, not 1995's network drive approach of endless folder paths to the 9th circle of Dante's Inferno. And that is why we are now building out department sites to break the habit of exclusively using the sync client as the sole way of interacting with files.
0 kommentar(er)
