Get access to immediate incident response assistance.
Eliminate active threats with 24/7 threat detection, investigation, and response.
Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.
Advance your cybersecurity program and get expert guidance where you need it most.
Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.
Prevent unauthorized access and exceed compliance requirements.
Stop email threats others miss and secure your organization against the #1 ransomware attack vector.
Prepare for the inevitable with 24/7 global breach response in-region and available on-site.
Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.
The server will unpack the files into the default update location so that clients can find the update as expected. The default location is http://{mobile Server host/ip}:81/mobile_client_updates. To verify that your update files have been posted, go to the file latest-manifest.mcxml in this directory. Clients read this file to determine if applicable updates are available.
When the MCU reads available update information, it gives priority to new versions of the software. If a new version of the Mobile Client is available, it is downloaded and installed. Since the updated package contains an embedded copy of the latest configuration, this is adequate to ensure both the software and the configuration are updated. However, if the MCU finds no new software available, it checks to see if a new configuration is available. If the latter is available, that is downloaded and applied. Such updates are much smaller in size than updating an entire new version of the Mobile Client.
To contact Trustwave about this article or to request support: