Create SC

Creates a subkey and entries for the service in the registry and in the Service Control Manager's database.

Note

This workflow is available only for use in Microsoft Windows environments.

 Workflow inputs – Create SC

Call Workflow Input

Description

Required

Default Value

connection details

XML document conforming to the Connection Details common object that contains the information required to execute a command via command line.

Yes

n/a

service name

Specifies the service name returned by the getkeyname operation.

Yes

n/a

binary path

Specifies a path to the service binary file.

Yes

n/a

server name

Specifies the name of the remote server on which the service is located.

 

Note

The name must use the Universal Naming Convention (UNC) format ("/myserver"). To run SC.exe locally, ignore this parameter.

No

Name of server on which the service is located.

service type

Specifies the service type.

 

Valid values:

  • own – The service runs in its own process. It does not share an executable file with other services
  • share – The service runs as a shared process. It shares an executable file with other services
  • kernelDriver.filesysFile &ndash
  • system driver
  • recFile – system–recognized driver that identifies file systems used on the computer; adapt –Adapter driver, identifies hardware items such as keyboard, mouse, and disk drive; interact – The service can interact with the desktop, receiving input from users.

    Interactive services must be run under the LocalSystem account

 

Note

interact must be used in conjunction with servicee type= ‘own’ or service type= ‘shared’

.

No

own

start

Specifies the start type for the service.

 

Valid values:

  • boot – A device driver that is loaded by the boot loader
  • system – A device driver that is started during kernel initialization
  • auto – A service that automatically starts each time the computer is restarted and runs even if no one logs on to the computer
  • demand – A service that must be manually started
  • disabled – A service that cannot be started

 

Note

To start a disabled service, change the start type to some other value.

No

demand

error

Specifies the severity of the error if the service fails to start during boot.

 

Valid values:

  • normal – The error is logged and a message box is displayed informing the user that a service has failed to start. Startup will continue
  • severe – The error is logged, if possible. The computer attempts to restart with the last–known–good configuration. This could result in the computer being able to restart, but the service can still be unable to run
  • critical – If possible, the error is logged. The computer attempts to restart with the last–known–good configuration. If the last–known–good configuration fails, startup also fails, and the boot process halts with a Stop error
  • ignore – The error is logged and startup continues. No notification is given to the user beyond recording the error in the Event Log.

No

normal

group

Specifies the name of the group of which this service is a member. The list of groups is stored in the registry in the HKLM/System/CurrentControlSet/Control/ServiceGroupOrder subkey.

No

null

tag

Specifies whether or not to obtain a TagID from the CreateService call.

 

Note

Only used in conjunction with start= ‘boot’ or ‘system’.

No

 

depend

Specifies the names of services or groups which must start before this service.

Note

The names are separated by forward slashes ( / ).

No

 

object

Specifies a name of an account in which a service will run, or specifies a name of the Windows driver object in which the driver will run.

No

LocalSystem

display name

Specifies a friendly, meaningful name that can be used in user–interface programs to identify the service to users. For example, the subkey name of one service is wuauserv, which is not be helpful to the user, and the display name is Automatic Updates.

No

 

password

Specifies a password. This is required if an account other than the LocalSystem account is used.

Conditional; required if object is ‘Local System’.

 

 

 Workflow outputs – Create SC

Call Workflow Output

Description

output

XML document consisting of one or more <line> elements that contain the command response. Each <line> element contains an index attribute indicating the order in which the information was returned by the command.

success

Did the operation succeed?

 

Valid values: true, false

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*