Mini Kabibi Habibi

Current Path : C:/Windows/System32/wbem/en-US/
Upload File :
Current File : C:/Windows/System32/wbem/en-US/wfascim.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!�

��@ ĸ8.rdata�@@.rsrc� �@@�X�b
T88�X�b$��8.rdata8x.rdata$zzzdbg @.rsrc$01@08�.rsrc$02 �S��9�ɢ]��t6�	{۝��h��X�b0�0�H������Q(�@�X�p���������	��
��0�
H�`�x������������ �8�P�h������������� �!(�"@�#X�$p�%��&��'��(��)��*�+�,0�-H�.`�/x�0��1��2��3��4��5�6 �78�8P�9h�:��;��<��=��>��?��@	�A(	�B@	�CX	�Dp	�E�	�F�	�G�	�H�	�I�	�J
�K
�L0
�MH
�N`
�Ox
�P�
�Q�
��
��
�	�
			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�	
	
	 
	0
	@
	P
	`
	p
	�
	�
	�
	�
	�
	�
	�
	�
			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 	0	@	P	`	p	�	�	�	�	�	�	�	�			 80���00,� ]�� az=�������T���J�0�H0�xp��#.�': �TG��K�4P �TU^��X�#�`|x�ؓ�
�\�����
�����@�N�����l����L�T�����0���������0�� &�0%B�t,��$5D�h8��=���Ab�G�
��T��`e��\h��<���ؒ����<��J�<���,��,�l���j����������!�����P�������)��,x�<@D��VF��W��\,��]�_�a���b���d���f��Th��Dj
�Pl�\n��$q��sz��t��@u���
�|�����������~� ��������MUI���XQ����l�
\EO����V�k�ڣ^=���GM���MUIen-US)InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below.
To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: 
<OrgID>:<LocalID> 
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>. 
<LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. 
If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.UThe Caption property is a short textual description (one- line string) of the object.FThe Description property provides a textual description of the object.)A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. 
Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.2.19.0�ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.�A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.�The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.>
Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration\'s values are self-explanatory. However, a few are not and are described here in more detail. 
"Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. 
"Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. 
"In Service" describes an element being configured, maintained, cleaned, or otherwise administered. 
"No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. 
"Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. 
"Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. 
"Dormant" indicates that the element is inactive or quiesced. 
"Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. 
"Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). 
"Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association. 
OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today\'s environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element.UnknownOtherOKDegradedStressedPredictive FailureErrorNon-Recoverable ErrorStartingStoppingStopped
In Service
No ContactLost CommunicationAbortedDormantSupporting Entity in Error	Completed
Power Mode
DMTF ReservedVendor ReservedAStrings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus.PA�A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 
1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped. 
2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. 
3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.QIndicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: 
"Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. 
"Critical Failure" (25) - The element is non-functional and recovery might not be possible. 
"Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 
"Minor Failure" (15) - All functionality is available but some might be degraded. 
"Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 
"OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. 
"Unknown" (0) - The implementation cannot report on HealthState at this time. 
DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.Degraded/Warning
Minor failure
Major failureCritical failureNon-recoverable error�CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact. 
A Null return indicates the implementation (provider) does not implement this property. 
"Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. 
"Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). 
"Communication OK " indicates communication is established with the element, but does not convey any quality of service. 
"No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. 
"Lost Communication" indicates that the Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.
Not AvailableCommunication OK�DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element. 
A Null return indicates the implementation (provider) does not implement this property. 
"Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). 
"No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK". 
"Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. 
"Predictive Failure" indicates that an element is functioning normally but a failure is predicted in the near future. 
"Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention. 
"Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.No Additional Informationm
OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions.
OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test 
A Null return indicates the implementation (provider) does not implement this property. 
"Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. 
"None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). 
"Servicing" describes an element being configured, maintained, cleaned, or otherwise administered. 
"Starting" describes an element being initialized. 
"Stopping" describes an element being brought to an orderly stop. 
"Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. 
"Dormant" indicates that the element is inactive or quiesced. 
"Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). 
"Migrating" element is being moved between host elements. 
"Immigrating" element is being moved to new host element. 
"Emigrating" element is being moved away from host element. 
"Shutting Down" describes an element being brought to an abrupt stop. 
"In Test" element is performing test functions. 
"Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable.
"In Service" describes an element that is in service and operational.	Servicing	Migrating
EmigratingPAImmigratingSnapshotting
Shutting DownIn Test
Transitioning�PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. 
PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. 
"OK" indicates the ManagedElement is functioning normally. 
"Degraded" indicates the ManagedElement is functioning below normal. 
"Error" indicates the ManagedElement is in an Error condition.�CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include: 
- software components such as application servers, databases, and applications 
- operating system components such as files, processes, and threads 
- device components such as disk drives, controllers, processors, and printers 
- physical components such as chips and cards.2.22.0�CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.2.6.0_The Name property defines the label by which the Filter Entry is known and uniquely identified.0The scoping ComputerSystem\'s CreationClassName.#The scoping ComputerSystem\'s Name.�CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.�Boolean indicating that the match condition described in the properties of the FilterEntryBase subclass should be negated. This property is defined for ease of use when filtering on simple negations - for example, to select all source ports except 162. It is not recommended that this Boolean be set to True when filtering on multiple criteria, such as defining an IPHeadersFilter based on source/destination addresses, ports, and DiffServ Code Points.A FilterList aggregates instances of (subclasses of) FilterEntryBase via the aggregation EntriesInFilterList. The filter entries are always ANDed together when grouped by the FilterList. Note that it is possible to aggregate different types of filters into a single FilterList - for example, packet header filters (represented by the IpHeadersFilter class) and IPsec security filters. 

A FilterList is weak to the network device (e.g., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class.2.7.0GA string that uniquely identifies this instance within the PolicyStore.[Used in CimInstance.ToString(). A short string for describing this instance when debugging.This field is ignored.3Reserved for internal use by the WMI provider only.�An array of addresses, subnets, ranges, or some of the following tokens: Any, LocalSubnet, DefaultGateway, DHCP, WINS, DNS, Internet, Intranet, IntranetRemoteAccess, PlayToTargets.  The 'Any' keyword may only be used by itself.FDetermines whether the the address is considered intranet or Internet.MAn AddressFilter matches based on the local or remote address of the traffic.<Path and filename of the executable whose traffic to filter.=The application package this rule applies to, given as a SID.UFilters traffic based on which local application is sending or receiving the traffic.3A user-friendly name of this policy-related object.�An array of keywords for characterizing / categorizing policy objects. Keywords are of one of two types: 
- Keywords defined in this and other MOFs, or in DMTF white papers. These keywords provide a vendor- independent, installation-independent way of characterizing policy objects. 
- Installation-dependent keywords for characterizing policy objects. Examples include \'Engineering\', \'Billing\', and \'Review in December 2000\'. 
This MOF defines the following keywords: \'UNKNOWN\', \'CONFIGURATION\', \'USAGE\', \'SECURITY\', \'SERVICE\', \'MOTIVATIONAL\', \'INSTALLATION\', and \'EVENT\'. These concepts are self-explanatory and are further discussed in the SLA/Policy White Paper. One additional keyword is defined: \'POLICY\'. The role of this keyword is to identify policy-related instances that may not be otherwise identifiable, in some implementations. The keyword \'POLICY\' is NOT mutually exclusive of the other keywords specified above.
An abstract class defining the common properties of the policy managed elements derived from CIM_Policy. The subclasses are used to create rules and groups of rules that work together to form a coherent set of policies within an administrative domain or set of domains.�PolicyDecisionStrategy defines the evaluation method used for policies contained in the PolicySet. There are two values currently defined: 
- \'First Matching\' (1) executes the actions of the first rule whose conditions evaluate to TRUE. The concept of \'first\' is determined by examining the priority of the rule within the policy set (i.e., by examining the property, PolicySetComponent.Priority). Note that this ordering property MUST be maintained when processing the PolicyDecisionStrategy. 
- \'All\' (2) executes the actions of ALL rules whose conditions evaluate to TRUE, in the set. As noted above, the order of processing of the rules is defined by the property, PolicySetComponent.Priority (and within a rule, the ordering of the actions is defined by the property, PolicyActionStructure.ActionOrder). Note that when this strategy is defined, processing MUST be completed of ALL rules whose conditions evaluate to TRUE, regardless of errors in the execution of the rule actions.First MatchingAll^The PolicyRoles property represents the roles associated with a PolicySet. All contained PolicySet instances inherit the values of the PolicyRoles of the aggregating PolicySet but the values are not copied. A contained PolicySet instance may, however, add additional PolicyRoles to those it inherits from its aggregating PolicySet(s). Each value in PolicyRoles multi-valued property represents a role for which the PolicySet applies, i.e., the PolicySet should be used by any enforcement point that assumes any of the listed PolicyRoles values. 

Although not officially designated as \'role combinations\', multiple roles may be specified using the form: 
<RoleName>[&&<RoleName>]* 
where the individual role names appear in alphabetical order (according to the collating sequence for UCS-2). Implementations may treat PolicyRoles values that are specified as \'role combinations\' as simple strings. 

This property is deprecated in lieu of the use of an association, CIM_PolicySetInRoleCollection. The latter is a more explicit and less error-prone approach to modeling that a PolicySet has one or more PolicyRoles.�Indicates whether this PolicySet is administratively enabled, administratively disabled, or enabled for debug. The "EnabledForDebug" property value is deprecated and, when it or any value not understood by the receiver is specified, the receiving enforcement point treats the PolicySet as "Disabled". To determine if a PolicySet is "Enabled", the containment hierarchy specified by the PolicySetComponent aggregation is examined and the Enabled property values of the hierarchy are ANDed together. Thus, for example, everything aggregated by a PolicyGroup may be disabled by setting the Enabled property in the PolicyGroup instance to "Disabled" without changing the Enabled property values of any of the aggregated instances. The default value is 1 ("Enabled").EnabledDisabledEnabled For Debug!PolicySet is an abstract class that represents a set of policies that form a coherent set. The set of contained policies has a common decision strategy and a common set of policy roles (defined via the PolicySetInRole Collection association). Subclasses include PolicyGroup and PolicyRule.2.8.0(The scoping System\'s CreationClassName.The scoping System\'s Name.(A user-friendly name of this PolicyRule.Indicates whether the list of PolicyConditions associated with this PolicyRule is in disjunctive normal form (DNF), conjunctive normal form (CNF), or has no conditions (i.e., is an UnconditionalRule) and is automatically evaluated to "True." The default value is 1 ("DNF").Unconditional RuleDNFCNF`A free-form string that can be used to provide guidelines on how this PolicyRule should be used.PA�PolicyRule.Priority is deprecated and replaced by providing the priority for a rule (and a group) in the context of the aggregating PolicySet instead of the priority being used for all aggregating PolicySet instances. Thus, the assignment of priority values is much simpler. 

A non-negative integer for prioritizing this Policy Rule relative to other Rules. A larger value indicates a higher priority. The default value is 0.TA flag indicating that the evaluation of the Policy Conditions and execution of PolicyActions (if the Conditions evaluate to TRUE) is required. The evaluation of a PolicyRule MUST be attempted if the Mandatory property value is TRUE. If the Mandatory property is FALSE, then the evaluation of the Rule is \'best effort\' and MAY be ignored.�This property gives a policy administrator a way of specifying how the ordering of the PolicyActions associated with this PolicyRule is to be interpreted. Three values are supported: 
o mandatory(1): Do the actions in the indicated order, or don\'t do them at all. 
o recommended(2): Do the actions in the indicated order if you can, but if you can\'t do them in this order, do them in another order if you can. 
o dontCare(3): Do them -- I don\'t care about the order. 
The default value is 3 ("DontCare").	MandatoryRecommended	Dont Care0ExecutionStrategy defines the strategy to be used in executing the sequenced actions aggregated by this PolicyRule. There are three execution strategies: 

Do Until Success - execute actions according to predefined order, until successful execution of a single action. 
Do All - execute ALL actions which are part of the modeled set, according to their predefined order. Continue doing this, even if one or more of the actions fails. 
Do Until Failure - execute actions according to predefined order, until the first failure in execution of an action instance.Do Until SuccessDo AllDo Until Failure�The central class used for representing the \'If Condition then Action\' semantics of a policy rule. A PolicyRule condition, in the most general sense, is represented as either an ORed set of ANDed conditions (Disjunctive Normal Form, or DNF) or an ANDed set of ORed conditions (Conjunctive Normal Form, or CNF). Individual conditions may either be negated (NOT C) or unnegated (C). The actions specified by a PolicyRule are to be performed if and only if the PolicyRule condition (whether it is represented in DNF or CNF) evaluates to TRUE. 

The conditions and actions associated with a PolicyRule are modeled, respectively, with subclasses of PolicyCondition and PolicyAction. These condition and action objects are tied to instances of PolicyRule by the PolicyConditionInPolicyRule and PolicyActionInPolicyRule aggregations. 

A PolicyRule may also be associated with one or more policy time periods, indicating the schedule according to which the policy rule is active and inactive. In this case it is the PolicySetValidityPeriod aggregation that provides this linkage. 

The PolicyRule class uses the property ConditionListType, to indicate whether the conditions for the rule are in DNF (disjunctive normal form), CNF (conjunctive normal form) or, in the case of a rule with no conditions, as an UnconditionalRule. The PolicyConditionInPolicyRule aggregation contains two additional properties to complete the representation of the Rule\'s conditional expression. The first of these properties is an integer to partition the referenced PolicyConditions into one or more groups, and the second is a Boolean to indicate whether a referenced Condition is negated. An example shows how ConditionListType and these two additional properties provide a unique representation of a set of PolicyConditions in either DNF or CNF. 

Suppose we have a PolicyRule that aggregates five PolicyConditions C1 through C5, with the following values in the properties of the five PolicyConditionInPolicyRule associations: 
C1: GroupNumber = 1, ConditionNegated = FALSE 
C2: GroupNumber = 1, ConditionNegated = TRUE 
C3: GroupNumber = 1, ConditionNegated = FALSE 
C4: GroupNumber = 2, ConditionNegated = FALSE 
C5: GroupNumber = 2, ConditionNegated = FALSE 

If ConditionListType = DNF, then the overall condition for the PolicyRule is: 
(C1 AND (NOT C2) AND C3) OR (C4 AND C5) 

On the other hand, if ConditionListType = CNF, then the overall condition for the PolicyRule is: 
(C1 OR (NOT C2) OR C3) AND (C4 OR C5) 

In both cases, there is an unambiguous specification of the overall condition that is tested to determine whether to perform the PolicyActions associated with the PolicyRule. 

PolicyRule instances may also be used to aggregate other PolicyRules and/or PolicyGroups. When used in this way to implement nested rules, the conditions of the aggregating rule apply to the subordinate rules as well. However, any side effects of condition evaluation or the execution of actions MUST NOT affect the result of the evaluation of other conditions evaluated by the rule engine in the same evaluation pass. That is, an implementation of a rule engine MAY evaluate all conditions in any order before applying the priority and determining which actions are to be executed./LimitNegotiation is used as part of processing either a key exchange or IPsec Rule. Before proceeding with either a phase 1 or a phase 2 negotiation, this property is checked to determine if the negotiation role of the Rule matches that defined for the negotiation being undertaken (e.g., Initiator, Responder, or Both). If this check fails, then the negotiation is stopped. Note that this only applies to new negotiations and has no effect on either renegotiation or refresh operations with peers for which an established Security Association already exists.Initiator-OnlyResponder-OnlyEither�SARule is a base class for defining IKE and IPsec Rules. Although concrete (because it subclasses from a concrete class), it is not intended to be instantiated. It defines a common connection point for associating conditions and actions for both types of rules. Note that each valid PolicyGroup containing SARules MUST use a unique priority number for the Rule in the aggregation, PolicySetComponent.Priority.Specifies which platforms the rule is applicable on.  If null, the rule applies to all platforms (the default).  Each entry takes the form Major.Minor+, for instance 6.0, 6.1+, or 6.2.  If + is specified, then it means that the rule applies to that version or greater.  For instance, Windows Vista could be represented as 6 or 6.0, and Windows 7 or later would be represented as 6.1+.  + may only be attached to the final item in the list.  6.0+ is not valid because it means the same thing as null (all platforms).^The locale-independent name for the group that this rule belongs to.  If this field is non-null, then Windows Defender Firewall with Advanced Security assumes that this rule belongs to a Windows component or an installed application, and some parts of the rule are protected (including but not limited to the Name, Description, Program, and Service).~The localized name of this rule.  This field's value is based on the value of ElementName.  Changes to this field are ignored.zThe group that this rule belongs to.  This field is based on the value of RuleGroup and changes to this field are ignored.&Which profiles this rule is active on.AnyPublicPrivateDomain=The InstanceID of the MainModeCryptoSet to use for Main Mode.?The InstanceID of the QuickModeCryptoSet to use for Quick Mode.FThe InstanceID of the Phase1AuthenticationSet to use for Phase 1 auth.FThe InstanceID of the Phase2AuthenticationSet to use for Phase 2 auth.�PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. 
PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. 
"OK" indicates the ManagedElement is functioning normally. 
"Degraded" indicates the ManagedElement is functioning below normal. 
"Error" indicates the ManagedElement is in an Error condition. 
9The detailed status of the rule, as a numeric error code.-The detailed status of the rule, as a string.gIf this object is retrieved from the ActiveStore, describes the current enforcement status of the rule.InvalidFullFirewallOffInProfileCategoryOffDisabledObjectInactiveProfileLocalAddressResolutionEmptyRemoteAddressResolutionEmptyLocalPortResolutionEmptyRemotePortResolutionEmptyInterfaceResolutionEmptyApplicationResolutionEmptyRemoteMachineEmptyRemoteUserEmptyLocalGlobalOpenPortsDisallowedPA%LocalAuthorizedApplicationsDisallowedLocalFirewallRulesDisallowedLocalConsecRulesDisallowedNotTargetPlatformOptimizedOutLocalUserEmptyTransportMachinesEmptyTunnelMachinesEmptyTupleResolutionEmpty�If this object is retrieved from the ActiveStore, with the TracePolicyStoreSource option set, describes the type of PolicyStore where this rule originally came from.�If this object is retrieved from the ActiveStore, with the TracePolicyStoreSource option set, contains the path to the PolicyStore where this rule originally came from.�Represents an IPsec Rule.  Subtypes differentiate between Connection Security Rules (MSFT_NetConSecRule) and Main Mode Rules (MSFT_NetMainModeRule).Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: 
<OrgID>:<LocalID> 
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>. 
<LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. 
For DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.�The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.)GCIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future.
Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. 
Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. 
When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. 
Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.2Reserved for internal use by the WMI provider onlyPAActionAddDeleteArray of V6 addressesArray of V4 addressesPolicy StoreIPsec rule name
endpoint type	Endpoint1	Endpoint2*Array of names that failed name resolution"The DisplayName of the IPsec rule.IPSec policy deltazA brief description of the rule.  May be an indirect string.  If it is an indirect string, then it may not be overwritten.DThe locale-independent name of the rule.  May be an indirect string.DIndicates whether this rule is administratively enabled or disabled.PA1The IPsec Encapsulation Mode that should be used.Transport ModeTunnel ModeTWhether to allow Trusted Intermediaries to set the key of SA's created by this rule.cWhether to allow Trusted Intermediaries to be notified when the encryption keys for this SA change.[The maximum lifetime, in seconds, for SA's created by this rule across the forwarding path.CDetermines how aggressively to enforce security on inbound traffic.NeverRequestRequireDDetermines how aggressively to enforce security on outbound traffic.Which keying modules to use.IKEv1IKEv2AuthIPZRequire authorization for endpoints.  The authorization list is part of the IPsec Globals.AAuthorized users for transport mode, specified as an SDDL string.DAuthorized machines for transport mode, specified as an SDDL string."The local tunnel endpoint address.�A Fully-Qualified Domain Name that resolves to a list of allowed Remote Endpoints.  If present, the value in RemoteEndpoint will be used initially, but will be replaced with all the IP addresses that this name resolves to.The remote tunnel endpoint(s).=Allow traffic that is already encrypted to bypass the tunnel.Synchronize IPsec policyServersDomains
Endpoint typeTypes of addressesIPv4IPv6*Servers to perform name resolution againstDelta collectionApply IPsec policy deltasIPv6 AddressesIPv4 AddressesPassThruOutput NetConSecRule Enumerate all parts of all rulesBFinds the rules that will be used to secure the specified traffic.Enable this rule.Disable this rule.Rename this rule.The new name for the rule.Copy this rule."The new policy store for the rule. The new GPOSession for the rule.A Connection Security Rule.&The parent element in the association.%The child element in the association.PA�CIM_Component is a generic association used to establish \'part of\' relationships between Managed Elements. For example, it could be used to define the components or parts of a System.%The parent Policy in the association.)The child/part Policy in the association.�CIM_PolicyComponent is a generic association used to establish \'part of\' relationships between the subclasses of CIM_Policy. For example, the PolicyConditionInPolicyRule association defines that PolicyConditions are part of a PolicyRule.iThe name of the class or the subclass used in the creation of the System object in whose scope this PolicyAction is defined. 

This property helps to identify the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action. 

Note that this property, and the analogous property SystemName, do not represent propagated keys from an instance of the class System. Instead, they are properties defined in the context of this class, which repeat the values from the instance of System to which this PolicyAction is related, either directly via the PolicyActionInPolicyRepository association or indirectly via the PolicyActionInPolicyRule aggregation.�The name of the System object in whose scope this PolicyAction is defined. 

This property completes the identification of the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action.For a rule-specific PolicyAction, the CreationClassName of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.	For a rule-specific PolicyAction, the name of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.*A user-friendly name of this PolicyAction.RDoActionLogging causes a log message to be generated when the action is performed.�A class representing a rule-specific or reusable policy action to be performed if the PolicyConditions for a Policy Rule evaluate to TRUE. Since all operational details of a PolicyAction are provided in subclasses of this object, this class is abstract.lPolicyAction instances may be aggregated into either PolicyRule instances or CompoundPolicyAction instances.BA PolicyAction aggregated by a PolicyRule or CompoundPolicyAction.�ActionOrder is an unsigned integer \'n\' that indicates the relative position of a PolicyAction in the sequence of actions associated with a PolicyRule or CompoundPolicyAction. When \'n\' is a positive integer, it indicates a place in the sequence of actions to be performed, with smaller integers indicating earlier positions in the sequence. The special value \'0\' indicates \'don\'t care\'. If two or more PolicyActions have the same non-zero sequence number, they may be performed in any order, but they must all be performed at the appropriate place in the overall action sequence. 

A series of examples will make ordering of PolicyActions clearer: 
o If all actions have the same sequence number, regardless of whether it is \'0\' or non-zero, any order is acceptable. 
o The values: 
1:ACTION A 
2:ACTION B 
1:ACTION C 
3:ACTION D 
indicate two acceptable orders: A,C,B,D or C,A,B,D, 
since A and C can be performed in either order, but only at the \'1\' position. 
o The values: 
0:ACTION A 
2:ACTION B 
3:ACTION C 
3:ACTION D 
require that B,C, and D occur either as B,C,D or as B,D,C. Action A may appear at any point relative to B, C, and D. Thus the complete set of acceptable orders is: A,B,C,D; B,A,C,D; B,C,A,D; B,C,D,A; A,B,D,C; B,A,D,C; B,D,A,C; B,D,C,A. 

Note that the non-zero sequence numbers need not start with \'1\', and they need not be consecutive. All that matters is their relative magnitude.�PolicyActions may be aggregated into rules and into compound actions. PolicyActionStructure is the abstract aggregation class for the structuring of policy actions.PThis property represents the PolicyRule that contains one or more PolicyActions.TThis property holds the name of a PolicyAction contained by one or more PolicyRules.sA PolicyRule aggregates zero or more instances of the PolicyAction class, via the PolicyActionInPolicyRule association. A Rule that aggregates zero Actions is not valid--it may, however, be in the process of being entered into a PolicyRepository or being defined for a System. Alternately, the actions of the policy may be explicit in the definition of the PolicyRule. Note that a PolicyRule should have no effect until it is valid. 

The Actions associated with a PolicyRule may be given a required order, a recommended order, or no order at all. For Actions represented as separate objects, the PolicyActionInPolicyRule aggregation can be used to express an order. 

This aggregation does not indicate whether a specified action order is required, recommended, or of no significance; the property SequencedActions in the aggregating instance of PolicyRule provides this indication.\DoPacketLogging causes a log message to be generated when the action is applied to a packet.�SAAction is the base class for the various types of key exchange or IPsec actions. It is abstract and used to categorize the different types of actions of SARules.The IPsec rule.The auth/crypto sets.0Links an IPsec rule to its auth and crypto sets.�MinLifetimeSeconds prevents certain denial of service attacks where the peer requests an arbitrarily low lifetime value, causing renegotiations with expensive Diffie-Hellman operations. The property specifies the minimum lifetime, in seconds, that will be accepted from the peer. A value of zero (the default) indicates that there is no minimum value. A non-zero value specifies the minimum seconds lifetime.Seconds|IdleDurationSeconds is the time an SA can remain idle (i.e., no traffic protected using the security association) before it is automatically deleted. The default (zero) value indicates that there is no idle duration timer and that the SA is deleted based upon the SA seconds and kilobyte lifetimes. Any non-zero value indicates the number of seconds that the SA may remain unused.vMinLifetimeKilobytes prevents certain denial of service attacks where the peer requests an arbitrarily low lifetime value, causing renegotiations with expensive Diffie-Hellman operations. The property specifies the minimum lifetime, in kilobytes, that will be accepted from the peer. A value of zero (the default) indicates that there is no minimum value. A non-zero value specifies the minimum kilobytes lifetime. Note that there has been considerable debate regarding the usefulness of applying kilobyte lifetimes to phase 1 security associations, so it is likely that this property will only apply to the subclass, IPsecAction.	KiloBytes�SANegotiationAction is the base class for negotiated SAs. It is abstract, specifying the common parameters that control the IPsec phase 1 and phase 2 negotiations.MThe ExchangeMode designates the mode IKE should use for its key negotiations.BaseMain
Aggressive�UseIKEIdentityType specifies what network identity type should be used when negotiating with the peer. It is used in conjunction with the available IPNetworkIdentity instances, that are associated with an IPProtocolEndpoint.IPV4 AddressFQDN	User FQDNIPV4 Subnet AddressIPV6 AddressIPV6 Subnet AddressIPV4 Address RangeIPV6 Address RangeDER ASN1 DNDER ASN1 GNKEY ID0VendorID specifies the value to be used in the Vendor ID payload. An empty string (the default) means that the Vendor ID payload will not be generated or accepted. A non-NULL value means that a Vendor ID payload will be generated (when acting as an initiator) or is expected (when acting as a responder).hWhen IKEAction.ExchangeMode is set to "Aggressive" (4), this property specifies the key exchange groupID to use in the first packets of the phase 1 negotiation. This property is ignored unless the ExchangeMode is \'aggressive\'. If the GroupID number is from the vendor- specific range (32768-65535), the VendorID qualifies the group number. Well-known group identifiers from RFC2412, Appendix E, are: Group 1=\'768 bit prime\', Group 2=\'1024 bit prime\', Group 3=\'Elliptic Curve Group with 155 bit field element\', Group 4=\'Large Elliptic Curve Group with 185 bit field element\', and Group 5=\'1536 bit prime\'.$No Group/Non-Diffie-Hellman ExchangePADH-768 bit primeDH-1024 bit primeEC2N-155 bit field elementEC2N-185 bit field elementDH-1536 bit primeStandard Group - ReservedOIKEAction specifies the parameters to use for an IPsec IKE phase 1 negotiation.�The ScopedSettingData class represents the general concept of SettingData, which is scoped or contained by a ManagedElement (that is, settings that are specifically defined for a system, device, and so on). ScopedSettingData is tied to a ManagedElement using the ScopedSetting association. Note that the cardinality of the ManagedElement reference is Min(1), Max(1). This cardinality mandates the instantiation of the ScopedSetting association for the referenced instance of ScopedSettingData. ScopedSetting describes the existence requirements and context for the referenced instance of ManagedElement. Specifically, the ManagedElement must exist and it provides the context for the ScopedSettingData.2.10.0�SAProposal is a base class defining the common properties of, and anchoring common associations for, IPsec phase 1 and phase 2 proposals. It is defined as a kind of ScopedSettingData (scoped by a ComputerSystem or AdminDomain), since its subclasses define sets of IPsec properties that MUST be applied together, if negotiated. This subclassing is different than that defined in IETF\'s IPSP Policy draft - where it is subclassed from Policy. The definition as SettingData is more consistent with the application of the properties as a set, to the negotiated Security Association. To indicate that \'this\' proposaltransform is negotiated for a Security Association, use the ElementSettingData to associate the proposal and the SA.MaxLifetimeSeconds specifies the maximum time the IKE message sender proposes for an SA to be considered valid after it has been created. A value of zero indicates that the default of 8 hours be used. A non-zero value indicates the maximum seconds lifetime.-MaxLifetimeKilobytes specifies the maximum kilobyte lifetime the IKE message sender proposes for an SA to be considered valid after it has been created. A value of zero (the default) indicates that there should be no maximum kilobyte lifetime. A non-zero value specifies the desired kilobyte lifetime.
CipherAlgorithm is an enumeration that specifies the proposed encryption algorithm. The list of algorithms was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list and aligns with the values in IKESAEndpoint.CipherAlgorithm.DESIDEABlowfishPARC53DESCASTDMTF/IANA ReservedrDescription of the encryption algorithm when the value 1 ("Other") is specified for the property, CipherAlgorithm.�HashAlgorithm is an enumeration that specifies the proposed hash function. The list of algorithms was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list and aligns with the values in IKESAEndpoint.HashAlgorithm.MD5SHA-1TigeriDescription of the hash function when the value 1 ("Other") is specified for the property, HashAlgorithm.�AuthenticationMethod is an enumeration that specifies the proposed authentication. The list of methods was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list and aligns with the values in IKESAEndpoint.AuthenticationMethod. There is one change to the list - the value 65000 has special meaning. It is a special value that indicates that this particular proposal should be repeated once for each authentication method corresponding to credentials installed on the machine. For example, if the system has a pre-shared key and an public-key certificate, a proposal list would be constructed which includes a proposal that specifies a pre-shared key and a proposal for any of the public-key certificates.Pre-shared KeyDSS SignaturesRSA SignaturesEncryption with RSARevised Encryption with RSAiDescription of the method when the value 1 ("Other") is specified for the property, AuthenticationMethod.CThe property GroupId specifies the proposed phase 1 security association key exchange group. This property is ignored for all aggressive mode exchanges (IKEAction.ExchangeMode = 4). If the GroupID number is from the vendor-specific range (32768-65535), the property VendorID qualifies the group number. Well-known group identifiers from RFC2412, Appendix E, are: Group 1=\'768 bit prime\', Group 2=\'1024 bit prime\', Group 3 =\'Elliptic Curve Group with 155 bit field element\', Group 4= \'Large Elliptic Curve Group with 185 bit field element\', and Group 5=\'1536 bit prime\'.iVendorID identifies the vendor when the value of GroupID is in the vendor-specific range, 32768 to 65535.SIKEProposal contains the parameters necessary to drive the phase 1 IKE negotiation.Represents an auth proposal.CThe locale-independent name for the group that this set belongs to.}The localized name of this set.  This field's value is based on the value of ElementName.  Changes to this field are ignored.yThe group that this set belongs to.  This field is based on the value of RuleGroup and changes to this field are ignored.6The proposals within this set, in order of preference.LA list of auth suites, in preferential order, to use when negotiating an SA.yA brief description of the set.  May be an indirect string.  If it is an indirect string, then it may not be overwritten.CThe locale-independent name of the set.  May be an indirect string.Rename this set.The new name for the set.Copy this set.The new ID for the set.PA!The new policy store for the set.The new GPOSession for the set.PA set of authentication proposals that can be used in Phase 2 of authentication.0The Phase 2 Authentication Set used by the rule.8Relates an IPsec rule to its Phase 2 Authentication Set.The connection security rule.ERelates a connection security rule to its Phase 2 Authentication Set.	The rule.%The filters associated with the rule.(Associates a policy rule to its filters.,The connection security rule being filtered.�Associates a connection security rule with its filters.  Instances of this class can be traversed and the values in the associated filters can be modified, but instances of this class may not be created or deleted.'The address filter applied to the rule.SInterfaces that the traffic applies to.  They may be specified by LUID or by Alias.BFilters traffic based on what interface it is sent or received on.)The interface filter applied to the rule.PA/Specifies what types of interface to filter on.Local area network
Remote accessWirelessIFilters traffic based on the type of interface it is sent or received on..The interface type filter applied to the rule.pIP Protocol Number that this filter applies to.  May be 0-255 or one of the following: ICMPv4, ICMPv6, TCP, UDP.�Applies only when Protocol is TCP or UDP.  Remote ports this filter applies to.  May be a number or range 0-65535, or one of the following: Any, IPHTTPSOut.�Applies only when Protocol is TCP or UDP.  Local ports this filter applies to.  May be a number or range 0-65535, or one of the following: Any, RPC, RPC-EPMap, IPHTTPSIn, PlayToDiscovery.�Applies only when Protocol is ICMPv4 or ICMPv6.  ICMP Type/Code pairs this filter applies to.  May be an ICMP type (0-255), or an ICMP type/code pair in the format Type.Code, where type and code values are numbers from 0 to 255.�Allows filtering traffic to/from endpoints by certain kinds of virtual transports, rather than traditional tuples of addresses, protocols, and ports.
ProximityAppsProximitySharingWifiDirectPrintingWifiDirectDisplayWifiDirectDevices/Filters traffic based on its protocol and port.-The protocol/port filter applied to the rule.6A PolicySet that aggregates other PolicySet instances.(A PolicySet aggregated into a PolicySet.A non-negative integer for prioritizing this PolicySet component relative to other elements of the same PolicySet. A larger value indicates a higher priority. The Priority property MUST have a unique value when compared with others defined for the same aggregating PolicySet.�PolicySetComponent is a concrete aggregation that collects instances of the subclasses of PolicySet (i.e., PolicyGroups and PolicyRules). Instances are collected in sets that use the same decision strategy. They are prioritized relative to each other, within the set, using the Priority property of this aggregation. 

Together, the PolicySet.PolicyDecisionStrategy and PolicySet Component.Priority properties determine the processing for the groups and rules contained in a PolicySet. A larger priority value represents a higher priority. Note that the Priority property MUST have a unique value when compared with others defined for the same aggregating PolicySet. Thus, the evaluation of rules within a set is deterministically specified.The name of the profile.0Whether the firewall is enabled on this profile.'The default action for Inbound traffic.(The default action for outbound traffic.�If this is true, administrators will be able to create firewall rules which allow unsolicited inbound traffic to be accepted.  If this is false, such rules will be ignored.tDetermines whether local firewall rules should be merged into the effective policy along with Group Policy settings.sDetermines whether local IPsec rules should be merged into the effective policy along with rules from Group Policy.WWhether to respect user allowed applications created in the legacy Windows XP firewall.SWhether to respect globally opened ports created in the legacy Windows XP firewall.8Whether to allow unicast responses to multicast traffic.UIf true, users will be notified when an application listens on a port that is closed.0The filename in which to store the firewall log.rMaximum size the log file can reach before being rotated.  May be a uint32 value, or MAXUINT64 for Not Configured.Whether to log allowed packets.Whether to log blocked traffic./Whether to log an event when rules are ignored.4Interfaces that the firewall profile is disabled on.8Whether to use Stealth Mode for IPsec-protected traffic.pRepresents a particular firewall profile. Multiple profiles may be in effect on any interface at any given time.The firewall profile.#The policy rule within the profile.?Indicates that a rule applies to a particular firewall profile.DA set of authentication proposals used in Phase 1 of authentication.0The Phase 1 Authentication Set used by the rule.8Relates an IPsec rule to its Phase 1 Authentication Set.3Represents a suite of crypto algorithms to propose.NA list of crypto suites, in preferential order, to use when negotiating an SA.$Diffie-Hellman Group to use with PFS
DH Group 1
DH Group 2DH Group 14DH Group 19DH Group 20DH Group 24�Specifies parameters for the quick mode negotiation as well as dictating the crypto sets that should be proposed during the exchange.,The Quick Mode crypto set used by this rule.3Relates an IPsec rule to its Quick Mode crypto set.@Relates a connection security rule to its Quick Mode Crypto Set./GUID ID which uniquely identifies this keyword.zName for this keyword. If the 'AutoResolve' flag is TRUE, then this should be a FQDN (i.e 'contoso.com' or '*contoso.com'.�A comma separated list of addresses, subnets, or ranges which this keyword represents. This must NOT be set if the 'AutoResolve' flag is TRUE.ETRUE if the 'Keyword' is a FQDN and should be resolved automatically.PThe type of PolicyStore where this dynamic keyword address originally came from.HThe PolicyStore where this dynamic keyword address originally came from.$Updates the dynamic keyword address. GUID ID of the keyword to updatePComma separated list of addresses, subnets, or ranges to update the keyword withlTRUE if the addresses should be appended to keyword's existing addresses, FALSE if it should overwrite them.JThis class represents a Windows Defender Firewall dynamic keyword address.�Whether to group UDP packets into conversations based upon the local address, local port, and remote port.  Applies only to UDP.qWhether to group UDP packets into conversations based only upon the local address and port.  Applies only to UDP.BSpecifies how this firewall rule will handle edge traversal cases.BlockAllow
Defer to UserDefer to App=Specifies which direction of traffic to match with this rule.InboundOutbound?Specifies the action to take on traffic that matches this rule.AllowBypass)The owner of the firewall rule, as a SID.[List of dynamic keyword address IDs to corresponding to the remote addresses for this rule.*Policy App Id corresponding for this rule.Desc,Represents a Windows Defender firewall rule.The firewall rule.�Associates a firewall rule with its filters.  Instances of this class can be traversed and the values in the associated filters can be modified, but instances of this class may not be created or deleted./Associates a FirewallRule to its AddressFilter.+The application filter applied to the rule.�Whether to require Authentication.  NoEncapsulation means that authentication is still required, but only once at the beginning of the traffic flow, instead of on every packet.NotRequiredRequiredNoEncapsulationPArWhether to require Encryption.  Dynamic encryption means that the first packet may be protected but not encrypted.Dynamic�Whether to allow this rule to take precedence over Block rules.  This setting may only be applied on Allow rules that require Authentication with specific RemoteUsers and/or RemoteMachines.9SDDL string describing Local Users that are allowed by this rule.  If this is empty, all users are allowed.  If LocalUsers/RemoteUsers/RemoteMachines are specified, then they apply conjunctively, and this is an ''Allow-Bypass'' rule and ProtectionLevel must be set above None (so that authentication is required).:SDDL string describing Remote Users that are allowed by this rule.  If this is empty, all users are allowed.  If LocalUsers/RemoteUsers/RemoteMachines are specified, then they apply conjunctively, and this is an ''Allow-Bypass'' rule and ProtectionLevel must be set above None (so that authentication is required).=SDDL string describing Remote Machines that are allowed by this rule.  If this is empty, all users are allowed.  If LocalUsers/RemoteUsers/RemoteMachines are specified, then they apply conjunctively, and this is an ''Allow-Bypass'' rule and ProtectionLevel must be set above None (so that authentication is required).�Filters traffic based on certain high-level security constraints, like whether or not the traffic is encrypted.  Connection Security rules will have to be created in order for traffic to pass the rule.(The security filter applied to the rule.-The short name of the service to be filtered.IFilters traffic based on which Windows service it is sent or received by.'The service filter applied to the rule.8Associates a firewall rule with a profile that it is in.�Specifies the proposed authentication. The list of methods was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list and aligns with the values in IKESAEndpoint.AuthenticationMethod.	AnonymousKerberos (machine as principal)NTLM (machine as principal)Kerberos (user as principal)NTLM (user as principal))X.509 Certificates (machine as principal)&X.509 Certificates (user as principal)#X.509 Certificates (machine health)�Represents an auth proposal.  Instances of this class only exist as embedded instances within a MSFT_NetIKEP1AuthSet and MSFT_NetIKEP2AuthSet./Only certs issued by this CA should be allowed.�Indicates whether to accept certificates only from the root TrustedCA, or to also accept certificates from Intermediate CA's which are children of the TrustedCA.Root CAIntermediate CAsIf this flag is set, certificate authority names are excluded. This flag MUST be set only on first authentications.QIf this flag is set, Windows will attempt to map certificates to domain accounts.3Specifies the certificate signing algorithm to use.RSA256-bit Elliptic-Curve DSA384-bit Elliptic-Curve DSA+The name that should be on the certificate."The type of name used in CertName.NoneDNSUPNRFC822CNOUODCThe EKU's to accept.The thumbprint to accept.&Whether to follow certificate renewal.pWhether the cert criteria (CertName, EKUs, Thumbprint) should be used when choosing which certificates to offer.pWhether the cert criteria (CertName, EKUs, Thumbprint) should be used for validating the certificates presented.�Represents an auth proposal that uses certificates to authenticate the remote peer.  Instances of this class only exist as embedded instances within a MSFT_NetIKEP1AuthSet and MSFT_NetIKEP2AuthSet.>The Kerberos proxy server to use when authenticating remotely.)Represents an auth proposal for Kerberos.4Require use of Diffie-Hellman for enhanced security.gThe maximum number of QM SA's that may be established using this MMSA before it must be re-established.SThe maximum amount of time that can elapse before this MMSA must be re-established.�For a Main Mode or Connection Security rule, sets parameters for the main mode negotiation and describes the crypto proposals that should be negotiated.,Specifies the proposed encryption algorithm.AES-128AES-192AES-256AES-GCM-128AES-GCM-192AES-GCM-256&Specifies the proposed hash algorithm.SHA-256SHA-384PAAES-GMAC-128AES-GMAC-192AES-GMAC-256�The property GroupId specifies the proposed phase 1 security association key exchange group. Well-known group identifiers from RFC2412, Appendix E, are: Group 1='768 bit prime', Group 2='1024 bit prime', Group 3 ='Elliptic Curve Group with 155 bit field element', Group 4= 'Large Elliptic Curve Group with 185 bit field element', and Group 5='1536 bit prime'.  Note that only groups 1, 2, 14, 19, 20, and 24 are acceptable in Windows 8.2Represents a crypto suite to propose in main mode.%The key to use in the authentication.)A Pre-shared Key authentication proposal.QThe maximum lifetime for a Quick-Mode SA before it must be rekeyed, in kilobytes.Hash algorithm to use in AH.Hash algorithm to use in ESP."What type of encapsulation to use.AHESPAH/ESPOThe maximum lifetime for a Quick-Mode SA before it must be rekeyed, in minutes.3Represents a crypto suite to propose in quick mode.PA%Superclass SettingData for networking6State entry idle timeout in seconds. Value must be > 0TPer internal IP address rate limit queue idle timeout in seconds.  Value must be > 0[DSCP (RFC 2474) marking for unauthenticated inbound IPv6 IPsec traffic. Value must be <= 63RPer internal IP address rate limit for unauthenticated inbound IPv6 IPsec traffic.ZDSCP (RFC 2474) marking for authenticated inbound IPv6 IPsec traffic. Value must be <= 63.8Rate limit for authenticated inbound IPv6 IPsec traffic.GDSCP (RFC 2474) marking for inbound ICMPv6 traffic. Value must be <= 63&Rate limit for inbound ICMPv6 traffic.VDSCP (RFC 2474) marking for inbound IPv6 filter exempted traffic. Value must be <= 63.4Rate limit for inbound IPv6 filter exempted traffic.XDSCP (RFC 2474) marking for inbound default-block exempted traffic. Value must be <= 63.6Rate limit for inbound default-block exempted traffic.@Maximum number of state entries in the table. Value must be > 0.~Maximum number of per internal IP address rate limit queues for inbound unauthenticated IPv6 IPsec traffic. Value must be > 0.Enabled keying modulesPAIkeV1IkeV2AuthIpFiltering flagsDisableDefaultBlockFilterBlockFilterExemptPublic network interfacesPrivate network interfacesKOptional public IPv6 address or subnet, for which this policy is specified.LOptional private IPv6 address or subnet, for which this policy is specified.'Address family(ies) currently protected0Denial of Service Prevention Settings for IPsec.Whether to enable stateful FTP.FalseTrue
NotConfigured Whether to enable stateful PPTP.8Current profile.  This is only valid in the ActiveStore.Not ApplicableXSpecifies which kinds of certificate problems should cause a certificate to be rejected.Attempt CRL CheckRequire CRL ChecktThe maximum length of time, in seconds, that an SA may be idle before it will be torn down.  0 means Not Configured.�When IPsec is in use, extra work is required to enable NAT traversal. This setting indicates on which side NAT traversal should be attempted.ServerBothHow to encode Pre-Shared Keys.UTF-16UTF-8Traffic exemptionsNeighborDiscoveryIcmpRouterDiscoveryDhcp4Opportunistically match full auth set per key module/SDDL for remote machine tunnel SA authorization,SDDL for remote user tunnel SA authorization2SDDL for remote machine transport SA authorization/SDDL for remote user transport SA authorization:Toggle IPSec queuing of packets for RSS-like functionalityReceiveForwardGlobal settings for IPsec.5The InstanceID of the CryptoSet to use for Main Mode.6The InstanceID of the CryptoSet to use for Quick Mode.6The InstanceID of the AuthSet to use for Phase 1 auth.6The InstanceID of the AuthSet to use for Phase 2 auth.=A rule that alters the behavior of main-mode authentications."The main mode rule being filtered.�Associates a main mode rule with its filters.  Instances of this class can be traversed and the values in the associated filters can be modified, but instances of this class may not be created or deleted.The main mode rule.;Relates a main mode rule to its Phase 1 Authentication Set.+The Main Mode crypto set used in this rule.2Relates an IPsec rule to its Main Mode crypto set.+The main mode crypto set used in this rule.5Relates a main mode rule to its Main Mode Crypto Set.ImpersonationTypeImpersonated+Authentication method used by this identity
Preshared keyCertificateKerberosSSLPANTLMV2CGACertificateEcdsa256CertificateEcdsa384SSLEcdsa256SSLEcdsa384EAPIdentity flagsHealthCertificateIdentityAn identity used by IPsec�A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details.The time that the Job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested.}The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval.�The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.VThe time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.PA�The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once.eThe month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.JanuaryFebruaryMarchAprilMayJuneJulyAugust	SeptemberOctoberNovemberDecember#The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth. 

When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.�A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay.PA	-Saturday-Friday	-Thursday
-Wednesday-Tuesday-Monday-SundayExactDayOfMonthSundayMondayTuesday	WednesdayThursdayFridaySaturday�The time interval after midnight when the Job should be processed. For example, 
00000000020000.000000:000 
indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.PA�This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time".
Local TimeUTC TimeThe time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely.BThe User who is to be notified upon the Job completion or failure.aThe User that submitted the Job, or the Service or method name that caused the job to be created.Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job.�The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property. 
Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.Percent�Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property.QA vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.0A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.�Describes the recovery action to be taken for an unsuccessfully run Job. The possible values are: 
0 = "Unknown", meaning it is unknown as to what recovery action to take 
1 = "Other", indicating that the recovery action will be specified in the OtherRecoveryAction property 
2 = "Do Not Continue", meaning stop the execution of the job and appropriately update its status 
3 = "Continue With Next Job", meaning continue with the next job in the queue 
4 = "Re-run Job", indicating that the job should be re-run 
5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.Do Not ContinueContinue With Next Job
Re-run JobPARun Recovery JobhA string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").EKillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction. 
A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.Success
Not SupportedTimeoutFailed
Access Denied	Not FoundVendor Specific�Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.�A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system.Primary classification of the error. The following values are defined: 
2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another. 
3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance. 
4 - Software Error. Error of this type are principally associated with a software or processing fault. 
5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure. 
6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations. 
7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues. 
8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation. 
9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource. 
10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.Communications ErrorQuality of Service ErrorSoftware ErrorPAHardware ErrorEnvironmental ErrorSecurity ErrorOversubscription ErrorUnavailable Resource ErrorUnsupported Operation Error[A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.kAn opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.7An array containing the dynamic content of the message.An enumerated value that describes the severity of the Indication from the notifier\'s point of view: 
0 - the Perceived Severity of the indication is unknown or indeterminate. 
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property. 
2 - Information should be used when providing an informative response. 
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 
5 - Major should be used to indicate action is needed NOW. 
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action. 
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.InformationMinorMajorCriticalPAFatal/NonRecoverableCAn enumerated value that describes the probable cause of the error.Adapter/Card ErrorApplication Subsystem FailureBandwidth ReducedConnection Establishment ErrorCommunications Protocol Error Communications Subsystem Failure!Configuration/Customization Error
CongestionCorrupt DataCPU Cycles Limit ExceededDataset/Modem ErrorDegraded SignalDTE-DCE Interface ErrorEnclosure Door OpenEquipment MalfunctionExcessive VibrationFile Format Error
Fire DetectedFlood Detected
Framing ErrorHVAC ProblemHumidity UnacceptableI/O Device ErrorInput Device Error	LAN ErrorNon-Toxic Leak DetectedLocal Node Transmission Error
Loss of FrameLoss of SignalMaterial Supply ExhaustedPAMultiplexer Problem
Out of MemoryOutput Device ErrorPerformance Degraded
Power ProblemPressure Unacceptable*Processor Problem (Internal Machine Error)Pump FailureQueue Size ExceededReceive FailureReceiver FailureRemote Node Transmission ErrorResource at or Nearing CapacityResponse Time ExcessiveRetransmission Rate Excessive&Software Program Abnormally Terminated*Software Program Error (Incorrect Results)Storage Capacity ProblemTemperature UnacceptableThreshold CrossedTiming ProblemToxic Leak DetectedTransmit FailureTransmitter FailureUnderlying Resource UnavailableVersion MismatchPrevious Alert ClearedLogin Attempts FailedSoftware Virus DetectedHardware Security BreachedDenial of Service DetectedSecurity Credential MismatchUnauthorized AccessAlarm ReceivedLoss of PointerPayload MismatchTransmission ErrorExcessive Error Rate
Trace ProblemElement UnavailableElement MissingLoss of Multi FrameBroadcast Channel FailureInvalid Message ReceivedRouting FailureBackplane FailureIdentifier DuplicationProtection Path FailureSync Loss or MismatchTerminal ProblemReal Time Clock FailureAntenna FailureBattery Charging FailureDisk FailureFrequency Hopping FailureLoss of RedundancyPower Supply FailureSignal Quality ProblemBattery DischargingBattery FailureCommercial Power ProblemFan FailureEngine FailureSensor FailurePAFuse FailureGenerator FailureLow BatteryLow Fuel	Low Water
Explosive Gas
High WindsIce BuildupSmokeMemory MismatchOut of CPU CyclesSoftware Environment ProblemSoftware Download FailureElement ReinitializedLogging Problems
Leak DetectedPAProtection Mechanism FailureProtecting Resource FailureDatabase InconsistencyAuthentication FailureBreach of ConfidentialityCable TamperDelayed InformationDuplicate InformationInformation MissingInformation ModificationInformation Out of SequenceKey ExpiredNon-Repudiation FailureOut of Hours ActivityOut of ServiceProcedural ErrorPAUnexpected Information>A free-form string describing the probable cause of the error.OA free-form string describing recommended actions to take to resolve the error.�The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.�The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as: 
0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application. 
1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
CIMObjectPath�A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.XThe CIM status code that characterizes this instance. 
This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation. 
The following values for CIM status code are defined: 
1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code. 
2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client. 
3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist. 
4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid. 
5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist. 
6 - CIM_ERR_NOT_FOUND. The requested object could not be found. 
7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported. 
8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances. 
9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances. 
10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist. 
11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists. 
12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist. 
13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type. 
14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported. 
15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language. 
16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed. 
17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist. 
18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected. 
19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid. 
20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty.
21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid.
22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty.
23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty.
24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed.
25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported.
26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported.
27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...).
28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down.
29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.CIM_ERR_FAILEDCIM_ERR_ACCESS_DENIEDCIM_ERR_INVALID_NAMESPACECIM_ERR_INVALID_PARAMETERCIM_ERR_INVALID_CLASSCIM_ERR_NOT_FOUNDCIM_ERR_NOT_SUPPORTEDCIM_ERR_CLASS_HAS_CHILDRENPACIM_ERR_CLASS_HAS_INSTANCESCIM_ERR_INVALID_SUPERCLASSCIM_ERR_ALREADY_EXISTSCIM_ERR_NO_SUCH_PROPERTYCIM_ERR_TYPE_MISMATCH$CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTEDCIM_ERR_INVALID_QUERYCIM_ERR_METHOD_NOT_AVAILABLECIM_ERR_METHOD_NOT_FOUNDCIM_ERR_UNEXPECTED_RESPONSE$CIM_ERR_INVALID_RESPONSE_DESTINATIONCIM_ERR_NAMESPACE_NOT_EMPTY#CIM_ERR_INVALID_ENUMERATION_CONTEXT!CIM_ERR_INVALID_OPERATION_TIMEOUTCIM_ERR_PULL_HAS_BEEN_ABANDONED CIM_ERR_PULL_CANNOT_BE_ABANDONED*CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED+CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTEDCIM_ERR_SERVER_LIMITS_EXCEEDEDCIM_ERR_SERVER_IS_SHUTTING_DOWN#CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED�A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.2.22.1�CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.>Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following \'preferred\' algorithm: 
<OrgID>:<LocalID> 
Where <OrgID> and <LocalID> are separated by a colon \':\', and where <OrgID> must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID, or that is a registered ID that is assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>. 
<LocalID> is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. If the above \'preferred\' algorithm is not used, the defining entity must assure that the resulting InstanceID is not re-used across any InstanceIDs produced by this or other providers for the NameSpace of this instance. 
For DMTF defined instances, the \'preferred\' algorithm must be used with the <OrgID> set to \'CIM\'.�The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.)�JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states: 
New (2) indicates that the job has never been started. 
Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state. 
Running (4) indicates that the Job is running. 
Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner. 
Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state. 
Completed (7) indicates that the job has completed normally. 
Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job. 
Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources. 
Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects. 
Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both.
Query pending (12) waiting for a client to resolve a queryNewRunning	Suspended
TerminatedKilledPA	ExceptionService
Query PendingThe date or time when the state of the Job last changed. If the state of the Job has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property. 
The default is five minutes.DRequests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost. 
If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.Completed with No ErrorUnknown/Unspecified Error&Can NOT complete within Timeout PeriodInvalid ParameterIn Use.Method Parameters Checked - Transition StartedInvalid State Transition&Use of Timeout Parameter Not SupportedBusyMethod ReservedPA�RequestStateChange changes the state of a job. The possible values are as follows: 
Start (2) changes the state to \'Running\'. 
Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.) 
Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner. 
Kill (5) terminates the job immediately with no requirement to save data or preserve the state. 
Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.StartSuspend	TerminateKill�A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition. 
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned.Unspecified Error�If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned.yA concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.�EnabledState is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following text briefly summarizes the various enabled and disabled states: 
Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests. 
Disabled (3) indicates that the element will not execute commands and will drop any new requests. 
Shutting Down (4) indicates that the element is in the process of going to a Disabled state. 
Not Applicable (5) indicates the element does not support being enabled or disabled. 
Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests. 
Test (7) indicates that the element is in a test state. 
Deferred (8) indicates that the element might be completing commands, but will queue any new requests. 
Quiesce (9) indicates that the element is enabled but in a restricted mode.
Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.Enabled but OfflineDeferredQuiesce�A string that describes the enabled or disabled state of the element when the EnabledState property is set to 1 ("Other"). This property must be set to null when EnabledState is any value other than 1.`RequestedState is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by EnabledState. This property is provided to compare the last requested and current enabled or disabled states. Note that when EnabledState is set to 5 ("Not Applicable"), then this property has no meaning. Refer to the EnabledState property description for explanations of the values in the RequestedState enumeration. 
"Unknown" (0) indicates the last requested state for the element is unknown.
Note that the value "No Change" (5) has been deprecated in lieu 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. 
It should be noted that there are two new values in RequestedState that build on the statuses of EnabledState. These are "Reboot" (10) and "Reset" (11). Reboot refers to doing a "Shut Down" and then moving to an "Enabled" state. Reset indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. Shut Down requests an orderly transition to the Disabled state, and might 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 shall be NULL or have the value 12 "Not Applicable".	Shut Down	No ChangeOfflineTestRebootReset�An enumerated value indicating an administrator\'s default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2).
No Default The date or time when the EnabledState of the element last changed. If the state of the element has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.�AvailableRequestedStates indicates the possible values for the RequestedState parameter of the method RequestStateChange, used to initiate a state change. The values listed shall be a subset of the values contained in the RequestedStatesSupported property of the associated instance of CIM_EnabledLogicalElementCapabilities where the values selected are a function of the current state of the CIM_EnabledLogicalElement. This property may be non-null if an implementation is able to advertise the set of possible values as a function of the current state. This property shall be null if an implementation is unable to determine the set of possible values as a function of the current state.Defer�TransitioningToState indicates the target state to which the instance is transitioning. 
A value of 5 "No Change" shall indicate that no transition is in progress.A value of 12 "Not Applicable" shall indicate the implementation does not support representing ongoing transitions. 
A value other than 5 or 12 shall identify the state to which the element is in the process of transitioning.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. 
A return code of 0 shall indicate the state change was successfully initiated. 
A return code of 3 shall indicate that the state transition cannot complete within the interval specified by the TimeoutPeriod parameter. 
A return code of 4096 (0x1000) shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job. Any other return code indicates an error condition.Unknown or Unspecified Error%Cannot complete within Timeout Period'Method Parameters Checked - Job StartedxThe state requested for the element. This information will be placed into the RequestedState property of the instance if the return code of the RequestStateChange method is 0 (\'Completed with No Error\'), or 4096 (0x1000) (\'Job Started\'). Refer to the description of the EnabledState and RequestedState properties for the detailed explanations of the RequestedState values.tMay contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.�A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition. 
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' shall be returned.�This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint.�The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the Description property of the object.,The CreationClassName of the scoping System.The Name of the scoping System.�CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available for other entities to use.4A string that identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method selected is described in the NameFormat property of this class.NameFormat contains the naming heuristic that is selected to ensure that the value of the Name property is unique. For example, you might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint (for example, IPv4) of this instance followed by an underscore.�Note: This property is deprecated in lieu of the ProtocolIFType enumeration. This deprecation was done to have better alignment between the IF-MIB of the IETF and this CIM class. 
Deprecated description: ProtocolType is an enumeration that provides information to categorize and classify different instances of this class. For most instances, information in this enumeration and the definition of the subclass overlap. However, there are several cases where a specific subclass of ProtocolEndpoint is not required (for example, there is no Fibre Channel subclass of ProtocolEndpoint). Therefore, this property is needed to define the type of Endpoint.IPX	AppleTalkDECnetSNACONPCLNPVINESXNSATMFrame RelayEthernet	TokenRingFDDI
Infiniband
Fibre ChannelISDN BRI EndpointISDN B Channel EndpointISDN D Channel EndpointIPv4/v6BGPOSPFPAMPLSUDPTCP�ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. The ifType MIB is maintained at the URL, http://www.iana.org/assignments/ianaiftype-mib. Also, additional values defined by the DMTF are included. The property is used to categorize and classify instances of the ProtocolEndpoint class. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property.Regular 1822HDH 1822DDN X.25RFC877 X.25Ethernet CSMA/CDISO 802.3 CSMA/CDISO 802.4 Token BusISO 802.5 Token Ring
ISO 802.6 MANStarLANProteon 10MbitProteon 80MbitPAHyperChannelLAP-BSDLCDS1E1
Basic ISDNPrimary ISDN!Proprietary Point-to-Point SerialPPPSoftware LoopbackEONEthernet 3MbitNSIPSLIPUltraDS3SIPRS-232ParallelARCNetARCNet PlusMIO X.25SONETX.25 PLEISO 802.211c	LocalTalkSMDS DXIFrame Relay ServiceV.35HSSIHIPPIModemPAAAL5
SONET PathSONET VT	SMDS ICIPProprietary Virtual/InternalProprietary MultiplexorIEEE 802.12HIPPI InterfaceFrame Relay InterconnectATM Emulated LAN for 802.3ATM Emulated LAN for 802.5ATM Emulated CircuitFast Ethernet (100BaseT)ISDNV.11V.36G703 at 64KG703 at 2MbQLLCFast Ethernet 100BaseFXChannelIEEE 802.11IBM 260/370 OEMI ChannelESCONData Link SwitchingISDN S/T InterfaceISDN U InterfaceLAP-D	IP SwitchRemote Source Route BridgingATM LogicalDS0PA
DS0 BundleBSCAsyncCombat Net RadioISO 802.5r DTRExt Pos Loc Report System AppleTalk Remote Access ProtocolProprietary ConnectionlessITU X.29 Host PADITU X.3 Terminal PADFrame Relay MPI	ITU X.213ADSLRADSLSDSLVDSLPAISO 802.5 CRFPMyrinetVoice Receive and TransmitVoice Foreign Exchange OfficeVoice Foreign Exchange ServiceVoice Encapsulation
Voice over IPATM DXIATM FUNIATM IMAPPP Multilink BundleIP over CDLCIP over CLAWStack to StackVirtual IP AddressMPCPAIP over ATMISO 802.5j Fibre Token RingTDLCGigabit EthernetHDLCLAP-FV.37X.25 MLPX.25 Hunt GroupTransp HDLCInterleave ChannelFAST Channel IP (for APPN HPR in IP Networks)CATV MAC LayerCATV Downstream
CATV UpstreamPAAvalon 12MPP SwitchTunnelCoffeeCircuit Emulation ServiceATM SubInterfaceLayer 2 VLAN using 802.1QLayer 3 VLAN using IPLayer 3 VLAN using IPXDigital Power LineMultimedia Mail over IPDTMDCN
IP ForwardingMSDSL	IEEE 1394IF-GSN/HIPPI-6400PADVB-RCC MAC LayerDVB-RCC DownstreamDVB-RCC UpstreamATM VirtualMPLS TunnelSRPVoice over ATMVoice over Frame RelayISDLComposite LinkSS7 Signaling LinkProprietary P2P Wireless
Frame ForwardRFC1483 Multiprotocol over ATMUSBIEEE 802.3ad Link AggregatePABGP Policy AccountingFRF .16 Multilink FRH.323 GatekeeperH.323 ProxyMulti-Frequency Signaling LinkHDSL-2S-HDSLDS1 Facility Data LinkPacket over SONET/SDH
DVB-ASI InputDVB-ASI Output
Power Line!Non Facility Associated SignalingTR008	GR303 RDT	GR303 IDTISUPProprietary Wireless MAC LayerProprietary Wireless DownstreamProprietary Wireless UpstreamHIPERLAN Type 28Proprietary Broadband Wireless Access Point to MulipointSONET Overhead Channel Digital Wrapper Overhead ChannelATM Adaptation Layer 2	Radio MAC	ATM RadioInter Machine TrunkMVL DSL
Long Read DSLFrame Relay DLCI EndpointATM VCI EndpointPAOptical ChannelOptical TransportProprietary ATMVoice over CableTE LinkQ.2931Virtual Trunk GroupSIP Trunk Group
SIP SignalingCATV Upstream ChannelEconetFSAN 155Mb PONFSAN 622Mb PONTransparent Bridge
Line GroupVoice E&M Feature GroupPAVoice FGD EANA	Voice DIDMPEG Transport6To4GTPParadyne EtherLoop 1Paradyne EtherLoop 2Optical Channel GroupHomePNAGFPciscoISLvlanactelisMetaLOOPFcip
IANA Reserved802.11a802.11bPA802.11g802.11hNFSCIFSDAFSWebDAVHTTPFTPNDMPTelnetSSHSM CLPSMTPLDAPRDPHTTPSPA�A string that describes the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other). This property should be set to null when the Type property is any value other than 1.�A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks.2.15.0?InstallDate records when the SA (and its endpoint) was created.�LifetimeSeconds specifies the maximum time that the SA will be considered valid after it has been created. A value of zero indicates that the default of 8 hours be used. A non-zero value indicates the seconds lifetime.�RefreshThresholdSecondsPercentage is the lifetime percentage after which a new SA should be acquired, before the existing SA expires. A random period may be added to a calculated threshold to reduce network thrashing.�IdleDurationSeconds specifies how long the SA can be idle before it is deleted. The default value, 0, indicates that there is no idle timeout period.:LifetimeKilobytes specifies the maximum number of kilobytes of data traffic to be protected by the SA. A value of zero (the default) indicates that there should be no maximum kilobyte lifetime. A non-zero value specifies the desired kilobyte lifetime. The SA is deleted when the LifetimeKilobyte value is exceeded.�RefreshThresholdKbytesPercentage is the lifetime percentage of kilobytes processed, at which a new SA should be acquired. A random value may be added to the calculated threshold to reduce network thrashing.SPacketLoggingActive causes a log to be kept of traffic processed by the SAEndpoint.{SecurityAssociationEndpoint (SAEndpoint) represents the endpoint of a secure connection. This is typically an IP connection, although the model allows more flexibility than just IP. The SecurityAssociationEndpoint is tied to an IPProtocolEndpoint (or possibly other endpoint) using the LogicalIdentity association. Note that an endpoint is defined at both ends of the connection.�Identifier of the IKE phase 1 negotiation initiator. Combined with the ResponderCookie, this value, in string form, may be used to construct the value of the key field \'Name\', inherited from ServiceAccessPoint.�Identifier of the IKE phase 1 negotiation responder. Combined with the InitiatorCookie, this value, in string form, may be used to construct the value of the key field \'Name\', inherited from ServiceAccessPoint.CipherAlgorithm is an enumeration that specifies the encryption algorithm used by the IKESAEndpoint. The list of algorithms was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list, since the values of Unknown and Other are taken into account.HashAlgorithm is an enumeration that specifies the hash function used by the IKESAEndpoint. The list of algorithms was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list, since the values of Unknown and Other are taken into account.AuthenticationMethod is an enumeration that specifies the operation of the IKESAEndpoint. The list of methods was generated from Appendix A of RFC2409. Note that the enumeration is different than the RFC list, since the values of Unknown and Other are taken into account.PA�GroupId specifies the key exchange group ID. If the GroupID number is from the vendor-specific range (32768-65535), the VendorID qualifies the group number. Well-known group identifiers from RFC2412, Appendix E, are: Group 1=\'768 bit prime\', Group 2=\'1024 bit prime\', Group 3= \'Elliptic Curve Group with 155 bit field element\', Group 4= \'Large Elliptic Curve Group with 185 bit field element\', and Group 5=\'1536 bit prime\'.�IKESAEndpoint is created in the first phase of SA negotiation and protects the key negotiation traffic. This endpoint is only created when IKE is the key exchange protocol. Other protocols and their endpoints will be defined in a future release./The actual encryption algorithm used by the SA.)The actual hash algorithm used by the SA.�The property GroupId gives the phase 1 security association key exchange group. Well-known group identifiers from RFC2412, Appendix E, are: Group 1='768 bit prime', Group 2='1024 bit prime', Group 3 ='Elliptic Curve Group with 155 bit field element', Group 4= 'Large Elliptic Curve Group with 185 bit field element', and Group 5='1536 bit prime'.  Note that only groups 1, 2, 14, 19, 20, and 24 are acceptable in Windows 8.;The Key Module used to negotiate the SA and its child SA's.4The address of the local endpoint the SA applies to.5The address of the remote endpoint the SA applies to.jThe maximum number of Quick Mode SA's that may be established with this SA before it must be renegotiated.'The first authentication local identity(The second authentication local identity(The first authentication remote identity)The second authentication remote identityExtensions to GroupId>Filter ID from the QM policy matching the extended mode filter&Local UDP encapsulation port for NAT-T'Remote UDP encapsulation port for NAT-TFGUID of the main mode policy provider context corresponding to this SA.ID/Handle to virtual interface tunneling stateA MainMode SA.�SPI contains the Security Parameter Index of the SA. This value in string form may also be used in the key field \'Name\' inherited from ServiceAccessPoint.`InboundDirection specifies whether the SA applies to inbound (TRUE) or outbound (FALSE) traffic._EncapsulationMode indicates whether the IPsecSAEndpoint uses transport or tunnel encapsulation.	TransportVDFHandling controls how the \'Don\'t Fragment\' bit is managed by the IPsecSAEndpoint.(Copy from Internal to External IP Header"Set DF Bit in External Header to 1"Set DF Bit in External Header to 0TPFSInUse indicates whether perfect forward secrecy is required when refreshing keys.�IPsecSAEndpoints are types of SecurityAssociationEndpoints representing both negotiated and static SAs that correspond to AH, ESP, or IPCOMP transforms.=The local machine port the SA applies to, or 0 for all ports.>The remote machine port the SA applies to, or 0 for all ports.If traffic type is transport mode, this is the LUID of the FWPS transport layer filter corresponding to this traffic. If traffic type is tunnel mode, this is the LUID of the associated QM policy. In tunnel mode, this represents the QM traffic selectors for the tunneleIP protocol for this traffic.  Only specified if the traffic is more general than the matching filterLocal interface aliasqThe profile ID corresponding to the actual interface that the traffic is going out on or coming in from the wire..Local Udp encapsulation port for NAT traversal/Remote Udp encapsulation port for NAT traversalSA FlagsNdSecure
NdBoundaryNdPeerNatBoundaryGuaranteeEncryptionNLBNoMachineLuidVerifyNoImpersonationLuidVerifyNoExplicitCredMatchAllowNullTargetNameMatchPAClearDfOnTunnelAssumeUdpContextOutboundNdPeerBoundarySuppressDuplicateDeletionPeerSupportsGuaranteeEncryptionForceInboundConnectionsForceOutboundConnectionsForwardPathInitiator%Name of the matching transport filterId of the associated Main ModeFirst Transform typeAhEsp-auth
Esp-cipherEsp-auth-and-cipherEsp-auth-firewallPA/The integrity algorithm for the first operation,The cipher algorithm for the first operationSecond Transform type0The integrity algorithm for the second operation-The cipher algorithm for the second operationThe spi for the first operation"Private address of peer behind NAT Perfect forward secrecy group idSame as Main ModeJLUID of the FWPS_LAYER_IPSEC_XX layer FWPS filter corresponding to this SALiftime by number of packetspTimeout after which the IPsec SA should stop accepting packets coming in the clear in negotiation discovery mode!Network Access Protection context*Identifier for tiebraking simultaneous SAs$ID/Handle to Virtual-IF tunnel state+ID/Handle to Virtual-IF traffic selector(s)PAMain Mode target SPNExtended Mode target SPN'Optional handle to explicit credentialsA Quick Mode SA.AAntecedent represents the independent object in this association.DDependent represents the object that is dependent on the Antecedent.kCIM_Dependency is a generic association used to establish dependency relationships between ManagedElements.�Phase 1 SAEndpoint that protected the negotiation of the phase 2 Security Association. An example of a phase 1 endpoint is an IKESAEndpoint.The phase 2 SAEndpoint.�Phase1SAUsedForPhase2 associates a phase 1 endpoint (such as an IKESAEndpoint) with an IPsecSAEndpoint that was negotiated using that phase 1 Security Association.%Read a GPO, and cache results locallyOutput GPO Session identifier*Write the local cached GPO info back to ADbThis class does not have any instances.  It is used to manage locally-cached Group Policy Objects.PA%�The IPsec DoSP settings are corrupt for the NetIPsecDoSPSetting WMI Object with name: %1

Please use %2 to restore them.

8Fragment grouping must be enabled in order for DoSP settings to function correctly.   

Please run these commands to enable fragment grouping.

%1

%2

tAt least one server or domain name must be specified.

XThe specified EndpointType is invalid.

�This edition of Windows does not support the requested functionality.

%1 %2: %3

$%1-%2 %3: %4

Cannot access the remote domain %1.  This may be caused by not having credentials configured for multiple hops over the network.

\The OutboundSecurity/InboundSecurity combination is invalid.  Acceptable values for transport mode are None/None, Request/Request, Request/Require, and

Require/Require.

,The OutboundSecurity/InboundSecurity combination is invalid.  Acceptable values for tunnel mode are None/None, Require/Require, and None/Require.

xThe Authentication/Encryption combination is invalid.  Acceptable values are:

NotRequired/NotRequired

Required/Required

Required/NotRequired

Required/Dynamic

NoEncap/NotRequired

@The Key Module is invalid.

�A local tunnel endpoint can only be an IPv4 address and/or an IPv6 address.  Subnets and ranges are not allowed.

�A remote tunnel endpoint can only contain addresses. Subnets and ranges are not allowed.

�Tunnel mode properties cannot be applied to transport-mode rules.

�User and machine authentication may only be applied to Allow rules.

(The run-time type of the field does not match the declared type.  This indicates that the

provider is incorrectly registered in the WMI store.

�An error occurred while retrieving information about the Group Policy container from the Domain Controller.

4Invalid Parameter: %1

<Unable to parse the GUID.

�Unable to parse Platform string.  The format is X[.Y][+], where X is the OS major version, and Y is an

optional minor version.  + means "or greater".  For example, these are valid platform strings: 6, 6.0, 6.0+

�The address is invalid.  Addresses may be specified as IP addresses, ranges, or subnets.  Also, the following address keywords are allowed in certain places: LocalSubnet, DNS, DHCP, WINS, DefaultGateway, Internet, Intranet, IntranetRemoteAccess, PlayToDevice.  Keywords can be restricted to IPv4 or IPv6 by appending a 4 or 6.

�The port is invalid.  When Protocol is TCP or UDP, individual ports or ranges are allowed.  Also, the following port keywords are allowed on Firewall Rules: RPC, RPCEPMap, Teredo, IPHTTPSIn, IPHTTPSOut, PlayToDiscovery.

<The protocol is invalid.

�ICMP Type:Code pairs are only supported in Firewall rules.

�The default object %1 is not present in the current store.    To find this object, execute the query against the %2.

tThe specified interface was not found on the system.

�The ICMP type/code entry is invalid.  When Protocol is ICMPv4 or ICMPv6, type:code pairs are allowed.

�When specifying Auth or Crypto Sets, you must use the Name of the set.  You cannot pass the object directly.

pDynamicTransport is only valid for firewall rules.

DThe key encoding is invalid.

TThe cert validation level is invalid.

`The IPsec NAT traversal setting is invalid.

0The ID is invalid.

TThe packet queuing flags are invalid.

LRemoteAddress must be specified.

xBoth IP addresses must be from the same address family.

�4VS_VERSION_INFO��
4aJ
4aJ?StringFileInfo�040904B0LCompanyNameMicrosoft Corporationj!FileDescriptionNetwork Management Value Objectsn'FileVersion10.0.19041.3636 (WinBuild.160101.0800)8InternalNamewfascim.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.HOriginalFilenamewfascim.dll.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.3636DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD