New File Viewers for OneDrive, SharePoint and Teams
To support OneDrive's vision is to enable you to share and work together on all your files in a simple and secure way, we’ve continued to invest in and improve our file viewing technology and currently support over 300 file types and growing. This enables users to get high-fidelity previews and thumbnail images for Adobe formats, like Photoshop and Illustrator, 3D files or DICOM medical images without installing the native application.OneDrive - Files on Demand - "a newer version is available"
A customer faces the irregular condition that files located on OneDrive for Business or SharePoint show a message band in Office App "A newer version is available" OneDrive: 22.012.0117.003 and previous version including release versions Windows 10: 19044.1466 Office Version: 2108, SAC, M365 apps for Enterprise Affected users: all Reproducible: yes (for this customer) The issue is that every file gets this notification on opening files, file won't be synced correctly but will ask to save new version / file. UNLESS: we deactivate "use office applications to Sync office files that I open" BUT the customer needs this feature in the first place. Anyone else with the issue or a solution?OneDrive Files On-Demand For The Enterprise
OneDrive Files On-Demand has been designed from the ground up for enterprises. Files On-Demand leverages the Windows Fall Creators update to simplify the user experience with cloud storage and sync, bring the power of the cloud into Windows File Explorer, and dramatically limit the network impact of sync on your corporate network.
How do I reduce the possibility of syncing entire sharepoint libraries with Files on Demand?
I would like to utilize the new FOD feature in OneDrive for users OneDrives and also Sharepoint libraries. One of the things I am concerned about is users right clicking Sharepoint library folders and selecting "always keep on this device" not realizing it will sync everything under that. Is my only option at this point just good education for our users? Or are there ways to help stop that through group policy or some other method?
KFM with vs without Files On Demand: Need to decide and Need Pros, Cons of each?
We're getting ready to deploy OD4B with KFM. There's some disagreement in my Project Team about whether to include mandatory Files On Demand (FOD) in the GPO. With a few exceptions AFAIK disk space on laptops is not an issue with local data. (It WILL be once we move the network personal drives to OD4B). AFAIK the 'M' in KFM means 'migration/move,' not 'copy'. I also know that FOD replaces all local content with pointers to OD4B, the location(s) of which can then be managed by the users with a simple right-click. Files no longer live locally and require internet connectivity to access unless/until changed. What I don't know is what the specific difference would be during the initial deployment & ongoing use of OD4B with KFM if we DO NOT include FOD. Would it be a 'copy' operation of the KFM contents to OD4B, with the status set by default to 'Locally Available?' I'm wanting FOD, as it gives us a true authoritative and single source for user data, which they can switch back/forth as needed. Others think there will be hand-wringing and support problems if users forget to click on a file to make it locally available on their device outside of Internet access. All advice/suggestions/experience appreciated!Your files, your way- The team behind OneDrive Files On-Demand
The building of OneDrive Files On-Demand has required a deep collaboration between the Windows and OneDrive engineering teams. From the start, the goal of engineering has been to make Files On-Demand an intuitive, secure and easy to use feature for our users.
Files On-Demand - Clean up function removes files set to be always available
Hi, we're testing OneDrive's Files On-Demand feature. There're two things, currently, hat we forsee might be difficult to explain to our users. Firstly, the difference between "locally available" and "always available". Secondly, and this is my question, why the context menu option to clean up also removes files set to be always available. We had assumed that this would only remove files marked as locally available and files set to be always available would remain untouched. Is this the correct behaviour? If so, "always available" only comes into play when locally available files that haven't been used in a while are automatically purged. Thanks for your input.
