The current OneDriveSetup spawns numerous processes in the user context even when initiated using a trusted installer like SCCM. This includes, command prompts, icacls granting read rights to the security service and random powershell. For companies using products to prevent standard users executing unknown software or commandline tools this gives a **** of a management headache! Can we tie the spawning processes into the original calling process rather than running as the currently logged on user please?