Anilrgowda

Question: I will explain this as concisely as possible... I have a network app that requires local admin rights but also the app is hard coded to utilize the 'R' drive which is a mapped network share (the app could be started using a UNC path, but will quickly fail if the R drive is not available). The problem is that I don't want all my users to have local admin rights so I'd like them to have non-admin accounts but run the app as local admins.

I am trying to use "runas" at the command line to start the app with a network user account (rmsuser) that is also on the local machine as an administrator. I've logged into the local machine as 'rmsuser' and mapped the R drive. Then logged in as the normal (non-admin) user and tried the following command:

runas /user:rms\rmsuser R:\rms4win\rms\rmsw.exe

It asks for the password and then fails because it can't find the path. Now the normal user who is logged in DOES have the R drive mapped as well as the rmsuser I am trying to runas. I've also tried using the '/env' parameter as well as '/profile' with no luck.

Am I missing something?? Thanks!

(p.s. A friend wrote me a vbs script that will do the runas command and put the password in for me so users won't know it... but first I need to get the runas command to work by itself in the command line)

Anilrgowda

When you use RUNAS, you are actually logging on as a different user. It's most likely that rms\rmsuser doesn't have the R: mapped after login. If this is an occasional manual operation, try to RUNAS cmd.exe, then use net use to map the R: drive then run your app from the command line. If you need to do this all the time, create a batch file or VBScript to map the drive the launch the app, and RUNAS the batch or VBScript.