ScalePad Lifecycle Manager syncs assets from your integrations based on your chosen sync settings.

Fewer assets than expected

As your integration sync settings determine what syncs to Lifecycle Manager, you may want to review your sync settings to see if your settings are restricting any assets from syncing.

The most common reason why asset counts don't match with RMM integrations is that assets that haven't checked into the RMM within the 30/60/90 days (In the Only sync Assets checked-in within option) are excluded from the sync.

Duplicate assets
Lifecycle Manager can also show a lower asset count than your integrations due to duplicate assets. The reason for this is that our platform aggregates duplicate records based on a shared serial number or MAC address.

More assets than expected

If you see more assets in Lifecycle Manager than you have in your RMM or PSA tool, here are some possible causes.

  1. Do you have more than one Lifecycle Manager integration?
    If your team is using one integration, such as your RMM as the source of truth for asset counts, this will likely be different if you have a PSA, documentation tool, or any networking integrations. As RMM integrations only sync in managed agents, it's possible you're syncing assets into Lifecycle Manager that can't have an agent installed on them (SANs, VMWare hosts, network, mobile, and imaging assets), increasing your asset count.

    If this is the case, we recommend reviewing your sync settings to ensure you’re syncing only your preferred assets into Lifecycle Manager.

  2. Inactive assets syncing into Lifecycle Manager
    There may be inactive or stale assets syncing into Lifecycle Manager from your integrations that haven't been marked inactive yet. Once an asset is marked as inactive in one of your integrations, it will be removed from our platform.

    Our recommendation to resolve this issue would be to review your sync settings between your RMM and PSA so that the PSA and RMM automatically mark inactive devices when devices are flagged as inactive. Check with your RMM/PSA admin as they should be able to help with this.

    Similarly, if you have an integration with a documentation tool, you should make sure the PSA and documentation tool syncs to pass this inactive status over to the configuration in that tool.

    After this is complete, any other assets that are not automatically marked as inactive will need to be manually marked as such to stop syncing to Lifecycle Manager.

Did this answer your question?