0

Recently I've started to migrate a domain from Windows Server 2003 (mapping drives by script) to a Samba 4 DC (mapping drives by GPO). Most of the computers work fine, but on some of them I've noticed that some drives are not showing in Windows Explorer and, after some research I've noticed this:

  • The drives that aren't showing are not always the same drives, it happens randomly and sometimes all the drives are OK
  • The drives are always mounted. If I use the command net use on cmd it shows all the drives.
  • To mount the drive I've to unmount the old first using cmd, and then mount the drive again. After this the drive shows up in explorer.
  • There is not local drive with the same letter so is not a conflict
  • The GPO info shows that all the GPO are applied without problem

I've also checked that there's no registry entry to hide the drive and also I've changed the option to show the drive on drive policy, but nothing worked.

I'm using Windows 10 and I think that I also had this problem in a Windows 7 computer.

Did anyone have similar problems?

3
  • I experience this all the time on Windows 10, especially if I am using "use other credentials" across multiple PCs, different clients. I am yet to find a solution, so I shall favorite this question ;) – DankyNanky Oct 2 '17 at 13:47
  • What "Action" have you got set? Create, Update? technet.microsoft.com/en-us/library/cc770902(v=ws.11).aspx – HelpingHand Oct 3 '17 at 21:00
  • The action I use is update. With this action the client should create the drive if not exists... and that's OK, the client create that drives and are showed on command line, but the Windows Explorer fails and don't show some of that drives. It only happens on some clients and I think that all are using Windows 10. – Daniel Carrasco Marín Oct 4 '17 at 8:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.