| CIM_FileSpecification | |||
| A CIM_FileSpecification identifies a file that is either to be on or off the system. The file is to be located in the directory identified by the CIM_DirectorySpecificationFile associations. When the invoke() method is used, it is expected that it will use the combination of information provided to check for the file existence. Therefore, any of the properties with a NULL value are not checked. So, if only the Name and the MD5 properties have values, they are the only ones consider by the invoke() method. | |||
| NameSpace Path | |||
| \ROOT\CIMV2 | |||
| PROPERTY | SMS_REPORT | CIMTYPE | DESCRIPTION |
| Caption | String | NA | |
| CheckID | String | An identifier used in conjunction with other keys to uniquely identify the check | |
| CheckMode | Boolean | The CheckMode property is used to indicate whether the condition is expected to exist or not exist in the environment. When the value is True, the condition is expected to exist (e.g., a file is expected to be on a system) so invoke() is expected to return True. When the value is False, the condition is not expect to exist (e.g., a file is not to be on a system) so invoke is expected to return false | |
| CheckSum | UInt32 | The Checksum property is a checksum calculated as the 16-bit sum of the first 32 bytes of the file. | |
| CRC1 | UInt32 | The CRC1 property is the CRC value calculated using the middle 512K bytes. | |
| CRC2 | UInt32 | The CRC2 is the CRC value for the middle 512K bytes with a offset modulo 3 to the start of the file of zero. | |
| CreateTimeStamp | DateTime | The creation date and time of the file. | |
| Description | String | A description of the objects. | |
| FileSize | UInt64 | NA | |
| MD5Checksum | String | The MD5 algorithm is a well-known algorithm for computing a 128-bit checksum for any file or object. The likelihood of two different files producing the same MD5 checksum is very small (about 1 in 2^64), and as such, the MD5 checksum of a file can be used to construct a reliable content identifier that is very likely to uniquely identify the file. The reverse is also true. If two files have the same MD5 checksum, it is very likely that the files are identical. For purposes of MOF specification of the MD5 property, the MD5 algorithm always generates a 32 character string. For example: The string abcdefghijklmnopqrstuvwxyz generates the string c3fcd3d76192e4007dfb496cca67e13b. See http://www. rsa.com/pub/rfc1321.txt for details on the implementation of the MD5 algorithm. | |
| Name | String | Either the name of the file or the name of the file with a directory prefix. | |
| SoftwareElementID | String | This is an identifier for this software element. | |
| SoftwareElementState | UInt16 | The software element state of a software element | |
| TargetOperatingSystem | UInt16 | The target operating system of the this software element. | |
| Version | String | Version should be in the form | |
| SAMPLE DATA INSTANCE | |||
|    [LOCALE(1033): ToInstance Amended]    instance of Win32_FileSpecification    {     Attributes = 16384;     Caption = "APP_CO~1.COM|App_Code.compiled";     CheckID = "_7B2A1A4406624BE891C71DC7B9F5B70D{32DB53E1-DB00-4AA8-AAC8-AF1C781F3B19}";     Description = "APP_CO~1.COM|App_Code.compiled";     FileSize = "180";     Name = "_40FB87EF79E36E336199B56E07230D23";     Sequence = 4;     SoftwareElementID = "{40FB87EF-F79E-36E3-3619-9B56E07230D2}";     SoftwareElementState = 2;     TargetOperatingSystem = 19;     Version = "5.9.7.2";    }; | |||