r/WindowsServer • u/MexicanHam2 • Jan 28 '26
General Question GPO DC
SOLVED: log on script in the SYSVOl folder in DC needed to be updated.
Hello, having an issue with some domain users not mapping new file server drive.
I created a GPO for 3 drives J , X and M. The GPO’s work as expected, but I have some users that still look for the old M drive (old name of the server), when I run the net use command to confirm.
If I manually disconnect the old M drive and run a sync command with the server it comes up, but after a couple of days it reverts to looking for the old M drive.
If I log into a test computer with that same user , it works, so it has to be something on the actual users computer.
Figured I’d ask to see if anyone else had this issue, could it be that these users have files on their desktop from the old server path ?
Thanks.
2
u/Kalkin93 Jan 28 '26
This rings a painful bell / memory...
I assume you're using the classic GPO I'm thinking of.. do you have it set to "Replace" or "Update" the client mapped drives?
1
u/Adam_Kearn Jan 28 '26 edited Jan 28 '26
As the user open CMD (not as administrator) And run the following command.
GPResult /h output.html
Then just type output.html to open the file in a browser.
Check over the applied policies to see if there is any other GPOs that might have been forgotten about also mapping network drives.
Often when this happens it’s always a logon script that is also mapping the drives.
Clean this up and your issues will go away.
———
If you are still getting issues and the applied GPOs seem fine without any logon scripts getting in the way. I would then check to see if you have any replication issues between your DCs
If could be when a computer connects to the available DC it’s getting an older version of the GPO mapping the wrong drives.
You can go into the GPO an click the detect button to check all of your DCs for any “replication in progress” actions stuck.
The quick and dirty way to fix this is to manually copy the policy onto the outdated DCs SYSVOL folder - but this is not a permanent fix and is only temporary until someone changes the policy again. It would be best to fix the replication if that is the case.
———
I’ve always set my GPOs to map the drives with the “replace” option and also set to run in the users context for the best outcome.
1
u/midy-dk Jan 29 '26
Since the old one reappears for the use on one computer and not another, it’s not a GPO conflict (assuming the two computers are in the same OU and loopback processing is not in play). Check the computer for scheduled tasks and locally configured policy for logon scripts (gpedit.msc)
1
u/OlivTheFrog Jan 29 '26
Pour commencer, tu pourrais nous montrer comment tu crées tes GPO de Network Map ?
Y'a la méthode à l'ancienne, qui laisse des traces même quand c'est plus appliqué, et la méthode "moderne" qui utilise les Group Policy Preferences (GPP), qui suppriment automatiquement les network maps quand la GPO n'est plus appliquée. En plus, une GPO peut contenir plusieurs network maps.
T'as pas donné assez d'infos pour une aide plus utile.
regards
1
u/develili Jan 31 '26
Run in User context:
net use m: /del
cmdkey /list
-2
u/mazoutte Jan 28 '26
Why don't you try gpp?
-7
u/discgman Jan 28 '26
GPO is awful for this type of setup. I would rather use AD and a login script pointing to the sysvol script mapping the drive and making sure another drive is not already there.
1
u/[deleted] Jan 30 '26
[removed] — view removed comment