Reference Guide

Property Description
NOTE: The value No Change (5) has been deprecated instead of
indicating the last requested state is Unknown (0). If the last
requested or desired state is unknown, RequestedState should
have the value Unknown (0), but may have the value No Change
(5)
. Offline (6) indicates that the element has been requested to
transition to the Enabled but Offline EnabledState.
There are two new values in RequestedState that build on the
statuses of EnabledState. These are Reboot (10) and Reset (11). Shut
Down requests an orderly transition to the Disabled state, and may
involve removing power, to completely erase any existing state. The
Disabled state requests an immediate disabling of the element, such
that it will not execute or accept any commands or processing
requests.
This property is set as the result of a method invocation (such as Start
or StopService on CIM_Service), or can be overridden and defined as
WRITEable in a subclass. The method approach is considered
superior to a WRITEable property, because it allows an explicit
invocation of the operation and the return of a result code.
If knowledge of the last RequestedState is not supported for the
EnabledLogicalElement, the property is NULL or has the value 12 Not
Applicable.
TransitioningToState
Indicates the target state to which the instance is transitioning.
Possible values are:
• 0 = Unknown
• 2 = Enabled
• 3 = Disabled
• 4 = Shut Down
• 5 = No Change — Indicates that no transition is in progress.
• 6 = Offline
• 7 = Test
• 8 = Defer
• 9 = Quiesce
• 10 = Reboot
• 11 = Reset
• 12 = Not Applicable — Indicates the implementation does not
support representing ongoing transitions
A value other than 5 or 12 identifies the state to which the element is
in the process of transitioning.
RequestStateChange (Method)
Requests that the state of the element be changed to the value
specified in the RequestedState parameter. When the requested state
change takes place, the EnabledState and RequestedState of the
element will be the same. Invoking the RequestStateChange method
multiple times could result in earlier requests being overwritten or
lost.
208