Question: Synchronization times between Lansweeper Web and on-premise

[getuliodesousa]

Hi there,

I would like to know how long it takes for Lansweeper Web to synchronize with Lansweeper on-premise?

[Tim_N]

Hello @getuliodesousa 

The sync itself is very fast -- of course, depending on all of the activity of the Lansweeper infrastructure, etc. it could take longer, but in general, the sync is very fast. 

But, to be clear, not all components sync back to Lansweeper on-premise. Some components are cloud-only. For clarity, what are you noticing as not showing up in the On-Premise console? 

Looking forward to hearing from you. 

[mgraham]

What is "very fast"? At what point is the synchronization process for any scanned device started?

[Tim_N]

Hello @mgraham 

There are a few factors to dictate frequency of sync schedules. On one hand, it relies on the frequency of accessing and logging into the Lansweeper cloud platform.

Logging in monthly will pause syncing status and only update your site 1x per 24 hour period. 

Whereas logging in daily will sync more multiple times a day. 

A fresh install and new synchronization of a hub will trigger an immediate sync to ensure you are able to see all assets discovered. 

On the other hand, and to get more complex, there are other factors that could impact a sync... more specifically, updated asset information in the cloud. For example, a freshly patched Windows server. 

If Scanned Item Intervals for "quickfix" is configured for every 7 days (which is default), you may not see a change in the asset for 7 days. To resolve this, you can trigger a manual scan of that asset which will force a full 100% rescan. Or, you can change your "quickfix" interval to 1 (daily) or 0 (every scan). 

In short, to properly answer your exact need/question, I need a little more information. But I hope this brings a little more clarity for you. 

Tim

[getuliodesousa]

Hi there,

On-premise OK, but when I update a machine and do the rescan and then resync in the cloud, I saw that in the cloud it updates immediately, taking up to hours for the change in the cloud. I don't know exactly how long it took in hours. For example, I upgraded Ubuntu Server 22.04 to version 24.04 and after doing the rescan process and then resyncing in the cloud, the information in the cloud was not updated.

Note: I apologize for any typos, as I am using Google Translate.

[Tim_N · Accepted solution]

Ah, ok, that helped to clarify. 

To restated what I'm seeing -- you have an Ubuntu 22.04 that you recently update to 24.04. The new 24.04 is now showing after the asset is rescanned.

The re-scanning of the asset may not scan all of the information upon each and every scan. To ensure the asset is fully rescanned, manually trigger a re-scan of the one induvial asset. If you allow the asset to be re-scanned based on a scan target's schedule, the OS version may not be scanned. It *should* be scanned every time, but a schedule scan may only scan it 1x per day. Manually scanning will force a 100% re-scan of everything on that asset. 

See if that helps. Then, after it's scanned, it shouldn't take long to re-sync and update the cloud with the new OS version. 

Please keep us posted how things go for you.