Windows Server 2008
- The CIM_ReplacementSet class aggregates physical elements that must be 'replaced' or 'FRUed' together. For example, when ...
- The CIM_Sensor class represents a hardware device capable of measuring the characteristics of some physical property - for ...
- The CIM_Setting reference represents the role of the CIM_Setting object of the CIM_ElementSetting association. Role: The ...
- The CIM_SoftwareElement class is used to decompose a CIM_SoftwareFeature object into a set of individually manageable or ...
- The CIM_SoftwareElementVersionCheck class specifies a type of software element that must exist in the environment. This check ...
- The CIM_SoftwareFeature class defines a particular function or capability of a product or application system. This class ...
- The CIM_SoftwareFeatureSoftwareElements associations identifies the software elements that make up a particular software ...
- The CIM_SwapSpaceCheck class specifies the amount of swap space that needs to be available on the system. The amount is specified ...
- The CIM_System object and its derivatives are top level objects of CIM. They provide the scope for numerous components. Having ...
- The CIM_SystemResource class is an entity managed by BIOS and/or an operating system which is available for use by software ...
- The CIM_TapeDrive class represents a tape drive on the system. Tape drives are primarily distinguished by the fact that they ...
- The CIM_ToDirectoryAction association identifies the target directory for the file action. When this association is used, ...
- The CIM_ToDirectorySpecification association identifies the target directory for the file action. When this association is ...
- The CIM_USBController antecedent reference represents the Universal Serial Bus (USB) controller associated with this device. ...
- The CIM_VersionCompatibilityCheck class specifies whether it is permissible to create the next state of a software element. ...
- The CIM_VideoSetting class associates the CIM_VideoControllerResolution setting object with the controller to which it applies. ...
- The class ID of the proxy stub DLL for the interface is not available, or failed to load the proxy stub DLL, or failed to ...
- The ClassGuid property contains the Globally Unique Identifier (GUID) that uniquely identifies this Plug and Play device. ...
- The clean up operation was successfully initiated, but did not complete within the specified time. It is still running and ...
- The Client Access License (CAL) limit was reached. This server is unable to serve more clients. This may lead to messaging ...
- The Client Access Point is not yet available. This may be due to network propagation delays, please try Refresh after a few ...
- The client at %1 has sent an invalid response. The client cannot be removed from quarantine. You might want to enable logging ...
- The client can't connect because it doesn't support FIPS encryption level. Please lower the server side required security ...
- The client cannot connect to the remote host specified in the request. Verify that the service on the remote host is running ...
- The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact ...
- The client certificate exceeded the maximum size allowed by the WinRM service. User Action Please use a different client ...
- The client certificate for the user %1\%2 is not valid, and resulted in a failed smartcard logon. Please contact the user ...
- The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the ...
- The client could not connect. You are already connected to the console of this computer. A new console session cannot be ...
- The client could not establish a connection to the remote computer. The most likely causes for this error are: 1) Remote ...
- The client credentials are valid, but claims could not be produced because a Lightweight Directory Access Protocol (LDAP) ...
- The client credentials are valid, but claims could not be produced because a Lightweight Directory Access Protocol (LDAP) ...
- The client credentials are valid, but claims could not be produced because the user is from a Windows NT 4.0 domain. %18 ...
- The client credentials are valid, but one or more claims could not be produced. The syntax of a Lightweight Directory Access ...
- The client credentials are valid, but one or more claims could not be produced. The syntax of a Lightweight Directory Access ...
- The client credentials could not be verified because multiple Lightweight Directory Access Protocol (LDAP) objects were found ...
- The client credentials could not be verified because multiple Lightweight Directory Access Protocol (LDAP) objects were found ...
- The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) connection error. ...
- The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) connection error. ...
- The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) error. Account store ...
- The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) error. The error string ...
- The client credentials could not be verified because searching is not supported for this Lightweight Directory Access Protocol ...
- The client credentials could not be verified because searching is not supported for this Lightweight Directory Access Protocol ...
- The client credentials could not be verified because the Lightweight Directory Access Protocol (LDAP) distinguished name ...
- The client credentials could not be verified because the Lightweight Directory Access Protocol (LDAP) distinguished name ...
- The client credentials could not be verified because the user's Lightweight Directory Access Protocol (LDAP) object could ...
- The client credentials could not be verified because the user's Lightweight Directory Access Protocol (LDAP) object could ...
- The client credentials were verified by Active Directory Domain Services, but claims could not be produced because the user's ...
- The client credentials were verified by Active Directory Domain Services, but claims could not be produced because the user's ...
- The client credentials were verified with Active Directory Domain Services, but an error was encountered when extracting ...
- The client credentials were verified with Active Directory Domain Services, but an error was encountered when extracting ...
- The client does not belong to the same Message Queuing enterprise. This error can occur only in a mixed-mode environment. ...
- The client has failed to validate the Domain Controller certificate for %2. The following error was returned from the certificate ...
- The Client IP Address condition specifies the IP address of the RADIUS client that forwarded the connection request to NPS. ...
- The Client IPv6 Address condition specifies the IPv6 address of the RADIUS client that forwarded the connection request to ...
- The client made an unexpected and illegal sequence of calls, such as calling EndEnumeration before calling BeginEnumeration. ...
- The Client page cannot be displayed. Message Queuing may not be properly installed. Please reinstall Message Queuing using ...
- The client presented a certificate that could not be mapped to an Active Directory Domain Services user account. Error code: ...
- The client presented a valid inbound token as evidence. Depending on the audit policy, further details of this token may ...
- The client presented a valid inbound token as evidence. Depending on the audit policy, further details of this token may ...
- The client presented a valid inbound token as evidence. Token ID: %4 Issuer: %5 Audience: %6 Effective time: %7 %8 Expiration ...
- The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
- The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
- The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
- The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
- The client presented a valid logon accelerator token as evidence. Depending on the audit policy, further details of this ...
- The client presented a valid logon accelerator token as evidence. Depending on the audit policy, further details of this ...
- The client presented a valid XML token, and a Windows NT token was created successfully. Token ID: %4 Issuer: %5 Identity: ...
- The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither a ...
- The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither user ...
- The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
- The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
- The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
- The client presented a valid XML token, but an error occurred when generating a Windows NT token from the Active Direcotry ...
- The client presented an invalid inbound token as evidence. Ensure that a verification certificate corresponding to the token-signing ...