how to map SYSTEM user permissions to a network drive?

how to map SYSTEM user access to a network drive using perl?

Does anybody have any insights to this I been searching around couldn't seem to find it anywhere?

Thanks in advance

PA

Find more posts tagged with

Comments

moonkhanna

please elaborate your question a little.. what is your requirement?

paruntha

well the thing is in order for me to use UNC paths to acess other network dirves during an external task i had to map the network drive and use the network drive letter instead to access the share drive. However i found that if network the drive using the owner's access permissions of the workflow user name and password it works but if i were to map it to someone other than the owner of the workflow ti does not work.

Because of the access issues in workflow I cannot seem to use the UNC paths directly from my perl script but if I were to run it manually through command line it works. So by using teh "net use" command to map and selecting person who has access to UNC path it worked but i think that was because that person was the owner of workflow as well. I"m not too sure about this maybe Im wrong on this but it seems like whoever the owner is I would probably have to use "net use" command on that person to map the drive which would include putting passwords not a good look.

That is why I'm wondering if there is way for to solve this issue by having a SYSTEM access for the network drives not sure if this right way doing it?

thanks

pa

paruntha

another thing is that owner is a master also other users i tried on are masters too

this is Windows xp opertain system by teh way and teamsite 6.5 sp2

moonkhanna

well the thing is in order for me to use UNC paths to acess other network dirves during an external task i had to map the network drive and use the network drive letter instead to access the share drive. However i found that if network the drive using the owner's access permissions of the workflow user name and password it works but if i were to map it to someone other than the owner of the workflow ti does not work.

Because of the access issues in workflow I cannot seem to use the UNC paths directly from my perl script but if I were to run it manually through command line it works. So by using teh "net use" command to map and selecting person who has access to UNC path it worked but i think that was because that person was the owner of workflow as well. I"m not too sure about this maybe Im wrong on this but it seems like whoever the owner is I would probably have to use "net use" command on that person to map the drive which would include putting passwords not a good look.

That is why I'm wondering if there is way for to solve this issue by having a SYSTEM access for the network drives not sure if this right way doing it?

thanks

pa

it seems you are mixing two things here... The above can be easily accomplished with NFS appearing as local drive on your server however in your case, Network drives are only specific to user accounts.. cannot be recognised as system drives because they are not system drives...

What I would recommend here is to use full paths to the network drives instead for eg.. if you have a network drive x: on your server whose complete path is like \\xyz\something\something, then use this complete path is your code...

With net use, you would not be able to determine which user actually edited a resource.. I am not sure, if you are able to .. but thats what I can think of

nipper

So I do this a little differently

I run OpenDeploy as a network user (not local admin) svcIWOV

In the WF I run an IPL that runs OpenDeploy from Y: to \\destaination\somedir

It works great.

moonkhanna

you may also like to check with your sys admins if they can mount the network drive as a system drive for you..

Just shooting an arrow in the dark...

moonkhanna

So I do this a little differently

I run OpenDeploy as a network user (not local admin) svcIWOV

In the WF I run an IPL that runs OpenDeploy from Y: to \\destaination\somedir

It works great.

Good one Andy... :-)

paruntha

Thanks,

The problem is when I use full paths \\server-name\share-drive it doesn't work through workflow, but it works through command line tool when i run it manually....but the open deploy sounds feasible i'll look into that

thanks

PA