none
Home drive mapping fails when using group policy preferences to map other drives

    Question

  • Hi folks,

    Discovered a peculiar issue today.

    We have a user who has a home drive defined in the U: drive in Active Directory.

    The location is on a DFS server.

    When the user has group policy preferences assigned to map some other drives (to different letters), the U drive no longer maps (The other drives map successfully).

    When the group policy preferences for drive maps are removed, the U drive returns.

    The machines are Windows 7 SP1. UAC is enabled on the machines, the user is NOT local administrator of the machines.

    Update:

    If a user is made administrator of the machine, all drives map correctly.

    If UAC is switched off, user not local admin, the U drive still does not map, just the other drives. So seems not to be UAC related.

    Machine logs event ID 1112 relating to the Drive Maps CSE, but "Always wait for network at startup and logon" is enabled on the computer.

    Any ideas what might be the issue?

    Suggestions welcome.

    thank you.






    • Edited by IUSR345369 Thursday, February 12, 2015 8:44 AM
    Wednesday, February 11, 2015 9:55 PM

Answers

  • Hi Martin,

    So, after running a logon trace (very handy!) I found the root cause.

    And yes, like your first reply stated, the issue was with Prefs settings..

    The issue was that the admin who had implemented the (item level targeting) setting for one of the drive mappings, had selected the Drive Letter option "Use first available, starting at" option, instead of assigning a drive letter.. when this was set to a Letter, the AD home drive now maps.

    Why Windows did not simply assign an unused drive letter A,B, or T (the next available letter after the departmental drives), and why it worked when the user was assigned local admin rights, I have no idea, and is what threw me when troubleshooting initially.

    Anyway, Im delighted to have the answer, its Friday :)

    Thanks!

    Friday, February 13, 2015 4:21 PM

All replies

  • > When the group policy preferences for drive maps are removed, the U
    > drive returns.
     
    Then double and triple check through GPresult /h report.html - which
    drives and which actions are processed and performed through GPP?
     

    Martin

    Mal ein GUTES Buch über GPOs lesen?

    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))
    Thursday, February 12, 2015 1:40 PM
  • Hi Martin,

    I initially thought the same thing - however when the user is made local admin it all works fine?

    In addition, I can reproduce the issue on a user who is running no logon script. Mapping 4 drives via GPP, and expecting the 5th to be the home drive via AD. But only the 4 via GPP map, unless user is local admin, then I get the 5th (U) drive.

    Any ideas?


    • Edited by IUSR345369 Thursday, February 12, 2015 1:52 PM
    Thursday, February 12, 2015 1:51 PM
  • > drive via AD. But only the 4 via GPP map, unless user is local admin,
    > then I get the 5th (U) drive.
     
    Hm. Did you "play around" with local GP settings? You can implement
    different local GP settings for Admins and Non-Admins, and this
    phenomenom seems like the Non-Admins get a (local) logon script that
    disconnects the homedrive.
     
    If in doubt, run process monitor and grab a logon trace. Check which UNC
    paths appear and disappear :)
     

    Martin

    Mal ein GUTES Buch über GPOs lesen?

    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))
    Friday, February 13, 2015 11:04 AM
  • Hi Martin,

    So, after running a logon trace (very handy!) I found the root cause.

    And yes, like your first reply stated, the issue was with Prefs settings..

    The issue was that the admin who had implemented the (item level targeting) setting for one of the drive mappings, had selected the Drive Letter option "Use first available, starting at" option, instead of assigning a drive letter.. when this was set to a Letter, the AD home drive now maps.

    Why Windows did not simply assign an unused drive letter A,B, or T (the next available letter after the departmental drives), and why it worked when the user was assigned local admin rights, I have no idea, and is what threw me when troubleshooting initially.

    Anyway, Im delighted to have the answer, its Friday :)

    Thanks!

    Friday, February 13, 2015 4:21 PM