A workstation command line folder contains a set of scalars that store information about the workstation command line. Workstation command line folder scalars have both create and read access. Therefore, an application can create a workstation command line folder.
A workstation command line folder has the following scalars:
Note that the Name scalar is also used as the identifier for the folder. Your application should ensure that this scalar is not set to a string that is already being used by another workstation command line folder within the same package folder.
In the SMS Administrator, this name will identify the command in the package's Workstation Command Lines dialog box and in a Run Command On Workstation job's Run Command dialog box. If the command is used for a Run Command On Workstation job, this name will also appear in the Command Name field of the Package Command Manager window on the target computers.
The command line is run from the package's root directory, which is located on a shared directory on a server. The command line has a limit of 255 characters.
The command line must specify an executable file or a batch file. It cannot contain MS-DOS or Windows NT commands. If you want to use operating-system commands, put them in a batch file and specify the batch file for the Command scalar.
If you set this scalar to zero, the setting is equivalent to clearing the Automated Command Line check box in the Command Line Properties dialog box in the SMS Administrator. If the command line requires the user at the target computer to enter data or respond to prompts, your application should set this scalar to zero.
If the command completes without any response from the user, make sure the Automated Command Line check box is selected. This displays a No in the package's Requires Input field in the Package Command Manager window.
This is equivalent to the System Background Task check box in the Command Line Properties dialog box in the SMS Administrator.
Set this flag if the application you are installing runs under Windows NT and does not display windows or require user input during installation.
Note that setting this flag implicitly sets the WCL_AUTOMATED_COMMAND_LINE flag.
Caution Your application must set at least one platform flag for the Platforms scalar. If your application does not set a platform flag, the workstation command line will not be available for jobs. To correct this problem, your application must delete the workstation command line folder and re-create the folder with the Platforms scalar set correctly.
You can select one or more operating systems. When a platform flag is set, the package command is available at target computers with the specified platform (the package appears in the Package Command Manager window). When a platform flag is not set, the package command is not available on computers with the specified platform (the package does not appear in the Package Command Manager window).