How to Retire Home Drives After OneDrive Migration

After migrating user files from traditional home drives to OneDrive, many organizations keep the old home drives active out of caution. This wastes server storage, complicates backup policies, and can confuse users who see two copies of their files. The primary reason home drives linger is the fear of accidental data loss or broken application shortcuts. This article explains how to safely retire home drives after confirming that OneDrive sync is complete and all critical data has been transferred.

Why Home Drives Persist After OneDrive Migration

Home drives, also known as H: drives or user profile shares, are network locations that store user files on a central server. When an organization migrates to OneDrive, users begin saving files to the cloud instead of the network share. However, several factors keep the old home drives active:

Application Dependencies

Many legacy line-of-business applications reference files using hard-coded UNC paths or mapped drive letters. If these applications still point to the old home drive, retiring it prematurely will break the software. You must identify and update application configurations before removing the share.

User Behavior

Users may continue saving new files to the home drive out of habit or because their default save location was never updated. A simple migration does not change the default save path in many desktop applications. You must redirect the known folders using Group Policy and communicate the change clearly.

IT Compliance Requirements

Some organizations have retention policies that require keeping user data for a specific period after migration. Retiring the home drive immediately could violate legal or audit requirements. A phased approach with a read-only period satisfies most compliance needs.

Steps to Retire Home Drives After OneDrive Migration

Follow these steps in order to retire home drives without losing data or breaking applications. Each step assumes you have already migrated user files to OneDrive using the Known Folder Move feature or a manual copy process.

Step 1: Verify OneDrive Sync Completeness

1. Check sync status on each user device
   Open OneDrive from the system tray. Confirm that all files under Documents, Desktop, and Pictures show a green checkmark. If any files show a red X or a sync pending icon, resolve those conflicts before proceeding.
2. Run the OneDrive sync health report in the admin center
   Go to Microsoft 365 admin center > Reports > Usage > OneDrive. Look for devices with sync errors. Address any devices that have not synced in the last 30 days.
3. Compare file counts between home drive and OneDrive
   Use a PowerShell script to count files in the old home drive folder and the corresponding OneDrive folder. The counts should match within 1 percent. Any significant discrepancy indicates missed files.

Step 2: Redirect Known Folders via Group Policy

1. Open Group Policy Management Console
   On a domain controller or management workstation, open the Group Policy Management Console. Create a new GPO named “OneDrive Known Folder Redirection” or edit an existing one.
2. Navigate to the Folder Redirection policy
   Go to User Configuration > Policies > Windows Settings > Folder Redirection. Right-click each folder (Documents, Desktop, Pictures) and select Properties.
3. Set the redirection to OneDrive
   Choose the setting “Redirect to the user’s local profile” and then select “Redirect to the user’s OneDrive folder.” Enter the path %OneDriveCommercial% for each folder. Apply the policy to all migrated users.
4. Force a Group Policy update
   On each user device, run gpupdate /force from an elevated command prompt. Verify that the known folders now point to the OneDrive location by right-clicking the folder and checking Properties > Location.

Step 3: Set the Home Drive to Read-Only

1. Remove write permissions on the share
   On the file server hosting the home drives, open the share properties. Remove the “Change” permission for the Users group. Keep only “Read” permission. This prevents new files from being saved to the home drive.
2. Create a notification file in the share root
   Place a text file named HOME_DRIVE_READ_ONLY.txt in the root of each home drive share. Include instructions telling users to save files to OneDrive instead. This reduces support calls.
3. Monitor for access attempts for 30 days
   Enable file server auditing to log any write attempts to the home drive shares. Review logs weekly. If users attempt to save new files, contact them and redirect to OneDrive.

Step 4: Retire the Home Drive Share

1. Back up the home drive data one final time
   Use Windows Server Backup or a third-party tool to create a final backup of all home drive shares. Store this backup for at least 90 days in case of data retrieval requests.
2. Remove the share from the file server
   Open Server Manager on the file server. Go to File and Storage Services > Shares. Right-click each home drive share and select Remove. Confirm the removal.
3. Delete the mapped drive GPO or logon script
   If you use Group Policy to map the H: drive, remove the Drive Maps policy. If you use a logon script, remove the net use H: line. Run a final gpupdate /force on all user devices.
4. Communicate the retirement to users
   Send an email to all affected users stating that the home drive is no longer available. Include links to OneDrive sync troubleshooting guides and a contact for data retrieval requests.

Common Issues When Retiring Home Drives

Users Still See the Old Home Drive in File Explorer

If users still see the H: drive after you remove the share, the drive letter may be cached in the registry. Run net use H: /delete on each device, or push a PowerShell script through Group Policy that removes the mapped drive. For persistent cases, delete the registry key HKEY_CURRENT_USER\Network\H using a startup script.

Applications Fail Because They Reference the Old UNC Path

Before retiring the home drive, use a network monitoring tool to identify which applications still call the old UNC path. Update the application configuration to point to the OneDrive sync path, typically C:\Users\%username%\OneDrive - YourTenantName. If an application cannot be updated, create a symbolic link on each device that maps the old UNC path to the new OneDrive location.

OneDrive Sync Fails After Home Drive Removal

Some users may have files that were saved to the home drive after the initial migration. When the share is removed, OneDrive may detect missing files and show sync errors. Run the OneDrive sync troubleshooter on affected devices. If files are permanently missing, restore them from the final backup you created in Step 4.

Home Drive vs OneDrive: Key Differences After Migration

Item	Home Drive (H:)	OneDrive
Storage location	On-premises file server	Microsoft 365 cloud
Access method	Mapped network drive	Sync client or web browser
Offline availability	Requires offline files feature	Files On-Demand with local cache
File version history	Requires Volume Shadow Copy	Up to 500 versions per file
Collaboration	Single-user access	Real-time co-authoring
Backup	Server-based backup policy	Built-in recycle bin and retention

After migration, OneDrive provides superior versioning, collaboration, and offline access. The home drive becomes redundant and can be safely retired once the steps above are completed.

You can now retire home drives with confidence by following the phased approach of verification, redirection, read-only period, and final share removal. Next, consider enabling OneDrive Known Folder Move for new users to prevent home drive creation entirely. An advanced tip: use PowerShell to generate a migration report that compares file counts between the home drive and OneDrive before and after the read-only period, giving you a data-driven green light to remove the share.