SMS_TaskSequence_AutoApplyAction Server WMI Class

Articolo
05/03/2011

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

The SMS_TaskSequence_AutoApplyAction Windows Management Instrumentation (WMI) class is an SMS Provider server class, in Configuration Manager, that represents a task sequence action that matches and installs device drivers as part of an operating system deployment.

The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties.

Class SMS_TaskSequence_AutoApplyAction : SMS_TaskSequence_Action
{
      Boolean BestMatch;
      String CategoryList[];
      SMS_TaskSequence_Condition Condition;
      Boolean ContinueOnError;
      String Description;
      Boolean Enabled;
      String Name;
      String SupportedEnvironment;
      UInt32 Timeout;
      Boolean UnsignedDriver;
};

Methods

The SMS_TaskSequence_AutoApplyAction class does not define any methods.

Properties

BestMatch
Data type: Boolean

Access type: Read/Write

Qualifiers: [Not_Null]

true (default) to install the device driver that is the best match for the hardware device. Set this property to false to install all compatible device drivers and have the operating system choose the best driver to use.

Note

This property is required by the task sequence action if there are multiple device drivers in the driver catalog that are compatible with the hardware device.

CategoryList
Data type: String Array

Access type: Read/Write

Qualifiers: None

Unique IDs of categories for which the task sequence action searches in the driver catalog. The default value is null.

You can obtain the available category IDs by enumerating the SMS_CategoryInstance Server WMI Class objects on the site.

Condition
Data type: SMS_TaskSequence_Condition

Access type: Read/Write

Qualifiers: None

See SMS_TaskSequence_Action Server WMI Class.

ContinueOnError
Data type: Boolean

Access type: Read/Write

Qualifiers: None

See SMS_TaskSequence_Action Server WMI Class.

Description
Data type: String

Access type: Read/Write

Qualifiers: [AllowedLen("0-255")]

See SMS_TaskSequence_Action Server WMI Class.

Enabled
Data type: Boolean

Access type: Read/Write

Qualifiers: None

See SMS_TaskSequence_Action Server WMI Class.

Name
Data type: String

Access type: Read/Write

Qualifiers: [AllowedLen("1-100")]

See SMS_TaskSequence_Action Server WMI Class.

SupportedEnvironment
Data type: String

Access type: Read/Write

Qualifiers: [Not_Null:ToInstance]

See SMS_TaskSequence_Action Server WMI Class.

The default value of this property for this task sequence action is WinPE.

Timeout
Data type: UInt32

Access type: Read/Write

Qualifiers: None

See SMS_TaskSequence_Action Server WMI Class.

UnsignedDriver
Data type: Boolean

Access type: Read/Write

Qualifiers: [Not_Null, VariableName("OSDAllowUnsignedDriver")]

true to configure the Windows operating system to allow unsigned device drivers to be installed. The default value is false.

The task sequence variable associated with this property is OSDAllowUnsignedDriver. For more information, see the MSDN documentation for Operating System Deployment Task Sequence Variables.

Note

This property is required by the task sequence action. However, it is not used when deploying the Windows Vista operating system.

Remarks

Class qualifiers for this class include:

[CommandLine("osddriverclient.exe /auto /bestmatch:%%OSDAutoApplyDriverBestMatch%% /unsigned:%%OSDAllowUnsignedDriver%%"),

ActionCategory{"Drivers,1,5"},VariablePrefix("OSDAutoApplyDriver"),

ActionUI{"AdminUI.TaskSequenceEditor.dll", "Microsoft.ConfigurationManagement.AdminConsole.TaskSequenceEditor", "AutoApplyDriverControl", "TaskSequenceOptionControl"}]

For more information about both the class qualifiers and the property qualifiers included in the Properties section, see Configuration Manager Class and Property Qualifiers.

Requirements

Runtime Requirements

For more information, see Configuration Manager Server Runtime Requirements.

Development Requirements

For more information, see Configuration Manager Server Development Requirements.

Condividi tramite