[Machine] Shutdown/Restart
This module allows you to shut-down or restart a running machine. This can be used for the local machine as well as on any machine in a member or trusted domain. While this may have many uses, one example we will outline might be when you normally want all your network users to shut off their machines when they leave for the day. If you have a problematic end-user who constantly forgets to do this, you could easily force their machine to shutdown after a certain time each time using this module.
The parameters that the module uses are detailed in the following table.
| Parameter | I/O | Description |
|---|---|---|
| MachineName | In | This is the name of the machine on your network you wish to perform the action on. For the machine the JobServer is running on, you can use the name localhost. |
| Domain | In | The name of the domain the target machine is a member of if it is not the same domain as the JobServer machine. When this is specified, the Username and Password parameters are also required for this to work. |
| Username | In | The username of the account that has permission to shut down the target machine when not specifying the JobServer machine. |
| Password | In | The password of the account specified in the Username parameter. |
| Message | In | The message that is recorded by the target machine as for why the shutdown occurred. |
| TimeoutSeconds | In | This defaults to 60 seconds. This is the amount of time that the machine should wait for running applications to stop before it begins the process of forcefully stopping any running applications. Ideally, you want all the applications to shut down in a controlled fashion, so this value may need to be adjusted higher for large applications that normally do take some time to completely shut down. |
| Restart | In | True (default): The machine will automatically reboot after the shutdown. False: The machine will power down completely after the shutdown is finished. |
| LogOutputLevel | In | Minimal: Normal output to the log. Verbose: More detailed output is written to the log, suitable for debugging purposes. |