TC doesn't set its environments for program runs as admin

[ts4242]

When running a program as administrator from TC, TC doesn't set its environments for that program. You can test with this program

Is it bug, feature or limitation?

TC 7.50a / Windows 7 ultimate

[Balderstrom]

The help for the cmd.exe RunAs command:

Code: Select all

RUNAS [/profile] [/env] [/netonly] /user:<UserName> program

   /profile        if the user's profile needs to be loaded
   /env            to use current environment instead of user's.
   /netonly        use if the credentials specified are for remote access only.
   /user           <UserName> should be in form USER@DOMAIN or DOMAIN\USER
   program         command line for EXE.  See below for examples

With RunAs you need to specify you want to use the current environment -- just like a normal launch of a program would do.

[ts4242]

2Balderstrom

I'm using "Run As Administrator" from the context menu and I was expecting TC pass its environments

[Balderstrom]

The Context Menu "Run As Administrator" is not TC (AFAIK) -- now if it is, that would be good to know, since I should be running Win7 early next year.

MVV has written Sudo.exe and another TC user indicated a similiar program as well as RunAs available in Win2K/XP. If TC had some internal RunAs Admin implementation there would be little need for any of that.

PS: Aside from TcmAdmin.exe, which can only be used by TC for File Operations.

[MVV]

2Balderstrom

I'm using "Run As Administrator" from the context menu and I was expecting TC pass its environments

TC can't choose what to pass or not when you use "Run As Admin", its all Windows. BTW, did you notice that if you start CMD using "Run As Admin", its start path is always Windows\System32? Its all dumb Windows:)