1 of 1 people found this helpful
The problem here is that the attribute is a 'STRING' data type and not DATETIME... This means that it is almost impossible to normalize or use in a search... How are you going to know if 1/8 is 1 august or 8 January...?
Do you re-image devices and insert the old device-id? If you don't, a new LANDESK record is created and you can use the Computer.Record Creation Date. Otherwise it might be useful to create a custom field and fill this during your Provisioning Process.
I see. The value is probably formatted as in the computer's regional settings...
Thanks for the hint to Computer.Record Creation Date. As we installed a new Server recently, lots of clients have a very recent Record Creation Date, which is to far away from the real installation date. But for the future, this value will be useful.
I learned, that this Date is available through various ways. For example:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\InstallDate (REG_DWORD in seconds from 1.1.1970). Can anyone tell us, from which source the Inventory scanner pulls that information?
In this case....
Add this regkey in customscanner and put it into your clients inventory
And then use ldda to convert this timestamp in an normal Date.
You can use vbscript in ldda calculate Rule to convert it into Time and Date.
And you can simple create two new inventory fields with ldda. Dont use unmodeled Data
Best regards MHO
Thanks for the suggestion. We used a WMI query to get the date and then chose DTS -> SQL to convert the date.