i need to be able to get an alert or extract from an endpoint or login to the admin portal to know when there is sync problem. currently, the only way to know if there's a sync problem is from the user - and by the time the user tells me, it's too late. again, either a dashboard in the Admin portal that shows the sync errors or i need to be able to extract some event ID, log file or other from an endpoint to identify when there's a problem to schedule time to correct the issue - or ensure we have a backup elsewhere

Please fix compatibility issues with Roaming Profiles

Scenario 1 – can’t install NGSC on a second computer after update

The automatic update not only updates the OneDrive.exe in the local profile, but also the registry, which roams with the user. When the user logs onto a new computer and NGSC tries to run OneDriveSetup for the user, it sees the registry key and delivers a message saying a newer version is installed. By deleting HKCU\Software\Microsoft\OneDrive, NGSC will install.

Scenario 2 – registry version mismatch between updated and non-updated OneDrive.exe when roaming

If NGSC installs for the user on a second computer, but the update doesn’t occur, the registry refers to the older version (1021). When the user then logs off, the registry is uploaded to the roaming profile. The user logs back onto their primary computer with the newer version (1212) installed, and OneDrive.exe will not run because the versions do not match.

We have multiple users connected one SharePoint site and we use this sites to share documents. Due to our operational requirements we need to keep our files in the desktop PC. Therefore all the users in the organization we keep our files in the PC using OneDrive client.

The issue is when a file get deleted from one end its effecting all other users in the network by moving all the deleted files to their desktop recycle bin. Which creates huge space of deleted files and make all the users to clean their recycle bin quite often. (For us avg 4 GB per weak)

If possible please fix this misbehavior and move the deleted files only to the share point's recycle bin and in the user end just remove the files from the One Drive (desktop PC). This won't keep any copies in the user's recycle bin (desktop PC) and if they want to recover the file again they can get it back from the share point recycle bin.

I suggest you make OneDrive more “enterprise ready”. We are in the planning stages for moving user documents to OneDrive but there are glaring limitations compared to using Windows based local shares. Here is a list of requirements if we were to seek out a 1:1 match for what we do now:

1. Make all OneDrive settings controllable via GPO. Without it, deployment is a non-starter given the number of workstations that we need to visit.




2. Use a folder redirection method to access OneDrive as the default. Sync should be secondary. This will solve a few problems. One is with shared conference room computers. Now, everyone’s Documents folder redirect to a network folder. No matter where they are “Documents” is their documents. GPO controls (limits) sync to these shared computers. As OneDrive stands now, users will not have local access to documents. They need to be trained to visit OneDrive online and instructed on how to open documents locally. If we train them to sync Onedrive documents, the shared conference room computers will quickly fill up and run out of space. In a dirsync AD environment, the username and PW are the same as on O365 so it should be a small matter to make this redirection persistent without the need to load a web site and/or map a drive which all offers even more admin overhead and training issues.




3. Maybe the above request can help in a related way, but we would like the ability to scan to OneDrive from a copier. This cannot happen without significantly increasing admin overhead, or using options which are not ideal. Scan to email is limited to file attachment size so that’s out. Archaic mapping of drives manually and maintaining a persistent connection to OneDrive via the web interface is also out. Manually creating shares within the OneDrive local cache is also out as this too is too manual and prone to its own problems. The best method we can think of is to have some sort of FTP or otherwise UNC path to OneDrive to push up our scans. Ideally copier vendors would have an option to sync to OneDrive but we are not there yet.

Without the level of control GPO and other centralized management offers, it is tough to sell the benefits of this to the user base. Sure, the protection, security and other flexibility using the cloud is very compelling but it seems we have to take a significant step back in managing file storage and sharing resources to gain these benefits. Please consider the above for future enhancements of OneDrive for Business.

In OneDrive for Business today the Shared with Me view is at times difficult to follow for some users and results in 'duplicate' entries.

Here is the simple scenario for Users1 and Users2:

In User2 Documents folder create the following simple structure where the names are self-describing:

Documents\FolderSharedEditwithUser1

Documents\FolderSharedEditwithUser1\FileOwnedByUser2SharedEditwithUser1

Documents\FolderSharedEditwithUser1\FileOwnedByUser2SharedViewwithUser1

After a while the Crawler will re-index the User1 Shared with Me view. In addition to showing the primary entry:

FolderSharedEditwithUser1

It will also show:

FileOwnedByUser2SharedViewwithUser1

This is duplicated if you drill into the shared folder. End users and customers do not like seeing this and it appears to be caused by the different in permission levels (Edit versus View). This has also been replicated with the CSOM API.

Customers many times come to the conclusion that this is caused by our product, which is false. This is a bug, or an "undocumented feature," whatever you want to call it. Please reproduce and attempt to fix it.

Regards

My understanding is that when a document is deleted from a document library it goes into Trash for 93 days. After this 93 days documents get moved to the second stage recycling bin for a further 93 days. Therefore a deleted document is only truly deleted after 186 days (unless someone empties the recycling bin manually). The second stage recycling bin is only accessible by site collection administrators.

This is all well and good but what about OneDrive for business recycling bins. They follow the same policy 93 + 93 days, but in this instance the user is a Site Administrator of their own OneDrive for Business library. Say for example a disgruntled employee who is getting fired deletes all documents in his OneDrive for Business library and empties both the first and second stage recycling bin. This data would be lost without getting an entire site recovery done through Microsoft.

There needs to be a solution that allows Administrators the ability to recover data from users OneDrive for Business library.