InvGate Assets Installation Guide
InvGate Assets Installation Guide
InvGate Assets
Content
Introduction
Server requirements
Necessary files...................................................................................................................................3
Installation
Database configuration .........................................................................................................7
Access to the system.......................................................................................................................................8
Installation of the agente .9
2
Installation Guide | InvGate Assets
Introduction
In this simple manual we will see the necessary steps to install InvGate Assets.
Server requirements
The software must be installed on a server with the following specifications:
Static IP
Operating system: Windows Server 2008 or higher, Windows Vista or higher
Administrator privileges
Necessary files
In addition, you will need access to a database; if you do not have one, download this installer from
MySQL1to use it with the trial:
[Link]
1
InvGate Assets works with MySQL 5.5 to 5.7, and SQL Server 2012 or higher. To simplify the
installation process, we recommend using MySQL.
3
Installation Guide | InvGate Assets
Installation
Run the installer as administrator:
4
Installation Guide | InvGate Assets
3. Enter the port in 'Web Server Port' where the system will run (we recommend the
8420).
To check if the port is already in use, there are several ways; one of them is to open the console and
write
En el siguiente ejemplo vemos que el puerto 8080 está ocupado, ya que se encontró un proceso
that is using it. In contrast, port 8081 is free, as no process was found:
5
Installation Guide | InvGate Assets
4. Click on 'Install':
6
Installation Guide | InvGate Assets
Warning: If the message below appears at the end of the installation, it means that the port
the chosen one is occupied by another application. In that case, uninstall the application and reinstall it
in a free port.
Database configuration
You will be redirected to the following page, where you must enter the system password:
iG4p$yDbMf and click on 'Confirm'.
7
Installation Guide | InvGate Assets
Then, the system will redirect you to the next screen, where you can configure the new database.
data.
Note: If you do not have MySQL installed on your system, download it from the official site. Remember to save the
password of the user 'root', which will be required later.
To create a database in MySQL, it is enough to enter the Host, Port, User (root) data.
Enter the Password (root) for the engine, the name of the database that will be created, and then check "Create DB".
and 'Create Schema'.
Then, press the 'Test' button. If the icon changes to it means there is a problem
in the connection or with the data; if the icon changes to it means that there is a connection with the
the database engine and the user you entered has permissions to perform the action
indicated. If so, press 'SAVE' to create the database. If an error occurs, check the
entered information and repeat the process.
System access
User: admininvgate
Password: inventec
8
Installation Guide | InvGate Assets
Make sure that the system is receiving and processing the reports from the agents. All the
reports are located in the TempData folder in the Assets\Assets directory. Once that
All processed reports are finalized and deleted.
Agent installation
The InvGate Assets trial comes with a limited number of licenses and the agent must be installed.
manually on each device. In the acquired software, the installation of the agent is a
automated process.
To install the agent on a device, access InvGate Assets from that device (see
System Accesshigher up) and follow these steps:
3. Choose the guide for your device's operating system (Windows, macOS, or Linux) and follow
the instructions to complete the installation.
9
Installation Guide | InvGate Assets
10
Installation Guide | InvGate Assets
> cd /usr/local/invgate/assets/agent
Note: You must replace "IP" with the server's Host Name and "PORT" with the target port of the agent.
Debian/Ubuntu
apt-get update
11
Installation Guide | InvGate Assets
If you want to install the agent in version 5, run the following commands:
wget --directory-prefix=/etc/[Link].d/
[Link]
Warning: The InvGate Assets agent depends on the lshw package. The same
it is available in EPEL, but if you do not wish to add EPEL to your repositories, please install
lshw previously manually.
12
Installation Guide | InvGate Assets
SUSE/OpenSUSE
Warning: To execute the following installation, you must allow the repositories to
hardware install the package lshw.
zypper ar --repo
[Link]
po
13
Installation Guide | InvGate Assets
Configuration
When you have completed the installation, you need to configure the agent to report to
server. To do this, enter the server connection parameters in the file
/usr/local/invgate/bin/[Link]
For example:
IP=[Link]
PUERTO=80
You must replace '[Link]' with the server's Host Name and '80' with the address.
from the server's port.
Agent distribution
This method is useful for networks that have a domain controller, such as Active Directory in
Windows. This allows companies to distribute certain actions on a large scale through
of group policies (Group Policy Object or GPO), which means that the action will be loaded and
automatically executed on the Workstations.
To use a GPO, you first need to download the script [Link]. Remember to log in.
from a computer that belongs to the domain, but is not the server.
Go to the installation guide as we explainedpreviously, and download the script from the guide
Windows. Then, load it into the GPO by following these steps:
2. Right-click on the domain, then choose "Create a GPO in this domain and link it"
here...
14
Installation Guide | InvGate Assets
4. Go to 'Group Policy Objects', select the policy you just created, click
right and choose 'Edit':
15
Installation guide | InvGate Assets
5. This will open a new screen from which you must enter the Settings section of the
team → Windows Settings → Scripts (startup or shutdown):
It is possible that your Active Directory configuration is preventing the GPO from executing properly.
MSI file. If you have problems with the installation of the agent, check the Active configuration.
Directory.
16
Installation Guide | InvGate Assets
IP range distribution
In networks without a domain controller, such as SMEs with limited workgroups, it is not
it is possible to execute commands in bulk. In those cases, the distribution by IP could be a
alternative, as it allows listing all the Workstations or IP addresses where it will be installed
agent.
Este método requiere descargar y guardar el instalador en una carpeta compartida, a la que todos
the devices must have access. Then, create a list of all the IP addresses of the
workstations and execute a script that calls the installer. This also allows for setting
the IP and the port of the server to which the workstations will report.
It is important to ensure that all devices in the group have the same configuration.
some aspects. For example, access to the folder containing the installer.
Manual distribution
This method requires the same process explained above in theagent installation,
which varies according to the operating system. The scenario involves individual PCs within
the network that does not belong to a workgroup, so in this case, it needs to be downloaded and
run the agent from the VB script on Windows, the PKG on macOS, or the SH on Linux. Also
it is possible to install it manually with a USB memory.
This scenario involves PCs that are not part of the network yet or were not registered in the
domain, but they still belong to the organization. Therefore, the distribution is the same as
for individual PCs, that is, a manual process.
Warning: In all cases, there must be a connection between the server and the device on which
the agent is installed, which means they must be able to send and receive information between
Yes. Otherwise, if there is something like a firewall blocking the connection, the device does not
will report to the server.
17