We are attempting to install a vendor app onto a Win2k3 server that is a member of a 2k3 AD environment which has policies applied to the local machine.
We suspect that the policy is blocking the ability for the application to create services on the server, and also register an encrypted license key into the registry. Both functions are done from a command line with switches. When running the command to create the services, we get a DOS error of "Error writing startup parameters Error Code = 6
The handle is invalid."
This install worked prior to the policy being applied to the server. No other changes to the system have been made.
If anyone is possibly able to identify which policy options may be affecting it, I would appreciate your help. My current suspicion is that "deny logon as batch file" and "deny logon as a service" may be the culprits, but I'd like to check that there may not be something else out there causing me the grief that I havent identified yet.
We suspect that the policy is blocking the ability for the application to create services on the server, and also register an encrypted license key into the registry. Both functions are done from a command line with switches. When running the command to create the services, we get a DOS error of "Error writing startup parameters Error Code = 6
The handle is invalid."
This install worked prior to the policy being applied to the server. No other changes to the system have been made.
If anyone is possibly able to identify which policy options may be affecting it, I would appreciate your help. My current suspicion is that "deny logon as batch file" and "deny logon as a service" may be the culprits, but I'd like to check that there may not be something else out there causing me the grief that I havent identified yet.
