![]() Using the script with ConfigMgr is straightforward. ![]() Notice the desired location in %programfiles(x86)%. This is how it looks prior to the installation in my end:Īnd below illustration is OneDrive after the installation. This is the familiar scenario where OneDrive is installed in the users profile. Needless to say, using the -NoSourceFiles parameter downloads the OneDriveSetup.exe directly from Microsoft and stores it into Windows\Temp from where it also is installed. The script basically comes with 2 options: Install with or without source files using the parameter -NoSourceFiles or -SourceFiles The magic lies in the Powershell script found in the very end of the post. Credit where due: I was inspired by Per Larsen’s post on doing the same with Microsoft Intune and like many times before, this brought me to doing something on my own for the sharing and learning experience. The option is currently in preview and all the juicy details are found here: Now, Microsoft has finally given us an option, allowing us to install OneDrive for the device into %programfiles(x86)%. OneDrive in it’s current state in the production ring, is installing into the users profile in %localappdata%, and for equally good reasons that is often not desired by enterprises. Installing the OneDrive for Business client on a per machine basis is an often requested feature and for good reasons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |