ALVAO Server - manual installation
Create a new database
- From the ALVAO downloads page, download the DatabaseDeploy.zip file.
- Extract the ZIP package to any folder on the disk.
- Check that you have permission to create a new database on the target SQL Server.
- Use the DatabaseDeploy utility to create a new database.
ALVAO Asset Management Collector
Service Installation Guide
- On the server where you want to run the Collector service, run the AlvaoAssetCollector.msi installation package.
- The installer will automatically install Collector as a service and start it.
Note:
In order to run ALVAO Asset Management Collector as an application, you must first stop its service.
Settings
- Stop the ALVAO Asset Management Collector service.
- Release AMCollector.exe from the installed folder.
- Use the Action - Settings command to set up the database connection.
- It is recommended to enable logging to the file and set the level to "status and errors".
- Set the ALVAO Asset Management Collector service to run under an account with administrator privileges. The services in Windows run by default with the permission "Local system account". In order to be able to detect stations on the network without using agents, the ALVAO Asset Management Collector service must run with administrator privileges.
- Enable the selected account to access the Alvao database and assign it the required database roles.
- In WebApp - Administration - Asset Management - Servers, enable the server with the Enable command.
- Run the ALVAO Asset Management Collector service again.
Tip:
Other Collector settings are done in
Management in ALVAO WebApp in the
Asset Management - Servers section.
Caution:
If you set the log detail in the file to the
Detailed, the Collector will generate a large amount of data in the LOG file and the detection rate will be very slow. Therefore, setting it to
Detailed is only recommended for troubleshooting and is not recommended for normal operation.
Note:
If you only want to run Collector as an application and have installed it with AM Console, you can run Collector from the
Start - ALVAO - Asset Management Collector (in this case there is no need to install AlvaoAssetCollector.msi).
Note:
After a new installation, automatic retrieval of detections from the %ProgramData%\ALC\ALVAO Asset Management Collector\Detections folder is enabled by default.
ALVAO WebApp
Installation Guide
- Make sure that the computer where you want to run ALVAO WebApp, has an IIS intranet server installed with a version that meets the technical requirements.
- We recommend creating a custom application pool ALVAO AppPool .NET 4.0 on IIS. This step is not strictly necessary to run the application, but it significantly affects the loading speed of the WebApp.
- Before installation, make sure you have ASP .NET v4.7.2 or higher installed.
- Log in as administrator and run the installation package AlvaoWebApp.msi. If you have a problem with UAC, run the installation from the command line using msiexec -i AlvaoWebApp.msi.
- When installing, select the ALVAO AppPool .NET 4.0 application pool.
If you did not create this AppPool in step 2, select .NET v4.5. For the Alvao WebApp, select pipeline: integrated.
- The installer will create a folder on disk (<InetPub>\wwwrootAlvao)
and also a virtual directory in IIS (Alvao).
- Give the NT AUTHORITY\NETWORK SERVICE account access to the Alvao database and assign it the required database roles. If you did not create a custom application pool in step 2, assign access and roles to the IIS APPPOOL\.NET v4.5 account.
- Go to ALVAO WebApp (http://localhost/Alvao) and in Administration under License, enter the activation key. Activation Key
You can obtain a key from the Alvao system vendor. You can also request a temporary activation key to test the system at info@alvao.com.
After entering the activation key, press Save.
Note:
When the database is activated, the activation key entered is verified over the Internet.
- More in Administration - Settings:
- In the Messaging section, enter the SMTP server address, login credentials, and email address for sending messages from the Alvao system.
- In the Active Directory section, set the Active Directory server address and default domain.
- In the ALVAO WebApp, edit the settings in Administration - Settings - WebApp.
- Fill in the WebApp (URL) path to the ALVAO WebApp folder. For example: .
http://server/alvao.
- By default, after installation, the application displays time data in the Coordinated Universal Time (UTC) time zone to users.
If necessary, change the default time zone in WebApp - Administration - Settings - Languages and Time Zone.
Caution:
We recommend installing the ALVAO WebApp in a folder on IIS (e.g. IIS\WebApp, IIS\ALVAO, etc.) and not placing it directly in the root (IIS). When installing
Service Desk WebService e.g. in the
<InetPub>\wwwroot\ServiceDeskWebService then problems with WebService configuration could occur.
Settings
For proper functionality of ALVAO WebApp
it is necessary to configure the user authentication method in IIS.
Available authentication methods:
- Form Authentication
- Authentication by entering username and password. For a permanent login without the need to enter a username and password, you can use the Permanently log in.
- This method of authentication should be used if the WebApp is accessible from the Internet.
- Windows Integrated Authentication
- Authentication without the need to enter a username and password (in case of successful integrated authentication).
- This authentication method is appropriate to use when both the solution teams and requesters are from Active Directory and working in a domain.
- Integrated Windows and Forms Authentication (simultaneously)
- WebApp first tries to authenticate the user using Windows. When this authentication fails (or is revoked by the user),
the user is allowed to log in using a form.
- This authentication method may not work properly due to technical limitations (see below).
Form Authentication
If you want to set up forms authentication:
- In IIS Manager, click on the Application AlvaoWebApp and then click Authentication.
- Make sure that Anonymous Authentication
is enabled, Forms Authentication
is enabled, and Windows Authentication
is disabled.
- Open the web.config file located in the ALVAO WebApp folder in a text editor.
- Make sure that in the configuration/system.web attribute is authentication mode is set to Forms and the loginUrl parameter
is set to ~/Account/Login.
Note:
For this authentication method, the available options are
.
Logout and
Change Password.
Note:
If users are logging in with a password from Active Directory, the path to the AD server must be set in the
ALVAO WebApp -
Management -
Settings
-
Active Directory.
Windows Integrated Authentication
To set up Windows Integrated Authentication:
- In IIS Manager, click on the application AlvaoWebApp and then click Authentication.
- Make sure Windows Authentication is enabled (and all others are disabled).
Caution:
Authentication must also be enabled on the website where the application is installed.
- Open the web.config file located in the ALVAO WebApp folder in a text editor.
- Make sure that in the configuration/system.web attribute is authentication mode is set to Windows.
- In the IIS root, set Feature delegation
(Feature Delegation) - enable read or write in the following authentication modes: Anonymous
and Windows.
Caution:
There are no options available for this authentication method
Logout and
Change Password.
Caution:
This authentication method cannot be used to authenticate users who are not imported from Active Directory.
Windows and Forms Integrated Authentication (simultaneously)
If you want to use Windows integrated authentication for some computers and forms-based logon for other computers:
- In IIS Manager, click on the AlvaoWebApp and then click Authentication.
- Make sure that Anonymous Authentication
is enabled, Forms Authentication
is enabled, and Windows Authentication
is enabled.
Caution:
Authentication must also be enabled on the website where the application is installed.
- Open the web.config file located in the ALVAO WebApp folder in a text editor.
- Make sure that in the configuration/system.web attribute is authentication mode is set to Forms and the loginUrl parameter
is set to ~/Account/MixedModeLogin.
- Set Feature Delegation in the IIS root.
- enable read or write in the following authentication modes: Anonymous, Forms, Windows.
- In WebApp- Administration - Settings -
Integrated Authentication
enter the IP address ranges of the computers on the internal corporate network for which integrated authentication is to be applied. For all other computers, forms-based authentication will be used.
Caution:
If Windows authentication is successful, the
Repudiate and
Change Password options are not available.
Caution:
For computers that will be authenticated in an integrated manner, the same restrictions and assumptions apply as for Windows integrated authentication, see the caveats in the previous section.
Database connection
Open the IIS Manager and select the ALVAO WebApp (Alvao). In the settings, click on the Connection Strings, click the string "Db" and set the correct path to the SQL server and database you created during installation (the default is localhost and the Alvao database). For example, you can use localhost for the SQL server and Alvao for the database. The connection string then looks like this:
Data Source=localhost\SQLEXPRESS;Initial Catalog=Alvao; Max Pool Size=2000; Integrated Security=True
The WebApp configuration is stored in the Web.config file in the ALVAO WebApp folder. It can also be edited manually by editing this file.
ALVAO Asset Management WebService
ALVAO Asset Management WebService is part of the ALVAO Asset Management product. It is used to communicate with autonomous agents and also to remotely connect to the Asset Management Console.
Installation Guide
- Make sure that the computer where you want to run ALVAO Asset Management WebService has IIS intranet server installed.
- Before installation, make sure that you have ASP.NET v4.7.2 or higher installed.
- If you want to use the Asset Management WebService on computers running IIS version 7, you must verify that IIS Management Compatibility 6 is installed before installation.
- We recommend creating a custom application pool ALVAO AppPool .NET 4.0 on IIS. This step is not strictly necessary for the application to run, but it significantly affects the responsiveness of the WebService.
- Log in as administrator and run the installation package .
AlvaoAssetWebService.msi.
- Select the ALVAO AppPool .NET 4.0 application pool during installation.
If you did not create this AppPool in step 3, select
.NET v4.5.
- The installer creates a folder on disk (<InetPub>\wwwroot\AssetWebService)
and also a virtual directory in IIS (AssetWebService).
- After installation, you need to configure the web.config file,
which you open in a text editor.
- In the line:
<connectionStrings>
<add name="Db" connectionString="Data Source=localhost;Initial Catalog=Alvao;Integrated Security=True;Current Language=Czech" providerName="System.Data.SqlClient" />
</connectionStrings>
set the connection to the database. The connection string has the same format as in the Web.config file in the ALVAO WebApp settings.
- Give the NT AUTHORITY\NETWORK SERVICE account access to the Alvao database and assign it the required database roles. If you did not create a custom application pool in step 3, assign access and roles to the IIS APPPOOL\.NET v4.5 account.
Note: To test the correct WebService setup, temporarily
enable WSDL. Then enter the AssetWebService path (URL) in your web browser all the way to the "AssetWebService.asmx" file.
For example:
https://server/AssetWebService/AssetWebService.asmx.
If set correctly, a list of operations is displayed. After the testing is finished, disable WSDL.
Note: When connecting AM Console via Asset Management WebService, you must install
Microsoft OLE DB Driver on the server.
ALVAO Service Desk WebService
For installation procedure, please refer to the ALVAO Service Desk.
ALVAO Service Desk MailboxReader
ALVAO Service Desk MailboxReader is an application that provides, among other things, automatic notification of users for missing licenses.
Installation Guide
- Download the installation package AlvaoServiceDeskMailboxReader.msi.
- The installer will install MailboxReader in the %Program Files%\ALVAO\ServiceDesk MailboxReader folder.
- In the MailboxReader.exe.config file in the line:
<connectionStrings>
<add name="Db" connectionString="Data Source=localhost;Initial Catalog=Alvao;Integrated Security=True;Current Language=Czech" providerName="System.Data.SqlClient" />
</connectionStrings>
set the connection to the database. The connection string has the same format as in the Web.config file for the ALVAO WebApp.
- In the Alvao database, enable access for the NT AUTHORITY\NETWORK SERVICE account and set the database roles.
- Set the ALVAO MailboxReader system service to run under the NT AUTHORITY\NETWORK SERVICE account. Otherwise, problems may occur when sending notifications via SD WebService.
- Start the system service.
Tip:
To verify functionality, you can run
MailboxReader.exe on your desktop. Then exit the application by closing its main window.
Note:
If you need to change the
MailboxReader.exe.config configuration file,
you need to stop the
ALVAO MailboxReader service before making the change and start the service again after saving the configuration changes.
ALVAO REST API
ALVAO REST API is used to communicate the ALVAO Teams Add-in and ALVAO Outlook Web Add-in with the ALVAO system.
Installation Guide
- Make sure the machine where you want to run the ALVAO REST API has an IIS intranet server installed with a version that meets the technical requirements.
- We recommend creating a custom application pool ALVAO AppPool .NET 4.0 on IIS. This step is not strictly necessary to run the application, but it significantly affects the loading speed of the WebApp.
- Before installation, make sure you have ASP .NET v4.7.2 or higher installed.
- Log in as administrator and run the AlvaoRestApi.msi installation package. If you have a problem with UAC, run the installation from the command line using msiexec -i AlvaoRestApi.msi.
- When installing, select the ALVAO AppPool .NET 4.0 application pool. If you did not create this AppPool in step 2, select .NET v4.5.
- The installer creates a folder on disk (<InetPub>\wwwroot\AlvaoRestApi) and also a virtual directory in IIS (AlvaoRestApi).
- After installation, you need to configure the web.config file in the ALVAO REST API folder (open the file in Notepad).
- In the line:
<connectionStrings>
<add name="Db" connectionString="Data Source=localhost;Initial Catalog=Alvao;Integrated Security=True;Current Language=Czech" providerName="System.Data.SqlClient" />
</connectionStrings>
set the connection to the database. The connection string has the same format as in the web.config file in the WebApp settings.
- Give the NT AUTHORITY\NETWORK SERVICE account access to the Alvao database and assign it the required database roles. If you did not create a custom application pool in step 2, assign access and roles to the IIS APPPOOL\.NET v4.5 account.
Note:
The ALVAO REST API web service is set to
Anonymous Authentication.
Assign database roles to application accounts
In SQL Server Management Studio on SQL Server, create the necessary user accounts under which the installed applications run so that they can access the database. Then, in the Security - Logins folder, use the following table to allow access to the individual application accounts and assign them database roles.
| Applications |
Recommended account |
Assigned database roles |
| ALVAO Asset Management Collector |
NT AUTHORITY\SYSTEM |
public, db_datareader, db_datawriter, db_ddladmin, db_executor |
| ALVAO WebApp |
NT AUTHORITY\NETWORK SERVICE (possibly IIS APPPOOL\.NET v4.5) |
public, db_datareader, db_datawriter, db_ddladmin, db_executor |
| ALVAO Asset WebService |
| ALVAO REST API |
| ALVAO Service Desk MailboxReader |
NT AUTHORITY\NETWORK SERVICE |
db_owner |
Did not find what you were looking for? Ask our technical support team.