NOTE: Please provide full access rights to the folder where you want to copy the backup.
Step 3: Save the hotfix from the link mentioned below,
Step 4: Run the script UpdateManager.sh in the <AssetExplorer-home>/bin folder. From the Update Manager tool click "Browse" to select the Service Pack file (ManageEngine_AssetExplorer_0_0_SP-x_0.ppm file that you had downloaded) and then click "Install...". Follow the on-screen instructions to apply the Service Pack / Hotfix.
Step 5: Once the upgrade is complete, start AssetExplorer Server.
Command line option to apply a patch in Linux
To install a patch from console or command line,
sh UpdateManager.sh -c
And it will guide the user through the steps.
Here are the other options:
sh UpdateManager.sh -u server/default/conf -c -option i -ppmPath <Patch file path including patch file name> -h <Product Home>
To un-install a patch: sh UpdateManager.sh -u server/default/conf -c -option u -h <Product Home> -version <Patch version>
To view installed patch versions: sh UpdateManager.sh -u server/default/conf -c -option v -h <Product Home>
To run UPDATEMANGER.bat from konsole mode: UpdateManager.sh -c -option i ppmPath <Path where PPM is downloaded> -h C:\ManageEngine\AssetExplorer
AssetExplorer, from version 6970 onwards, will only support TLS versions 1.3 and 1.2. The older protocols, such as TLSv1 and TLSv1.1 will not be supported going forward.
Mandatory configurations before moving to 6970:
Recommended configurations after upgrading to 6970:
Configuring Internet Settings for TLSv1.3 ( or TLSv1.2 ) in Server machine:
1. Get the assetexplorer.txt file available here.
2. Create a file called assetexplorer under /etc/init.d/ and copy the following script in it.
bcp assetexplorer.txt /etc/init.d/assetexplorer
3. Edit the file and modify the MDIR variable to the bin folder in the product directory. For example, MDIR=/home/guest/ManageEngine/assetexplorer/bin. To edit the file, type vi assetexplorer.txt on the Vim editor.
4. Get the Execute permission for assetexplorer startup script by using the command:
chmod +x assetexplorer
5. Create a blank file under /var/log for application login purposes by using the command: touch /var/log/assetexplorer.log.
6. To add the script as a startup process, use the command: systemctl start assetexplorer or service assetexplorer start.
You can download and Install AssetExplorer Probe in the remote network by downloading the exe file from the website below.
After installation when you start the application and connect to the client for the first time, it will prompt you to run either as a Central server or Probe (Remote server). Choose Remote server. You will be able to scan assets and perform scan configuration in Remote server as you do in AssetExplorer.
You can then export scanned Asset information from the Remote server under Admin -> Distributed Asset Scan. This will export the scanned Asset information as a zip file. These exported assets can be imported into your central AssetExplorer server under Admin --> Distributed Asset Scan.
By doing this we have a track of all our Assets in the organization in one place which makes it easier for us the manage them. Also Distributed asset scan functionality helps to reduce the load in AssetExplorer server.
Customers interested in using the Distributed scan feature can get the AssetExplorer Probe (Remote server) license from our licensing team (This license will be equivalent to the number of nodes purchased for AssetExplorer) which can be applied in the Asset explorer Remote server installations.
If AssetExplorer is installed in a Non - Windows server like say, Linux, then DC has to be installed manually in another Windows machine (as currently DC supports windows OS only). This DC installation has to be integrated with AE under Admin. Once integrated, agent deployment can be done from DC installation and refer the links below for more details.
By default DC would be installed in both HTTP and HTTPS mode. But when DC is integrated with AE, it uses HTTP mode. However, DC can be changed to the HTTPS mode .
Refer the link for more details.
If the old build is a different build, then the same build needs to be installed in new server. You can download earlier builds of from our Archives website https://archives.manageengine.com/asset-explorer/
You can download all versions of from our Archives website https://archives.manageengine.com/asset-explorer/
The way is designed is that it does not store attachments in the database. They are stored in the file attachments folder of the installation directory (C:\ManageEngine\AssetExplorer)
You would have to copy the following folders to the new server from the existing server in order to retain the file attachments.
Step 4: Copy the backup taken from the production server to the Test server.
Step 5: To restore the backed up data, Go to [AssetExplorer-Home]\bin directory and execute restoreData.bat. Choose the backup file while prompted as in the screen shot given below,
cmd> [ Home]\bin
cmd> restoreData.bat [ Screenshot ]
Step 6: Start the server once after restoring the data in the Test server.
Step 7: Stop mail fetching immediately after applying production data to your test server. You don't want it stealing emails that should be going into your production system. (Admin --> Mail server settings --> Stop fetching).
Was your question answered here?
Check the other FAQ modules or you can contact our support team at