Shared Folder Drive Letter Assignment in V6 (again)
Posted: 6. Mar 2019, 22:14
Followed the discussions regarding the assignment of drive letters to network shares. If I have understood correctly, VB does not assign drive letters to shared folders, the Windows Guest makes those assignments.
Well, something changed! Just upgraded from 5.2.26 to 6.0.4. I have a several guest machines running Win XP, Win 7, Win 8 and Win 10. All use the same Shared Folder and the Auto Mount option is checked in the machine settings. Through versions 2, 3, 4 and 5 of VB, Windows, regardless of version, has always mapped this folder as drive E.
After the upgrade, these same VB machines now map the drive to the letter Z.
I found the posts that discuss not using Auto Mount, and mapping the drives within the guests themselves to the desired drive letter, but have had problems, which I believe are related to the shared folder having a space in its name. I don't have an urgent requirement to map shared folders to specific drive letters, but I do like consistency.
Since the Windows guest machines didn't change (no recent updates applied), it seems to me VB changed something that causes the guest to choose the last drive letter available, instead of the first open drive letter.
I'd like to not have to change from auto mount to drive mapping on 15 or so guests.
Anyone have any idea what happened, and is there a setting that can be changed? Until the, I reverted back to 5.2.26.
O.N.
Well, something changed! Just upgraded from 5.2.26 to 6.0.4. I have a several guest machines running Win XP, Win 7, Win 8 and Win 10. All use the same Shared Folder and the Auto Mount option is checked in the machine settings. Through versions 2, 3, 4 and 5 of VB, Windows, regardless of version, has always mapped this folder as drive E.
After the upgrade, these same VB machines now map the drive to the letter Z.
I found the posts that discuss not using Auto Mount, and mapping the drives within the guests themselves to the desired drive letter, but have had problems, which I believe are related to the shared folder having a space in its name. I don't have an urgent requirement to map shared folders to specific drive letters, but I do like consistency.
Since the Windows guest machines didn't change (no recent updates applied), it seems to me VB changed something that causes the guest to choose the last drive letter available, instead of the first open drive letter.
I'd like to not have to change from auto mount to drive mapping on 15 or so guests.
Anyone have any idea what happened, and is there a setting that can be changed? Until the, I reverted back to 5.2.26.
O.N.