Is there anyway around the rights issue? Kind of like the way the policies work? I'm stuck in a catch 22 here. I have a script that sets up a service to let another maleable script run at startup with admin rights. I can't seem to find a way in though.
Since kix runs with the local users security rights this might cause a problem.
BUT!
I am working on a way of using SU.exe from the NT resource kix to try and see if there isn't a way around this. the only problem i can see is that you have the potential of having powerful account name/password sitting in a text file that anyone can read.....
I have thought of that, but the thing is, it only needs to be up there long enough to install the service on everyone's workstation, and from then on the password will be ***** out in the services section, and we're home free!
Bryce, I just about have the SU.exe script done (that's where my password post came from). A few more add on's, and we're golden. The script is alot to post, so if you want a copy send me an email. Anyone else who wants it can email me to. For the record, that's why I love this board, it's one of the few places left on the net where the info runs free!
------------------ -------------------------------------------------- Randy Watson PC Consultant I University of Pittsburgh Medical Center
The script is completed, however I'm having problems with the last line, and sure enough, it's the SU.exe command. What would be the correct syntax for this command given: username = username password = password remote workstation to run process on = epicteam-203 Command to run = cmd.exe
