How are people finding the reliability of Onedrive in Windows 10

[maxrebo]

Just looking for some feedback on the use of Onedrive on Windows 10,

I had a big push for staff to use Onedrive in Windows 7 but we had so many issues with Syncing (I, on a daily basis received sync errors for no apparent reason) that eventually SLT decided to pay for (some) Dropbox licenses!.

I`m now looking to reboot this with Windows 10 (mass roll out this summer).

I've just set this up on my W10 machine to test, it looks prettier at least!

[tmoon-mint]

I have OneDrive setup here for all staff with files on demand enforced by GPO. The same GPO also signs the staff in to the OneDrive client silently using their domain credentials (We use Azure AD sync)

 

Not had anyone report any issues yet. Files on demand helps massively as its only syncing files locally when they use them.

Edited May 11, 2018 by tmoon-mint

[sted]

for me personally at home /school on my hotmail account its fine not really fired it out to teachers yet

id be wanting to use window 10 1709/1803 and the latest onedrive client and gpos as you can set pcs to on demand mode so tehy dont sync every file they only sync used files (less important on staff laptops but you dont want shared pcs having gbs and gbs of stuff on them because random user logged on once

[free780]

Seems to be fine. I think the main issues are caused by not allowing all the Office 365 domains staright out. Proxying that amount of persitant connections is bound to cause issues.

[Joanne]

The new client is so much better than the OneDrive for Business client that came with Office 2016.

 

TOUCH WOOD, my only issue is with staff changing their e-mail password and then not updating it on the client. I don't have the AD sync set up here because LA manage our tenure.

[Katy]

Does the new client need any AppX packages installed? On a fresh install (but from MDT so it removed all the AppX stuff) double clicking the onedrive EXE does nothing

[tmoon-mint]

Does the new client need any AppX packages installed? On a fresh install (but from MDT so it removed all the AppX stuff) double clicking the onedrive EXE does nothing

 

Have you got a software restriction policy in place? I did and had to pop an exception in because it was blocking the onedrive client from running within appdata.

[Katy]

Have you got a software restriction policy in place? I did and had to pop an exception in because it was blocking the onedrive client from running within appdata.

Oooh probably, I forgot it forces it into appdata. Pretty useless when it needs to be installed multiple times for everyone (once per user per machine, so for people who move machines a nightmare), how's everyone else find it (or manage to get it to not be a total nightmare)?

[DalekSec]

Since the big update just over a year ago it's been fine, had a few problems but that's always been user area.

 

All our staff Surfaces are redirected to OneDrive so everything the staff do is backed up, 95%+ of them are running fine.

[free780]

I've got a server downloading the latest client and copying to each PC in c:\windows\syswow64. You cant get away from the per user updating. Several enterpise folks want the updates adding to WSUS. Shared devices are an after throught for the sync client.

 

Start-Transcript -Path 'c:\temp\onedrive_download.log' -Verbose

 

#Production Ring

 

#Rolling out Version

Invoke-WebRequest -Uri "https://go.microsoft.com/fwlink/?linkid=860984" -OutFile "\\\\OneDrive Client\Production\Rolling Out\OneDriveSetup.exe" -Verbose

#Last released Version

Invoke-WebRequest -Uri "https://go.microsoft.com/fwlink/?linkid=844652" -OutFile "\\\\OneDrive Client\Production\Last Released\OneDriveSetup.exe" -Verbose

 

#Enterprise Ring

 

#Rolling out Version

Invoke-WebRequest -Uri "https://go.microsoft.com/fwlink/?linkid=860988" -OutFile "\\\\\OneDrive Client\Enterprise\Rolling Out\OneDriveSetup.exe" -Verbose

 

#Last released Version

Invoke-WebRequest -Uri "https://go.microsoft.com/fwlink/?linkid=860987" -OutFile "\\\\OneDrive Client\Enterprise\Last Released\OneDriveSetup.exe" -Verbose

 

#See https://support.office.com/en-gb/article/new-onedrive-sync-client-release-notes-845dcf18-f921-435e-bf28-4e24b95e5fc0 for versions.

 

Stop-Transcript

 

Then for the client

 

$onedriveversion = Get-Item "C:\windows\syswow64\OneDriveSetup.exe" | Select-Object -ExpandProperty VersionInfo | Select-Object -ExpandProperty ProductVersion

 

$rollingoutversion = Get-Item "\\\share\OneDrive Client\Production\Rolling Out\OneDriveSetup.exe"| Select-Object -ExpandProperty VersionInfo | Select-Object -ExpandProperty ProductVersion

 

if($onedriveversion -ne $rollingoutversion){

 

#Set ownership to user

$ACL = Get-ACL "c:\windows\SysWOW64\OneDriveSetup.exe"

$Group = New-Object System.Security.Principal.NTAccount("NT AUTHORITY\System")

$perm = New-Object system.security.accesscontrol.filesystemaccessrule("NT AUTHORITY\System","FullControl","Allow")

$ACL.SetOwner($Group)

$ACL.SetAccessRule($perm)

Set-Acl -Path "c:\windows\SysWOW64\OneDriveSetup.exe" -AclObject $ACL -Verbose

 

#Download latest version and replace file

Copy-Item -Force "\\server\share\OneDrive Client\Production\Rolling Out\OneDriveSetup.exe" -Destination "c:\windows\SysWOW64\OneDriveSetup.exe" -Verbose

 

#Remove Permission from file

$ACL = Get-ACL "c:\windows\SysWOW64\OneDriveSetup.exe"

$rules = $acl.access | Where-Object {

(-not $_.IsInherited) -and

$_.IdentityReference -like "\System"

}

ForEach($rule in $rules) {

$acl.RemoveAccessRule($rule) | Out-Null

}

Set-Acl -Path "c:\windows\SysWOW64\OneDriveSetup.exe" -AclObject $ACL -Verbose

 

#Set Owner as Trusted Installer

$ACL = Get-ACL "c:\windows\SysWOW64\OneDriveSetup.exe"

$Group = New-Object System.Security.Principal.NTAccount("NT SERVICE\TrustedInstaller")

$ACL.SetOwner($Group)

Set-Acl -Path "c:\windows\SysWOW64\OneDriveSetup.exe" -AclObject $ACL -Verbose

}

else {$null}

 

Use it in a scheduled task as SYSTEM. Of course test in your environmnet first. Your servers need 80,443 outbound no proxy.

[Katy]

I've got a server downloading the latest client and copying to each PC in c:\windows\syswow64. You cant get away from the per user updating. Several enterpise folks want the updates adding to WSUS. Shared devices are an after throught for the sync client.

 

 

 

Then for the client

 

 

 

Use it in a scheduled task as SYSTEM. Of course test in your environmnet first. Your servers need 80,443 outbound no proxy.

How's it get installed once it's in syswow64? Does Windows 10 just use that and do it automatically without me having to do anything? (and then set the relevant GPO settings for it to do the "files on demand" thing)

[free780]

So by default OneDrivesetup.exe runs as the user and checks for updates. If OneDrivesetup.exe is up to date it starts OneDrive.exe. On the first login for a user. So set the GPO options and test aslong as you have SSO configured, ADAL should kick in if the registry setting is present.