How to perform 'Silent Installation' of Applications Manager in Windows?

How to perform 'Silent Installation' of Applications Manager in Windows?

Follow the steps given below to perform the silent installation in Windows:

1. To perform silent installation/uninstallation, a response file needs to be created first. To create a response file, execute the below command:
Response file for Installation:
"<Path>ManageEngine_ApplicationsManager_64bit.exe" -a -r  -f1"<Path>Install.iss"
Response file for Uninstallation:
"<Path>ManageEngine_ApplicationsManager_64bit.exe" -a -r  -f1"<Path>Uninstall.iss"
where  <Path> refers to the path in which the response (.iss) file needs to be saved.

2. Now execute the installer along with the response file to do silent installation using the below command:
For silent installation:
"<Path>ManageEngine_ApplicationsManager_64bit.exe" -s -a -s -f1"<ISSPath>Install.iss" -f2"<LogPath>Install.log" 
For silent uninstallation:
"<Path>ManageEngine_ApplicationsManager_64bit.exe" -s -a -s -f1"<ISSPath>Uninstall.iss" -f2"<LogPath>Uninstall.log" 
where,
<Path> - Location of the installer (.exe) file.
<ISSPath> - Location of the response (.iss) file .
<LogPath> - Location where the log file needs to be created. -f2 is optional. By default, the log file will be created in the current execution directory.

After performing the above steps, a  setup.log file will be created in the specified location directory. The InstallShield places any one of the following return values after the ' ResultCode' key name, indicating the status of execution in the  setup.log file:
  1. 0 = Success
  2. -1 = General error
  3. -2 = Invalid mode
  4. -3 = Required data not found in the setup.iss file
  5. -4 = Not enough memory available
  6. -5 = File does not exist
  7. -6 = Cannot write to the response file
  8. -7 = Unable to write to the log file
  9. -8 = Invalid path to the InstallShield Silent response file
  10. -9 = Not a valid list type (string or number)
  11. -10 = Data type is invalid
  12. -11 = Unknown error during setup
  13. -12 = Dialogs are out of order
  14. -51 = Cannot create the specified folder
  15. -52 = Cannot access the specified file or folder
  16. -53 = Invalid option selected
For a successful installation, the log file should look similar to the example below:
[InstallShield Silent]
Version=v5.00.000
File=Log File

[Application]
Name=KiXscripts Editor
Version=1.10.000
Company=RWK Systems, Inc.

[ResponseResult]
ResultCode=0

                  New to ADSelfService Plus?

                    • Related Articles

                    • How to perform 'Silent Installation' of Applications Manager in Linux?

                      For silent installation, execute the installer (.bin) file using the below command in Linux: <Installation (.bin ) file>  -silent  -options ismp_silent.txt Example: .../AppManager15$ ./ManageEngine_ApplicationsManager_64bit.bin -silent -options ...
                    • Troubleshoot - RUM Agent silent installation

                      RUM Agent silent installation can fail on various factors based on your environment, troubleshoot with the help of error message shown while running the script. Below are the list of the error messages thrown from the script and its troubleshooting ...
                    • Installing Applications Manager in AWS

                      Applications Manager can be installed in EC2 instances in both Windows and Linux platforms.  Applications Manager comes with bundled PostgreSQL. Installing Applications Manager in EC2 for Windows Go to EC2 console and launch an "Windows" instance ...
                    • Installing Applications Manager in Cloud (AWS, Azure)

                      To install Applications Manager in the cloud, we can use any of the below methods: AWS/Azure marketplace Direct installation AWS/Azure marketplace Applications manager is readily available in AWS/Azure marketplace as a pre-installed product. AWS ...
                    • How to manually uninstall Applications Manager?

                      Windows Shut Down Applications Manager (Ensure that the ManageEngine ApplicationsManager service has been stopped if it has been installed as a Windows service) Open a command prompt with administrator privileges, navigate go to the <Applications ...