Drive Mapping not appying/charging

[newpersn]

Hello,

 

Weird one here. We have just replaced our Sims server and its got a new name.  (We map the S drive to Sims server)

 

We have updated group policy for it to update/replace and its not applying automatically. (Both DC's are fine and replicating without any issues) - Even created a new policy with just that drive map and its still not working. 

 

When we force a client pc to update it will apply the network drive but wont apply when they log on. 

 

Is there something missing somewhere?

 

Thanks 

Newp

[Frodo_Baggins]

gpresult is your friend assuming there are no events relating to file serving\sharing on the SIMS server

[PotNoodleTech]

Check if the GPO optional setting

 

"Apply once and do not reapply"   Is set or not in the additional properties on the drive map?

 

[newpersn]

 

Nothing extra is set via GP. 

 

Nothing jumping out when gpresult - All looks corrects on the computer i just tested with. 

[psydii]

Maybe related to the Action? Create/Update/Replace/Delete?  Try Update or Replace? Been ages since I double checked what those action labels actually really really do though, so test carefully

[Koldov]

1 hour ago, newpersn said:

We have updated group policy for it to update/replace and its not applying automatically.

 

Are you using GPP in your user GPO for the drive mapping (as iirc 'update' and 'replace' are two different settings and do slightly different things)?

 

I remember having some difficulty doing something similar with printer mappings when I changed our print server. From what I read I should just have been able to choose update or replace (can't remember which now), but for some reason it never seemed to work, or I got 2 (the old AND the new). In the end I put a delete (apply once) to apply first (higher order) and then a create. YMMV but this way you could see on a test machine in a separate policy test OU, if once the old S: drive has been deleted the new one applies.

 

I've also had it where a setting was being overridden by a setting in another policy, so best if your test OU is completely clean.

 

Strange that it seems to work if you force the gpupdate, so maybe for some reason the drive maps are taking a little longer than the log on (network issues/slow NIC on startup, other GPOs applying - do you have a wait for network GPO applied)? What about multiple log on/off attempts on an already booted machine, does it kick in then?

Edited April 30, 2025 by Koldov

[psydii]

There was a reason years ago that it wasn't uncommon to have a script un-map all network drives at log off.

 

Thinking sideways for a moment... do you really need an S drive? What if the connect.ini just pointed to the share?

[Koldov]

Good shout!

 

I remember taking the plunge and removing the S: drive mapping a couple of years ago and used the connect.ini, SIMS definitely still worked.

 

EDIT: I did need to arrange alternative mappings for one or two staff members (in finance and admissions) that still needed access to sub folders on the share, though for the majority of users it was fine.

Edited April 30, 2025 by Koldov

[PotNoodleTech]

SIMS does need access to the S drive for quite a few things stored in the subfolders.  I used to map mine and hide it in the HPO settings so the users couldnt see/navigate the S Drive

[Fazza]

Are you still using the old SIMS server?  If not then in the short term you could add a DNS entry with the old server name and the new IP address so the old S: drive mapping will still work but it will be on the new server/share.

[psydii]

Kerberos would like a word.

[mikes]

all I can think would be the old share still applying / not having removed properly - if you have a test gpo can you use a drive letter you haven't used before just as a test?

We also changed our sims ini  to go directly to the UNC path not the share (or even I might have set it to have the DB details directly?)  as we had so many problems with drive maps back then (thanks to RM CC4 earlier on, then later with DirectAccess or machines resuming from sleep having red X's) - and it fixed all our SIMS problems - only a2c seemed to actually need the drive map

[newpersn]

Ok - Mini update, New users logging on to the computer S drive will map fine. 

Users that have already been logged on to - Wont map. Until gpupdate /force is ran, and its fine until the next time the users logged in. 

I have added a delete "S drive" in the drive mappings in first and map S drive in second. 

 

I am tempted to change the connect.ini to point to UNC until i wipe computers.