There is a VBScript (Visual Basic Script) allow you to perform an unattended deployment of fusioninventory-agentwindows-.exe in large (. A new may contain improvements regarding the installer itself, the agent (patches) or both. Itâs possible to install fusioninventory-agentwindowsx86.exe on a 32-bit or 64-bit Microsoft Windows system but itâs only possible to install fusioninventory-agentwindowsx64.exe on a 64-bit Microsoft Windows system.
g-bougard released this Feb 22, 2019 · 297 commits to develop since this release
2.4.3 stable release
Official news: FusionInventory Agent 2.4.3
You'll find here distribution packages. See installation instructions here to install from sources.
Windows x86 & x64 installers are available below and are copied from windows x86 & x64 installers built thanks to appveyor project (see appveyor build log).
FusionInventory-Agent-2.4.3-1.pkg.tar.gz.sha256sum107 Bytes
FusionInventory-Agent-2.4.3.tar.gz.sha256sum101 Bytes
fusioninventory-agent_windows-x64_2.4.3-portable.exe8.02 MB
fusioninventory-agent_windows-x64_2.4.3.exe9.22 MB
fusioninventory-agent_windows-x64_2.4.3.exe.sha256149 Bytes
fusioninventory-agent_windows-x86_2.4.3-portable.exe7.58 MB
fusioninventory-agent_windows-x86_2.4.3.exe8.81 MB
fusioninventory-agent_windows-x86_2.4.3.exe.sha256149 Bytes
F.2.1 UNIX Systems: Creating the oraInst.loc FileThe Installer uses the Oracle inventory directory to keep track of all Oracle products installed on the systems. The inventory directory is stored in a file named oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation.Perform the following steps to create the oraInst.loc file if it does not exist:.Log in as the root user.Using a text editor such as vi or emacs, create the oraInst.loc file in any directory. The contents of the file consist of the following two lines:inventoryloc= ouiinventorydirectoryinstgroup= ouiinstallgroupReplace ouiinventorydirectory with the full path to the directory where you want the Installer to create the inventory directory. Replace ouiinstallgroup with the name of the group whose members have write permissions to this directory.Exit from the root user. F.3 Creating Response FilesBefore performing a silent installation, you must provide information specific to your installation in a response file.
Response files are text files that you can create or edit in a text editor. The Installer will fail if you attempt a silent installation using a response file that is not configured correctly.Several default response files, which you can use as templates and customize for your environment, are included in the installation media. Table F-1 Installer Command Line Parameters ParameterDescriptionInstallation Modes - Only One Mode Can be Specified-i -installLaunches the Installer in GUI mode. This is the default mode and is used if no mode is specified on the command line.-silentInstall in silent mode. The Installer must be passed either a response file or command line variable value pairs.-d -deinstallLaunches the Installer in GUI mode for deinstallation.-p -prerequisiteLaunches the Installer in GUI mode but only checks the prerequisites. No software is installed.-v -validateLaunches the Installer in GUI mode and performs all prerequisite and validation checking, but does not install any software.-sv -silentvalidatePerforms all prerequisite and validation checking in silent mode. You must pass the Installer either a response file or a series of command line variable value pairs.Installation Options-help -help -usageDisplays the usage parameters for the runInstaller command.-invPtrLoc filePointer to the inventory location file.
Replace file with the full path and name of the oraInst.loc file.-response file -responseFile filePointer to the response file. Replace file with the full path and name of the response file.-jreLoc locationPointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where your JRE is installed.-logLevel levelSpecify the level of logging performed by the Installer; all messages with a lower priority than the specified level will be recorded.
Valid levels are:.severe.warning.info.config.fine.finer.finest-debugObtain debug information from the Installer.-forceAllow the silent installation to proceed in a non-empty directory.-printdiskusageLog debugging information pertaining to disk usage.-printmemoryLog debugging information pertaining to memory usage.-printtimeLog debugging information pertaining to time usage. This command causes the timeTakentimestamp.log file to be created.-waitforcompletionWindows only - the Installer will wait for completion instead of spawning the Java engine and exiting.-noconsoleMessages will not be displayed to the console window.-ignoreSysPrereqsIgnore the results of the system prerequisite checks and continue with the installation.-executeSysPrereqsExecute the system prerequisite checks only, then exit.-paramFile fileSpecify the full path to the oraparam.ini file. This file is the initialization file for the Installer. The default location of this file is Disk1/install/platform.-novalidationDisables all validation checking performed by the Installer.-nodefaultinputFor the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated.Command Line VariablesInstaller VariablesInstaller variables are specified using varName= value. For example:ORACLEHOME=/scratch/install/IDMHomeSession VariablesSession variables are specified using session: varName= valueScripting on this page enhances content navigation, but does not change the content in any way.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |