Bankesy Posted February 13, 2025 Posted February 13, 2025 Good afternoon, Probably not strictly a Windows 10 query but seeing an issue on one PC where regardless of user, a particular network drive does not get mapped at logon. I've tried looking in Event Viewer but not really sure what I would be looking for in terms of an error, it doesn't help that I'm not overly familiar with how the drives get mapped as I inherited but think it is a logon script by GPO. Does anybody have any suggestions? I did wonder if it was a networking-level thing, switch port config etc. Thanks
LeMarchand Posted February 13, 2025 Posted February 13, 2025 Is something else using the drive letter? 1
altecsole Posted February 13, 2025 Posted February 13, 2025 Check which OU the computer is in and then check what group policies are being applied - it may have been moved to a testing OU. Our drive mapping is done as a User GP Preference - Windows Settings - Drive Maps, so check if this is set. Mapping as a logon script may be a possibility, if so, try running the script as the logged in user, to test. 1
JRA Posted February 13, 2025 Posted February 13, 2025 (edited) If it's not a script have a dig into the policy/policies, wherever you discover them to be. Could be some item-level targeting options. Edited February 13, 2025 by JRA 1
PotNoodleTech Posted February 13, 2025 Posted February 13, 2025 Is something else using the drive letter? yeh check Disk Manager - could be something alreayd using the drive letter especially if it's the low end E - L 1
Oaktech Posted February 14, 2025 Posted February 14, 2025 Can you try mapping it manually? might give you an in-your-face error rather than something silent and stashed away in event logs. 1
Davit2005 Posted February 14, 2025 Posted February 14, 2025 I have seen a issue with SMB before caused by a switch fault. Worth looking at as a quick fix/test and switch to a known working port. 1
mikes Posted February 17, 2025 Posted February 17, 2025 User def has permissions? a manual map should show that 1
2097 Posted February 27, 2025 Posted February 27, 2025 Try assigning a network path to the same drive letter in CMD prompt and see if its in Use. If it is remove said mapping and then logoff and back on and see if it maps correctly
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now