We have an issue with X drive mapping on windows 10 machines. As windows 7 shared drive locations are not migrated to windows 10 yet, we are still using to connect the shared drives using windows 7 credentials on windows 10.
Below is the issue description:
We have mapped the X drive with On-premise domain Credentials using the "reconnect at sign-in and remember my credentials option" on windows 10 machines. (For your information: On-premise domain ID uses in windows 7 machines & Azure domain uses in windows 10). it mapped successfully and shows all the folders correctly under L drive. To ensure whether we have mapped with the correct domain ID, crossed check by using the command line - Get-WmiObject -class win32_networkconnection | select -property * in powershell . the result shows the CORRECT value(i.e., As we have mapped X drive with On-premise ID, the Username value assigned to, On-premise domain\USERID).
To double check, we have also verified the registry value under HKEY_CURRENT_USER\Network\X, the username has the correct DOMAIN ID. i.e., On premise domain ID
After restart the machine & logged with Azure domain ID on windows 10, I could still see that map drive is connected but few folders are missing on it. To double check whether the map drive is still connected with On-premised ID, ran the same command line "Get-WmiObject -class win32_networkconnection | select -property * " in powershell, i see that Username value is assigned to Azure domain account but NOT on-Premise ID.
Could you please suggest what could be the issue and how can we fix this permanently?