RDP 6 Client Using Wrong User's Temp Directory

  • Thread starter Thread starter Will
  • Start date Start date
W

Will

Guest
I'm coming in to a Windows 2000 server as the local administrator from a
Windows XP client running RDP 6. Once logged in, I try to start an
application in the security context of an ordinary user. This works, but
the application is apparently running in a process environment inherited
from the local administrator, because for example the TEMP directory it
tries to use is the local administrators.

Is there any way for me to ensure that the application starts up in a
different security context and also uses the correct environment and user
registry?

--
Will
 
Re: RDP 6 Client Using Wrong User's Temp Directory

Hi Will,

How exactly are you running this program? I have not seen
the symptoms you describe.

As a test I created a shortcut to cmd.exe on the desktop, then
shift right-clicked it, chose Runas, and entered a different
user name/password. After the command prompt opened
I typed set and verified correct tmp paths as well as opened
task manager and verified that the cmd.exe process was
running under a different user.

-TP

Will wrote:
> I'm coming in to a Windows 2000 server as the local administrator
> from a Windows XP client running RDP 6. Once logged in, I try to
> start an application in the security context of an ordinary user.
> This works, but the application is apparently running in a process
> environment inherited from the local administrator, because for
> example the TEMP directory it tries to use is the local
> administrators.
>
> Is there any way for me to ensure that the application starts up in a
> different security context and also uses the correct environment and
> user registry?
 
Back
Top