Where did this drive mapping come from?

[ra8888]

I am administering a native NT 4.0 environment with roaming profiles implemeted.&nbsp;&nbsp;I have one user who, for some reason, gets an F: mapped when he should only have a g:.&nbsp;&nbsp;It happens intermittently.&nbsp;&nbsp;any ideas?<br><br><br>

 

[DougP]

What is it connected to ie<br>\\ComputerName\ShareName<br><br>Then see which programs they launch<br>Something is restoring the bogus &quot;F:&quot; when it runs<br><br>

 

[pmkincaid]

Do both F: and G: get restored?&nbsp;&nbsp;Is F: being mapped to where G: is supposed to get mapped?<br><br>Check the user's Registry for any Run, RunService, RunOnce, etc for anything that may be mapping it.<br><br>Does this happen if the user logs into a different machine on the network?&nbsp;&nbsp;How about if someone else or an administrator logs in to the questionable machine?<br><br>Hope this helps,<br>Paul Kincaid

 

[Lehtoant]

There's a discussion of mapping problems in:<br>Top &gt; Desktop Software &gt; PC Operating Systems &gt; Microsoft: NT Workstation Forum<br>Drive Mappings Ghosting<br><br><A HREF="

http://www.tek-tips.com/gviewthread.cfm/lev2/67/lev3/70/pid/621/qid/6434"

TARGET="_new">

http://www.tek-tips.com/gviewthread.cfm/lev2/67/lev3/70/pid/621/qid/6434</A><br><br>Check

this for help.<br><br>Al