When your hardware asset data syncs into Lifecycle Manager, your integrations may have different purchase and expiry dates to our vendor lookups. In this case, Lifecycle Manager may choose to report your dates in the Final Summary.
When dates conflict, we take action
To be cautious with purchase and expiry dates, this is what Lifecycle Manager does with each conflicting date:
-
Purchase Date will resolve to the date furthest in the past
-
Expiry Date will resolve to the date furthest in the future
The date in the Final Summary is used in our automated reporting, and on the Hardware page.
Writing dates back using Two-Way sync
To write dates to an integration using Two-Way Sync, they must be sourced from a vendor lookup. That said, Lifecycle Manager will not read a date from one of your integrations and then write it into another integration.
Refreshing warranty dates
Lifecycle Manager updates coverage data regularly. Coverage for Workstation Assurance and Infrastructure protection purchases displays immediately.
In contrast, if you purchase a third-party or OEM warranty extension, the updated warranty may not appear. This is because our warranty lookup frequency can extend up to 30 days.
Data is updated as often as possible while avoiding constant warranty checks on millions of assets. To balance these needs, we use a smart algorithm for each OEM that prioritizes assets likely to be renewed, ensuring up-to-date coverage information.