When your hardware asset data syncs into Lifecycle Manager, your integrations might have different purchase and expiry dates from our warranty lookups. When this happens, Lifecycle Manager determines which date to show in the Final Summary.

Resolving conflicting dates

To err on the side of caution, Lifecycle Manager resolves each conflicting date as follows:

• Purchase Date resolves to the date furthest in the past
• Expiry Date resolves to the date furthest in the future

This resolved date is the one used in the Final Summary, our automated reporting, and in the Hardware console.

Writing dates back using Two-Way Sync

Two-Way Sync can only write back dates that come from a warranty lookup. Lifecycle Manager will never read a date from one of your integrations and then write it into another integration.

Refreshing warranty dates

Lifecycle Manager updates coverage data regularly. Expiry dates for Workstation Assurance and Infrastructure protection purchased through Lifecycle Manager display immediately.

In contrast, if you purchase a third-party or OEM warranty extension, the updated warranty may not appear. Our system has no way to determine the expiry date of a warranty purchased outside of Lifecycle Manager. OEM extended warranties can also take up to 30 days before they are refreshed and displayed in Lifecycle Manager.

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.

NEW Join our MSP Power-Ups - Free 15-minute micro-workshops + live Q&A with our Lifecycle Manager experts. Sign up here to reserve your spot.