Mapped Home Drives - Mapped Home Drives - OnBase - Desktop and Application Virtualization Guide - OnBase/Desktop-and-Application-Virtualization-Guide/English/Foundation-22.1/Desktop-and-Application-Virtualization-Guide/Installation-and-Configuration/File-Storage-Locations/Mapped-Home-Drives - English - Foundation 22.1

Desktop and Application Virtualization Guide

Platform
OnBase
Product
Desktop and Application Virtualization Guide
Release
Foundation 22.1
License
Premier
Standard
Essential
ft:lastPublication
2026-02-19T14:20:05.165000
ft:locale
en-US

It is considered a best practice to assign users a mapped home drive rather than using mapped or re-mapped local drives for file storage external to OnBase. A mapped home drive provides the following advantages:

  • Sensitive information can be securely stored in user-specific locations.

  • Files stored in user-specific locations can be identified by OnBase as unique to specific users.

  • Files are accessible to users, regardless of the server to which they connect.

  • Files that save user-specified settings are stored in user-specific locations, allowing users to maintain their customizations.

Note:

The example mapped home drive used in this guide is represented as the Y: drive. Mapped home drives do not require this letter to be used, but users' mapped home drives must always share the same letter.

OnBase using mapped home drives can be represented by the following example:

Diagram depicting 4 people with arrows pointing to a server with 4 entries to the "Y:\" drive. This represents 4 different users accessing mapped home drives to a shared server.

Configuring each user's mapped home drive to use the same letter allows the Remote Desktop Server to reference the same directory, yet access a user-specific location. OnBase can be configured to use the specified drive letter instead of C: as the default location for external file storage, ensuring proper functionality in the virtualization environment.

Note:

For information on configuring mapped home drives, see Microsoft Windows documentation.