OneDrive Machine Wide Install

[craigcamacho]

Hi,

 

I have just migrated all my Staff and Students from on-prem file storage to OneDrive. I have all my GPOs set up so it logs them in automatically, files on demand, KFM etc. Ideally I would like it so that when they log in for the first time that it doesn't have that delay from having to run OneDriveSetup.exe from AppData for every user. I know I can download and run OneDriveSetup.exe /allusers for a machine wide install but this seems to throw up a UAC prompt when a user logs in. How have other people dealt with moving away from the the per-user install from appdata to per-device in Program Files? If using SCCM or MDT do you put this in your Task Sequence? How do you deal with deploying this for existing users?

[supportman]

From experience of doing this I wish I had not rolled out onedrive client (we just did it with PDQ deploy remotely with the /alluser switch and no UAC enabled).

 

We now only really use the Web for access and I think its so much better personally than local syncing and all the issues that come along with it.

 

We're 2 years in now and I would not deploy any OneDrive locally if I did it again.

Edited September 12, 2022 by supportman

[bald_pig]

We just use the built in onedrive app, and have never had an issue.

[free780]

Becomes an issue with 3rd party software such as Adobe etc where staff/students need to store files.

 

The Machine level installer keeps up to date via scheduled task rather than only updating in the user context. I think I did script the download of the latest installer to SCCM. The deployed is as part of the TS.

 

The largest issue is getting staff/students to realise they need to let their files sync on logoff.

[craigcamacho]

Figured it out in the end.

 

Created an application in SCCM using OneDriveSetup.exe /AllUsers and deployed

Created a package and deployed the below Powershell script using a command of "%Windir%\sysnative\WindowsPowerShell\v1.0\powershell.exe" -ExecutionPolicy Bypass -Command .\RemoveDefaultOneDrive.ps1

 

https://byteben.com/bb/installing-the-onedrive-sync-client-in-per-machine-mode-during-your-task-sequence-for-a-lightening-fast-first-logon-experience/

 

#Create PSDrive for HKU

New-PSDrive -PSProvider Registry -Name HKUDefaultHive -Root HKEY_USERS

 

#Load Default User Hive

Reg Load "HKU\DefaultHive" "C:\Users\Default\NTUser.dat"

 

#Set OneDriveSetup Variable

$OneDriveSetup = Get-ItemProperty "HKUDefaultHive:\DefaultHive\Software\Microsoft\Windows\CurrentVersion\Run" | Select -ExpandProperty "OneDriveSetup"

 

#If Variable returns True, remove the OneDriveSetup Value

If ($OneDriveSetup) { Remove-ItemProperty -Path "HKUDefaultHive:\DefaultHive\Software\Microsoft\Windows\CurrentVersion\Run" -Name "OneDriveSetup" }

 

#Unload Hive

Reg Unload "HKU\DefaultHive"

 

#Remove PSDrive HKUDefaultHive

Remove-PSDrive "HKUDefaultHive"

 

In my OneDrive GPO I had to modify the regs below under User Preferences which fixed the keys for users who had already previously logged into a machine and ran the baked in OneDrive from AppData rather than Program Files

 

HKCU\Software\Microsoft\OneDrive\OneDriveTrigger to C:\Program Files\Microsoft OneDrive\OneDrive.exe

HKCU\Software\Microsoft\OneDrive\SilentBusinessConfigCompleted to 00000000