Allow Drive Mappings Using Letters A, B, and C

At this time, it is not possible to create drive mappings using the drive letters A, B, or C. While I understand this restriction may be in place due to historical conventions or system-level reservations, I believe the application should not enforce this limitation by default.

By preventing users from selecting these letters, Application Workspace imposes an unnecessary limitation that forces administrators to work around the issue using custom PowerShell scripts, even though a dedicated "Add Drive Mapping" action already exists within the product.