get error when using run as and trying to install app

[computerjock33]

We are in the process of removing local admin rights from users, and am testing some different items. when I browse to a network drive to install an application, right click on it, choose run as, change credentials to enter domain account information for user with admin rights, I get the following error "path to application setup that im trying to install" The specified path does not exist. Check path and try again. But the path does exist because Im browsing to it with explorer. It does this with any install I try, using the run as any advice?
thanks in advance

 

[chipk]

I've seen problems with RunAs working with UNC names. Try mapping a drive and running it from the mapped location instead of browsing to it.

 

[computerjock33]

by browsing, I mean, opening windows explorer, going to the mapped drive F:\install directory\application\application.exe for example and right-clicking on application.exe, choosing run as from there.......then getting the results above. thanks

 

[chipk]

Gotcha, Browsing usually means looking through Network Places for a share. Thanks for clarifying.

Try the solution here:

http://support.microsoft.com/kb/303308

 

[computerjock33]

hmmmmmm seems to have something to do with being on a domain or a mapped drive issue. If I copy the application to the c: and do run as, it works fine

 

[computerjock33]

Well I guess you cant do it anymore with XP. This is close to what you sent me, I guess I will just have to log the user off and log back on. thanks for you help

. XP's implementation of the RunAs command lets you execute a program under the context of another user. However, if you attempt to use RunAs on a program located on a mapped drive, XP enforces mapped-drive credentials and displays one of the following error messages:
RUNAS ERROR: Unable to run - <drive>:\<path>\<filename>.exe 3: The system cannot find the path specified.
The application failed to initialize properly (0xc0000022). Click on OK to terminate the application.
These errors result because mapped-drive connections use the security context of the currently logged-on user, and RunAs can't use this security context because RunAs is attempting to run programs under another user's security context. To resolve this problem, you need to use a Universal Naming Convention (UNC) name instead of a mapped drive. For example, instead of using
runas /user:<domain>\<user name> h:\progs\delold.exe
use
runas /user:<domain>\<user name> \\server1\share1\progs\delold.exe
Unlike XP, Windows 2000's RunAs implementation doesn't enforce the mapped drive credentials, so a Win2K user can access a mapped drive using another user's security context.