Announcement

Collapse
No announcement yet.

Drive mappings are not mapping correctly.

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

  • Drive mappings are not mapping correctly.

    This is the second time this has happened. The first time, as each user logged into the TS, all their drive mappings (as defined in their AD login script, were mapped to ONE drive, being the first drive mapping (G-Drive).

    This time, none of my users can access their U-drive (Home drive) as it is being mapped to the G-drive (somehow!?).

    The last time this happened we had to restart the TS but I don't want to have to do this each time so I need to ask how this is happening, why and how to fix it.

    Here's more info:

    Login Script:
    net use g: \\jlrx01\jldata
    net use h: \\jlrx01\actdata
    net use i: \\jlrx01\buildsoftjobs
    :net use j: \\jlrx02\jlawestdata
    net use k: \\jlrx01\archives
    net use l: \\jlrx01\digital_dictation
    net use m: \\jlrx01\buildsoft
    :net use n: \\rxbrissrv\rxbrisdata
    net use p: \\jlrx01\digi_photos
    net use s: \\sqlserver\solomon
    net use u: \\jlrx01\home\%username%
    :net use v: \\Gopher\VetAntivirus
    Login script execution status:
    C:\Documents and Settings\jmilano>net use g: \\jlrx01\jldata
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use h: \\jlrx01\actdata
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use i: \\jlrx01\buildsoftjobs
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use k: \\jlrx01\archives
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use l: \\jlrx01\digital_dictation
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use m: \\jlrx01\buildsoft
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use p: \\jlrx01\digi_photos
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use s: \\sqlserver\solomon
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>net use u: \\jlrx01\home\jmilano
    System error 85 has occurred.

    The local device name is already in use.


    C:\Documents and Settings\jmilano>pause
    Press any key to continue . . .
    Net USE output:
    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\jmilano>net use
    New connections will not be remembered.


    Status Local Remote Network

    -------------------------------------------------------------------------------
    Unavailable__G:____\\jlrx01\jldata_____________Mic rosoft Windows Network
    OK___________H:____\\jlrx01\actdata____________Mic rosoft Windows Network
    OK___________I:____\\jlrx01\buildsoftjobs______Mic rosoft Windows Network
    OK___________J:____\\jlrx02\jlawestdata________Mic rosoft Windows Network
    OK___________K:____\\jlrx01\archives___________Mic rosoft Windows Network
    OK___________L:____\\jlrx01\digital_dictation__Mic rosoft Windows Network
    Disconnected_M:____\\jlrx01\buildsoft__________Mic rosoft Windows Network
    OK___________P:____\\jlrx01\digi_photos________Mic rosoft Windows Network
    OK___________S:____\\sqlserver\solomon_________Mic rosoft Windows Network
    The command completed successfully.


    C:\Documents and Settings\jmilano>
    Note that all drives listed in NET USE are available in Windows Explorer, and pointing to the correct shares on the respective servers, except for the U-Driver which is pointing to the same share as the G-Drive and the M-Drive which I had to remove the share from the source server earlier today (no problem tho with this mapping).

    So why do drives G: & J: come up as Unavailable & disconnected respectively???

    Here's a screenshot:



    Can someone suggest why this is ocurring?
    |
    +-- JDMils
    |
    +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
    |

  • #2
    Re: Drive mappings are not mapping correctly.

    I haven't used batch file logon scripts since WSH was released, as VBS logon scripts are about 10 times faster, and much more feature rich.

    http://www.computerperformance.co.uk...on_scripts.htm

    http://www.informit.com/articles/art...p?p=19420&rl=1

    http://groups.msn.com/windowsscript/logonscripts.msnw
    Patrick Rouse
    Microsoft MVP - Terminal Server, Provision Networks VIP
    President - Session Computing Solutions, LLC
    http://www.sessioncomputing.com

    Comment


    • #3
      Re: Drive mappings are not mapping correctly.

      Thanks. Cool articles which I will start experimenting with. But back to my problem, why is the TS acting this way with its drive mappings?
      |
      +-- JDMils
      |
      +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
      |

      Comment


      • #4
        Re: Drive mappings are not mapping correctly.

        just my 2 cents

        For System error 85 has occurred. The local device name is already in use error messages

        Try adding net use * /delete in the top of the script.
        This will remove al current connected drivemappings from the user. Then create the mappings with you're current script.


        For disconnecting:
        Also run the following command on the server where the shares are located:
        Code:
        net config server /autodisconnect:-1
        see for more information:
        http://support.microsoft.com/default...b;en-us;138365
        Marcel
        Technical Consultant
        Netherlands
        http://www.phetios.com
        http://blog.nessus.nl

        MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
        "No matter how secure, there is always the human factor."

        "Enjoy life today, tomorrow may never come."
        "If you're going through hell, keep going. ~Winston Churchill"

        Comment


        • #5
          Re: Drive mappings are not mapping correctly.

          I've tried all the suggestions but still have the same problem. Can any1 help further?
          |
          +-- JDMils
          |
          +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
          |

          Comment


          • #6
            Re: Drive mappings are not mapping correctly.

            How is the Terminal Services Home Folder setup in AD Users & Computers (under Terminal Services Profile tab)? Is U: their Home Folder drive letter or G:?
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: Drive mappings are not mapping correctly.

              Some users have "\\jlrx01\trmprofiles\kdare" in the Profile Path with no other settings changed. Other users have nothing changed, not even the Profile Path.

              What benefits does a user get when there is a Terminal Services Profile setup?
              |
              +-- JDMils
              |
              +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
              |

              Comment


              • #8
                Re: Drive mappings are not mapping correctly.

                If you use Roaming Profiles on the client OS, you MUST define a different TS Roaming Profile or the client OS Roaming Profile will be used on the TS which will cause all kinds of problems, including profile corruption, data loss...



                Originally posted by JDMils
                Some users have "\\jlrx01\trmprofiles\kdare" in the Profile Path with no other settings changed. Other users have nothing changed, not even the Profile Path.

                What benefits does a user get when there is a Terminal Services Profile setup?
                Patrick Rouse
                Microsoft MVP - Terminal Server, Provision Networks VIP
                President - Session Computing Solutions, LLC
                http://www.sessioncomputing.com

                Comment


                • #9
                  Re: Drive mappings are not mapping correctly.

                  FYI, I think I found the solution. It seems our file server is resetting itself because of an unknown faulty device driver and when it reboots, the drive mappings on the Terminal server are all reset to the G drive, being the first mapped drive in the script.

                  Now I just have to find which driver on the file server is screwing up.
                  |
                  +-- JDMils
                  |
                  +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
                  |

                  Comment

                  Working...
                  X