Hello Glenn

I need to know why doing the shell or comspec command line is not
exactly like a locally run CLI? or say I use PSTOOLS psexec command
these claim to run a CLI shell dont they, but isnt really a true shell is it? I mean I have this problem running a msi remotely using psexec
and I can run many other msi installer files with the comspec/shell command
in kix but I can run the msi locally thru the CLI on that machine as admin of that machine and it runs fine but when I run the same command using psexec and msiexec /switches type command it doesnt scope correctly.

My ramblings is my lack of terms to use for you to help me understand but
I am grasping at the words scope you know path reference. running programs locally from the cli is to me a diferent scope reference that running thing remotely and scope is a very important issue when dealing with programs and installing them remotely. how can I get the same scope installing things remotely as I would running the same file and same commands locally on the machine thru the local CLI. I just dont understand how I can mimic the pure CLI environment and scope but do it remotely?
did I make sense or give you a big headache.?

I just wish I had a greater understanding of why I cant get the same scope remotely as I have with local CLI programs and command line?

thanks

~Robert
_________________________
Robert
A+, CCNA, MCP
Network Admin
Credit Union Wisconsin