G
Guest
Hi.
Aim: Run a scheduled task on Server A, which is running Windows 2000 Server
SP4, under local user account SERVERUSER, which is a member of the group
USERS. The scheduled task calls a vbs script, which is located on Client
Computer A, whose operating system is Windows XP SP2, under the folder USER,
which is a shared resource, on which only the local user CLIENTUSER has READ
access.
Situation: SERVERUSER doesn't seem to see the shared resource once the
scheduled task is launch (it fails with 0x2). I have mapped a network drive
to Client Computer A, to shared resource folder USER, with priviledges of
CLIENTUSER just ok.. but still, once the task is launched, SERVERUSER doesn't
recognize the drive. The mapping has been done under the ADMINISTRATOR
account on Server A. The only way I seem to get everything working as I want
is If I share the resource once I run the task (with: net use *
\\clientcomputera\user /persistent:no user:clientcomputera\user password) but
this solution is not feasible, since I have to especify and hard-code the
password and create an aditional batch job on Server A.
Question: Is there anyway I can map a scheduled task directly to use a file
on Client Computer A in Server A without having to make the share everytime I
run the task ? /persistent:YES is of no help since once the task is ran, the
mapping dissapear.
If have not explained myself very well, feel free to ask, and I'll do my
best to explain it in more detail.
Thanks!
Aim: Run a scheduled task on Server A, which is running Windows 2000 Server
SP4, under local user account SERVERUSER, which is a member of the group
USERS. The scheduled task calls a vbs script, which is located on Client
Computer A, whose operating system is Windows XP SP2, under the folder USER,
which is a shared resource, on which only the local user CLIENTUSER has READ
access.
Situation: SERVERUSER doesn't seem to see the shared resource once the
scheduled task is launch (it fails with 0x2). I have mapped a network drive
to Client Computer A, to shared resource folder USER, with priviledges of
CLIENTUSER just ok.. but still, once the task is launched, SERVERUSER doesn't
recognize the drive. The mapping has been done under the ADMINISTRATOR
account on Server A. The only way I seem to get everything working as I want
is If I share the resource once I run the task (with: net use *
\\clientcomputera\user /persistent:no user:clientcomputera\user password) but
this solution is not feasible, since I have to especify and hard-code the
password and create an aditional batch job on Server A.
Question: Is there anyway I can map a scheduled task directly to use a file
on Client Computer A in Server A without having to make the share everytime I
run the task ? /persistent:YES is of no help since once the task is ran, the
mapping dissapear.
If have not explained myself very well, feel free to ask, and I'll do my
best to explain it in more detail.
Thanks!