Drive mapping weirdness

Viewing 3 posts - 1 through 3 (of 3 total)
  • Back to forum
    Posted in: Muster usage
  • voxel
    10th March 2011 at 8:47 pm #14448

    Hi,

    I’m mapping Y: and Z: to a Windows server (used to work! but something’s weird in 6.1.4 and 6.1.5). When I try to access them via a Generic script it fails… In fact, I did something stranger and got back even more bizarre results. Here’s my test:

    Generic Script job

    Script file: y:testDriveMappings.bat

    Contents of testDriveMappings.bat

    dir c:
    dir y:
    dir z:


    The result I get is

    c:>dir c:
    Volume in drive C is OS
    Volume Serial Number is XXXXXX

    Directory of c:
    ..
    …

    c:>dir y:
    Volume in drive Y is New Volume
    Volume Serial Number is XXXXXXX

    Directory of Y:

    …
    …

    z:

    c:>dir z:

    The system cannot find the path specified.

    My drive mappings are set! And I’ve even restarted my machine! I’m very confused on why Z: is not being mapping. If I copy testDriveMapping to Z: and then run a new script job

    Script file: z:testDriveMappings.bat

    Z is finally mapped! Am I crazy?

    Nelson

    Leonardo Bernardini
    24th March 2011 at 5:36 pm #15099

    Where did you mapped the drives ? It’s possible that you just have the AUTOMAP feature turned on, that means Muster automatically maps Y because Y is where your bat file to launch resides, but it doesn’t know anything about Z because it’s just referenced inside the bat file.
    Are you mapping the drives using the static drive mappings preferences of the client ?

    voxel
    30th March 2011 at 8:35 pm #15154

    Yes, I’m using the static drive mappings. The logged in user has the drives mapped but of course Muster ignore them.

    It turns out the Muster client has to have admin rights to map the drives so we run Muster as admin as a service (?) now and this problem tends to go away… but it is annoying.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.