Follow

Using OneDrive with ProfileUnity

Product: ProfileUnity-FlexApp

Product Version: 6.x

Expires on: 365 days from publish date

Updated: June 22, 2020

 

NOTE:  This Configuration assumes that your systems already have OneDrive installed using the /allusers machine-wide option.

Updates:

6/22/2010 - Now hides the O: drive

Description:

When RDSH or multi-session Windows 10 is detected, we use the user's profile path for OneDrive sync location. This isn't ideal since it may be non-persistent or it may bloat the ProfileDisk.

When a non-RDSH machine is detected, we will create a VHD(x), mount it to O:\ and force the sync location there. This keeps from bloating the user's profile and keeps sync'd files on-disk for non-persistent machines.

To force the sync path to the user's profile instead of using O:\, disable the Virtual Disk Registry rules that use the "Non-RDSH" filter that force the sync path to O:\.  (Maybe for persistent machines)

Instructions:

Download the "OneDrive - Windows 10, 2016, 2019.json" located at the bottom of the page locally and import it into the ProfileUnity web console.

  1. Open the ProfileUnity console
  2. Go to configuration management
  3. Select Import

import.png

Once imported, change the relevant paths for the virtual disk as appropriate for your environment as well as review the registry module in the template for drive letter assignments.

The template contains two variables; {profileshare} and {TenantID}.  You must add these variables into the Global Variables section of the Admin screen and click Update.  (Leave off the {brackets} when entering the variable name in the Admin screen)

{profileshare} refers to the network share where user profiles are located; modify accordingly.

{TenantID} refers to the Office 365 Tenant ID for your company. If the ID is unknown, it can easily be determined by going to the URL below, changing "yourcompany" accordingly. The alphanumeric string shown in the "authorization_endpoint" entry is the Tenant ID for your company.

https://login.windows.net/yourcompany.onmicrosoft.com/.well-known/openid-configuration 

Finally, deploy the ini to "NETLOGON\ProfileUnity" or the respective deployment share for your environment.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.