Skip Navigation LinksALVAO 11.0ALVAO Service DeskSystem implementation in the organizationInstallationALVAO Server - manual installation Skip Navigation Links.

ALVAO Server - manual installation

Creating a new database

Create a new database, see ALVAO Asset Management - ALVAO Server - Manual Installation - Creating a New Database.


For installation procedure, see ALVAO Asset Management - ALVAO Server - manual installation - ALVAO WebApp.

ALVAO Service Desk WebService

This application provides, among other things, sending email notifications to users.

Installation Guide

  1. Make sure that the computer where you want to run ALVAO Service Desk WebService has an IIS intranet server installed with a version that meets the technical requirements.
  2. Before installation, make sure you have installed ASP.NET v4.7.2 or higher.
  3. We recommend installing a custom application pool "ALVAO AppPool .NET 4.0" on IIS - instructions here. This step is not strictly necessary for the application to run, but it significantly affects the loading speed of the web application. If you do not want to create an "ALVAO AppPool", continue with step 4.
  4. Log in as administrator and run the installation package . AlvaoServiceDeskWebService.msi.
  5. Select the Application Pool ALVAO AppPool .NET 4.0 during installation. If you did not create this AppPool in step 2, select .NET v4.5.
  6. The installer creates a folder on disk (<InetPub>\wwwroot\ServiceDeskWebService) and also a virtual directory in IIS (ServiceDeskWebService).
  7. After installation, you need to configure the web.config file in the ServiceDeskWebService folder. (open the file in Notepad).
  8. In the line:
      <add name="Db" connectionString="Data Source=localhost;Initial Catalog=Alvao;Integrated Security=True;Current Language=Czech"  providerName="System.Data.SqlClient" />

    set the connection to the database. The connection string has the same format as in the Web.config file in the WebApp settings.
  9. Add the server on which WebService is installed to the local intranet zone for all client computers. We recommend using the Group Policy template Computer Configuration/Administrative Templates/Windows Components/Internet Explorer/Internet Control Panel/Security Page/Site to Zone Assignment List found in the Local Group Policy Editor (gpedit.msc).
  10. Launch the ALVAO WebApp.
  11. From the menu, select Administration - Settings - Web Services. Here, fill in the ServiceDeskWebService path (URL) all the way to the file "ServiceDeskWebService.asmx". For example: http://server/ServiceDeskWebService/ServiceDeskWebService.asmx
Do not install WebService in the AlvaoWebApp or its subfolders to avoid configuration problems with WebService.
To test the availability of WebService temporarily enable WSDL and use e.g. the function GetServiceDeskPortalUrl, which returns the set path to the ALVAO WebApp and does not require any input parameters.


For proper functionality of ALVAO Service Desk WebService it is necessary to configure how users are authenticated in IIS.

The recommended authentication method is Windows Integrated Authentication.

Windows Integrated Authentication

To set up Windows Integrated Authentication:

  1. In IIS Manager, click on the Application ServiceDeskWebService and then click on Authentication.
  2. Make sure Windows Authentication is enabled (and all others are disabled).
    Authentication must also be enabled on the website where the application is installed.
  3. Open the web.config file located in the ServiceDeskWebService installation folder in a text editor.
  4. Make sure that in the configuration/system.web attribute is authentication mode is set to Windows.
Methods of authentication to IIS

To properly set up Windows authentication on a domain network, use the following procedure:

  1. In IIS Manager, click the ServiceDeskWebService application and then click Authentication.
  2. Select Windows Authentication (enabled) and select Providers in the panel on the right.
  3. In addition to the default Negotiate option, we recommend enabling the Kerberos option.
    Differences between authentication methods:
    Windows Kerberos The newest and most secure method of authentication, but makes no sense on networks with older PCs.
    Technical requirements: a Windows operating system and a Windows server with the required system versions (see technical requirements).
    Windows NTLM Older but sufficient option, works even on older stations.
    Windows Negotiate The option tries Kerberos and if authentication fails, tries NTLM.
  4. If the server name differs from its DNS alias, you must set the alias in the Windows registry. So add the following key of type MULTI_SZ to the registry: HKLM\System\CCS\Control\LSA\MSV1_0, option BackConnectionHostNames = <alias>.
This setting will prevent the problem with not generating notifications, for example after creating a new request from the WebApp.

Disabling Authentication

Disabling authentication is not recommended. If you disable authentication, you will allow any Internet user to access WebService methods.
  1. Open the web.config file in the WebService installation directory.
  2. Find the <authentication>
  3. Delete everything contained between the <authentication> and </authentication> tags.

ALVAO Service Desk MailboxReader

This application provides, among other things, the automatic retrieval of messages from electronic mailboxes and their storage in the Alvao database. For installation procedure, see ALVAO Asset Management - ALVAO Server - manual installation - ALVAO Service Desk MailboxReader.


Installation procedure, see ALVAO Asset Management - ALVAO Server - manual installation - ALVAO REST API.


Did not find what you were looking for? Ask our technical support team.