OK Here's what the Gates consultant said. I don't understand what he is saying to do in the last paragraph about breaking the batch file into three files and how that would work. Do you?
~~~~~~~~~~~~~~~~~~~~~~~~~~
First, when you try to run the batch file and you get the access denied error, it is because the batch file must use the executable CMD.EXE to process. We have restricted access to this file. You can edit the properties of CMD.EXE to add the Child account, or the Everyone group and grant them Read and Execute access.
This will allow the batch file to begin running. There is another problem. The patron accounts do not have the necessary level of permissions to stop and start services. When the batch file hits those commands, it will return an error, and the service will be unaffected. To fix this, you'll need to make Child (or whatever account you wish to have this level of access) a member of the Power Users group.
Now for the security concerns. We have restricted these things in our model in order restrict patrons from being able to do certain things that can adversely affect the performance of the computers. Granted you do have the Centurion Guards installed, so nothing would be permanent, but it can be a headache having to reboot every time a patron gains access to stop certain services or abuses
the access to a command prompt to engage in malicious activity.
One option, if possible (I don't know) is to break the batch file into a three. One that stops the service, one that starts the service and a third that calls both and then launches the MSB title. This would work if you can figure out a way to run the batch files to start and stop the service under another account, without logging out and back in. Again, I don't know if this is possible given
native Windows 2000 tools, or with the use of third-party software.