Skip Navigation LinksALVAO 7.1What's New in ALVAO 7.1ALVAO 7.1 - Release Notes Skip Navigation Links. Skip Navigation Links Skip Navigation Links.


Change ALVAO version
Change language

ALVAO 7.1 – Release Notes

This section contains the description of changes in the new product version that may cause certain problems in case of upgrades from legacy versions and/or running the new version. Please read this information carefully before upgrading to the new version. We also recommend reading the list of known issues in the released versions, see Troubleshooting.

All ALVAO Products

  • If you are upgrading to ALVAO 7.1, it is necessary to upgrade the database with ALVAO Admin.
  • The columns for custom items and all commonly available columns of the ntext type in the database have been converted to the nvarchar(max) type.
  • If the SQL Server is located outside of the EU, some historic values of the "date and time" type can display incorrectly following the upgrade.
  • E-mail messages are sent by the ALVAO Service Desk MailboxReader for the entire ALVAO system.
  • Admin – The SMTP server settings have been moved from "Manage – Service Desk – Settings..." to "Manage – Settings...".
  • Admin – The options "Administrator" and "Application list manager" have been removed from user details. These options have been replaced with membership in the groups "Administrators" and "Application managers".
  • All portals now require a new version of the Web.config file. Once you have installed the new version, back up the existing Web.config file, copy SampleWeb.config and rename it to Web.config and transfer the settings from the old Web.config file to the new one.

ALVAO Asset Management

  • The "Name on the network" remains unchanged following detections.
  • If you want to detect usernames of the last logged-on user for computers, include the "Last logged-on user (username)" property in the computer template, unify objects based on the computer template and have the system re-evaluate all HW detections for computers.
  • For automatic notifications to work correctly, the ALVAO Service Desk MailboxReader service must be installed, configured and running.
  • Once the user has been loaded from Active Directory, the property "Username" in the AM Console will be updated to username including the corresponding domain. The sAMAccountName will be replaced with sAMAccountNameWithDomain in the txtADAttr column in the tblADMap table.

ALVAO Service Desk

  • Files containing user pictures are now stored in folders based on domains. If you are performing a system upgrade, move user pictures to folders with the same names as the corresponding domains. Note: The name of the sub-folder must be identical to the domain name that is displayed for users under Username in Admin following the first import of users from AD after the system upgrade.
  • SDL Console – The "Search for requests" command has been changed to "Search in requests" (Ctrl+E).
  • The Service Desk Webservice component now supports secure access. Following the installation of ServiceDesk WebService 7.1 you will need to enable secure access on the IIS server, or disable secure access in the WebService configuration. WebService will not be available until you make the required settings; see Installation Instructions. It is always recommended to enable secure access.

ALVAO Monitoring

  • The Monitoring WebService application is now included as a part of the Monitoring Portal. Separate installation package for the Monitoring WebService is no longer available. If you are upgrading to version A7.1, install the Monitoring Portal only.
  • Statistics of user activity are computed and displayed in the local machine time where the activity was recorded.
  • Detailed records on user activity are no longer stored in the database, but on the server drive under C:\ProgramData\ALC\ALVAO Monitoring Server\DetailedRecords. Like in previous versions, records older than 90 days are deleted automatically. Summarized user activity records for individual days are stored permanently in the database.
    Please refer to the Implementation Guide for more information on changes in detailed user activity records location.

 

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