By default, autoexec.cmd has security set so that the system and administrators have full control, and the special group Everyone has read-only access. This prevents users from modifying the autoexec.cmd file and then rebooting the machine to run their commands. (Note: file-level security is only available on NTFS-formatted drives.)

By default, the Greyware Autoexec Service runs under the LocalSystem security context. This gives the autoexec.cmd program full control over the local machine, but no network access. If you want your autoexec.cmd to use network resources, you must change the user account. Use Control Panel / Services / Greyware Autoexec Service / Startup. Pick a user account with the authority you desire, and provide the proper password.

Also by default, the Greyware Autoexec Service is set to run with the Automatic startup type. This means that the service will run automatically after the machine boots. The service turns itself off after running, so although it is set to automatic, it probably won't be running when you examine the services in Control Panel. You may manually start the service from Control Panel at any time. It will run and then turn itself off again. Since the service is set to automatic, it will run once every time you boot the machine.

Greyware Autoexec Service stores its configuration parameters in

    HKEY_LOCAL_MACHINE
        System
            CurrentControlSet
                Services
                    Greyware Autoexec Service
                        Parameters

• Directory REG_SZ:
  This value defaults to your %systemroot%\system32 directory. It specifies the current directory when the service is running. You may change this to any valid local directory.
• Filename REG_SZ:
  This value defaults to autoexec.cmd. This is the name of the batch file or executable program the service runs at startup. If no path information is specified, the program is assumed to be in the directory specified in the Directory value (see above). By specifying an explicit path here, you can load the program from one directory and execute it in another.

You may want to have every machine in the domain execute the same batch file on startup. To do this, specify a UNC path for the Filename value in the registry. For example, to have all machines run a program found on server Laura in the shared Scripts directory, specify \\laura\scripts\autoexec.cmd. (Note: Remember that to access network resources, the service must be running under a valid user context. Use Control Panel to change the user context under which the service runs.)