This message was deleted.
# citrix-vad
s
This message was deleted.
e
Autopatch will update OD4B, Team, Edge and M365.
n
MS has multiple ways of updating OneDrive, and really, the best method that I have found is to tackle it at installation. Here's my install script for the OD client:
Copy code
$var_Install_Exec = "OneDriveSetup.exe"
$var_Install_Arg = "/allusers"

$proc = Start-Process -FilePath $var_Install_Exec -ArgumentList $var_Install_Arg -WorkingDirectory $PSScriptRoot -PassThru
Do { Start-Sleep 5 } While (Get-Process | Where ProcessName -eq OneDriveSetup.exe)
Start-Sleep 10
schtasks /change /tn "OneDrive Per-Machine Standalone Update Task" /disable | Out-Null
Get-ScheduledTask -TaskName "OneDrive Per-Machine Standalone Update Task" | Unregister-ScheduledTask -Confirm:$False | Out-Null
Get-ScheduledTask -TaskName "OneDrive Reporting Task*" | Unregister-ScheduledTask -Confirm:$False | Out-Null
If (!(Test-Path "HKLM:\SOFTWARE\Policies\Microsoft\OneDrive")) {
	New-Item "HKLM:\SOFTWARE\Policies\Microsoft" -Name "OneDrive" -Force | Out-Null
}
New-ItemProperty "HKLM:\SOFTWARE\Policies\Microsoft\OneDrive\" -Name "GPOSetUpdateRing" -Value 0 -PropertyType "DWORD" -Force | Out-Null
Set-Service -Name "OneDrive Updater Service" -StartupType Disabled
Stop-Service -Name "OneDrive Updater Service" -Force
Long story short, you want to disable/delete the OneDrive scheduled tasks that are created as part of the install, and then set the update ring to 0, which is Deferred. This will at least buy you time by not being on the Production ring.
👍 1
You'll also want to disable the 'OneDrive Updater Service' service, as well. I enforced this via GPO even though I was disabling it via the install script.
👍 2
n
Thank you sir
@Nick Panaccio - are these large enterprises that are changing the updates to deferred....i am a little hesistant on recommending this to a client b/c of security reason. however, for non-persistent there is no point running updates on those b/c after they reboot it reverts to the old version. its a waste of especially if there are workstation VDIs. just thinking out loud here
n
I can only speak for myself, with regards to my last company - my suggestion to stick with the Deferred ring was based on prior issues with the OneDrive client while in the Production ring. Multiple issues, mind you, all affecting end users. Given that like 90% of OneDrive's updates are listed as "We've resolved product issues to improve the reliability and performance of the OneDrive sync app.", I felt like this was a no-brainer. Moving to Deferred really just allows you to choose when you upgrade to a new OneDrive client, and not Microsoft. If you want to install the latest and greatest in your image, go for it. That policy won't prevent manual installations. And the last thing I want is for MS to control OneDrive updates. I used the same philosophy towards Teams, too.