Movere has three different mechanisms for uploading payloads. The preferred method is to upload directly from the endpoints, reaching the internet over port 443 outbound.
In the event that internet connectivity on the endpoint is unavailable, or automatic uploading will not be utilized, the endpoint can send payloads back to the console device over port 443, (port 443 outbound and inbound must be opened on the Console machine).
If Movere encounters the situation where port 443 is blocked, there is a third mechanism to return an inventory payload!
The scenario here is that an inventory scan has been requested but uploading to the cloud from the endpoint is not enabled or possible, and sending the payload from the endpoint to the console machine over port 443 is also not allowed. In this case, the console will wait for exactly 2 minutes and then pull the inventory payload back from the target. Even if port 443 is blocked! You will see a "pulling" message in the Log.Service file indicating that the payloads are retrieved:
This option is not currently possible for ARC payloads, which is why Movere requires either automatic uploading to the cloud over 443 or inbound traffic over 443 to the Console device when uploading payloads from the Console, (the Console machine must have internet connection when uploading payloads back from the endpoint).
Note: Uploading of ARC payloads is time-sensitive. Movere does enable manual uploading of ARC payloads, but any payloads that are uploaded more than 24 hours after payload generation will not be processed. These payloads will show successful uploading, but the data will no display on the web.