Announcement

Collapse
No announcement yet.

Mapping Home Directory (Profile vs Script)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mapping Home Directory (Profile vs Script)

    I've ran into a weired issue recently. I'll run down the history quickly for you. It seems like there's an easy fix, but I just can't figure it out. If this problems needs to be moved to the scripting directory, please move if necessary.

    About a month ago we did a file server migration from one server to another. This file server was the location for the users "home" directory. The UNC path is \\server\home\%username%\private-data\.

    If a user wants to share a file on the network for others to see, they store the file in the %username% folder. If they want to keep the file private, they store in the private data folder.

    In our script, we have 2 lines in question. This script is stored on our domain controllers in the Netlogon share and is assigned to the Profile tab for each user that makes use of the script.

    net use P: \\server\home This maps the users to the public directory.
    net use W: /home This maps the user to their private-data.

    However, while performing the server migration, I noticed that the users had a their home folder set on the Profile tab of the profile. Which was \\server\home\%username%\private-data\ and was also set to the drive letter W.

    Now, I didn't notice an issue until myself and the other network administrator got new laptops. We have also seen this issue on various other computers throughout the network, which were also new computers.

    However, when we logon our W drive is mapped to \\server\home, when it should be \\server\home\%username%\private-data\.

    Since the time of seeing this, I have removed the net use W: /home from the script. After doing this and logging in for the first time, I get no W drive at all. Which means it's not even finding my profile on the domain. For kicks, I plugged into a wired LAN line and recieved the same results to ensure that it was not using a cached version of my profile.

    I have verified that all permissions are exactly the same as they were on the old server.

    Any help would be appreciated. If you need more info, please let me know.
    MCITP:SA, MCSA 2003, MCP, CCNA, A+, Net+, Security+

  • #2
    Re: Mapping Home Directory (Profile vs Script)

    Is there anything in the script that deletes the drive mappings ?
    Guy Teverovsky
    "Smith & Wesson - the original point and click interface"

    Comment


    • #3
      Re: Mapping Home Directory (Profile vs Script)

      Yes. I have all of the drives being deleted before they are mapped again with net use driveletter /delete.
      MCITP:SA, MCSA 2003, MCP, CCNA, A+, Net+, Security+

      Comment


      • #4
        Re: Mapping Home Directory (Profile vs Script)

        It's quite simple:

        1) User logs on
        2) User's home folder is mapped to W from the properties in AD
        3) Logon script deletes all the drive mappings (including W)
        4) You get no mapping to W after you log on

        Exclude deletion of W drive mapping in logon script and you'll get your W back mapped from AD properties.
        Guy Teverovsky
        "Smith & Wesson - the original point and click interface"

        Comment


        • #5
          Re: Mapping Home Directory (Profile vs Script)

          That did it. I removed all references to the W drive in the script and it mapped the AD home directory perfectly. That was so easy to fix. Thanks for pointing that out. So here's to you....
          MCITP:SA, MCSA 2003, MCP, CCNA, A+, Net+, Security+

          Comment

          Working...
          X