VB.net Dim objNetwork, objFSO, objShell Dim strDriveLetter, strRemotePath, strUserName, skipUserDrive Dim strDriveLetter1, strRemotePath1, strDriveLetter2, strRemotePath2, strDriveLetter3, strRemotePath3, strDriveLetter4, strRemotePath4, strDriveLetter5, strRemotePath5 Set objShell = WScript. I tried running the following command to disable this feature: I read in another thread that the drives might be auto-disconnecting. Even with the change the drives still disappear. The login script used to only point to \\our-file-svr\users\%username% but after reading that, I tried changing to \\\users\%username% with no success. I read somewhere that with recent updates, Windows 10 now requires FQDN names instead of just the server name. Even when mapped as something else, they still disappear, so we can rule out the letter being the issue. We've mapped these drives as different letters. We've already tried just about everything we can think of. It's strange though, because none of the other mapped drives are disappearing, only U:\ We've confirmed the issue exists on multiple users' PCs. After a short amount of time of using their computers, users have notified us that their U:\ drive is disappearing. We have a login script (VBS file) that runs whenever a user logs into Windows that will automatically map this as well as several other network locations. Each user gets their own "user drive" mapped as U:\ which points to \\\users\%username% We've started migrating all of our users to Windows 10, and we're running into a problem with mapped network drives.
Here's a strange one, hopefully someone has encountered something similar and has a solution.
0 kommentar(er)
