Migrating H:\ drives to OneDrive any gotchas concerning existing redirect policies?

[kennysarmy]

As the title : "Migrating H:\ drives to OneDrive any gotchas concerning existing redirect policies?"

 

Our users have redirected Documents as per the below:

 

 

I'm just worried after reading some things online about how this policy needs to be reversed and each user logon to each PC to pull down new settings before a migration???

 

 

 

Surely this is not necessary?

 

Any help appreciated.

[kennysarmy]

The lower part of this document seems to suggest it's not an issue:

https://learn.microsoft.com/en-us/sharepoint/redirect-known-folders#about-the-known-folder-move-group-policy-objects

 

[supportman]

I just did this a while back and had no issues, works quite well and nice to not have mapped drives anymore.

[Oaktech]

I had to reverse the policy on my setup before it would pick up the OneDrive policy. With one just removed it was first past the post as to whether you got no redirection or OneDrive.

[altecsole]

We did this last summer, but quickly changed back to having a H: drive, for the following reasons:

 

1. Problems on some computers with automatic sign-in to OneDrive, in particular on Windows 11. This left some users with the default save location set to the local hard drive.

2. We wanted to keep user Downloads on a server so that we can continue to use FSRM to block attempted downloads of things we don't want.

 

Even though we do have a user H: drive, we use hard quotas with a limit of 300 MB for students. This includes their Downloads folder. This encourages them to use their OneDrive as their main storage location. They understand that if they download something, and want to keep it, they must move it over to their OneDrive (which is available in Explorer). If they don't, they hit their quota and are then forced to tidy up. The Default save location is user's H: drive.

 

In preparation for this setup, we used the SharePoint Migration tool to copy user home folders to a 'Migration' folder within their OneDrive. We then renamed the root share to prevent any further access to these files. We did keep them on our server for a couple of months, but no one complained about missing files, so we went ahead and deleted them. Freed up a lot of local storage.

[kennysarmy]

Thanks for the replies so far.