{"id":49008,"date":"2023-09-27T14:47:14","date_gmt":"2023-09-27T12:47:14","guid":{"rendered":"https:\/\/www.loginventory.de\/?p=49008"},"modified":"2023-12-21T09:37:19","modified_gmt":"2023-12-21T08:37:19","slug":"loginventory-version-9-4-0","status":"publish","type":"post","link":"https:\/\/www.loginventory.de\/en\/changelog-en\/loginventory-version-9-4-0\/","title":{"rendered":"LOGINventory Version 9.4.0"},"content":{"rendered":"

New<\/span> With version 9.4 LOGINventory gets many new features in the area of Cloud Inventory<\/strong>. For example, virtual machines<\/strong> from Azure<\/strong> and AWS<\/strong> are now newly captured, the Azure Active Directory<\/strong> is inventoried, and the on-premises AD inventory<\/strong> has also been extended<\/strong>. “Modern Authentication<\/strong>” is now always used to capture cloud services. Upgrade now for free to LOGINventory 9.4 and benefit from all new features!<\/em><\/p>\n

<\/p>\n<\/div>

VMs from Azure and AWS<\/h2>\n

LOGINventory can now query online from Azure<\/strong> and AWS<\/strong> which virtual machines<\/strong> exist, what status they have, which image they are based on, which payment model is used, which hardware equipment the VM has, how the VM can be addressed, in which data center it is running, and much more.<\/p>\n

To do this, use the new definition types<\/a> directly in the Remote Scanner and try out the acquisition right away!<\/p>\n

Tip<\/em>: As with other hypervisors (e.g. Hyper-V, VMware ESXi), only the information that is known to the hypervisor about the VM is determined in this way. However, if you also want to determine which software is installed, how full the partitions are, or which user logged in when, the device must also be scanned explicitly. For example, the Offline Agent can be used for the explicit scan of the VMs in the cloud.<\/p>\n<\/div>

Azure Active Directory<\/h2>\n

In addition to the inventory of an on-premises Active Directory, it is now also possible to determine information on Users<\/strong>, Computer Accounts<\/strong> and Group Memberships<\/strong> from an Azure Active Directory<\/strong>. This type of collection is suitable for pure Azure Active Directory<\/strong> configurations, but also for hybrid environments<\/strong>, as this also identifies information about users’ permissions on Azure<\/strong>.<\/p>\n

Also for this, set up the new definition type<\/a> in the Remote Scanner to benefit from the new features!<\/p>\n<\/div>

<\/i>Breaking Change<\/span> The previously scanned data of an on-premises Active Directory cannot\u00a0be migrated<\/strong> into the new structure and will therefore be deleted<\/strong> by the update installation. After the update installation, simply restart the acquisition of the AD!<\/p>\n<\/div>

New account types in Remote Scanner<\/h2>\n

For the inventory of cloud services, no classic authentication with username and password is used, but “Modern Authentication<\/strong>“: Thus, appropriate settings must be made in Azure, or AWS and stored in the Remote Scanner at the new account types<\/a> Azure Credentials<\/strong> and AWS Credentials<\/strong>.<\/p>\n

To read Azure VMs, Exchange Server online, Azure AD, and Microsoft 365 subscriptions, an App Registration must be set up in Azure and authorized accordingly<\/a>. An access key must be generated<\/a> online for authentication to AWS.<\/p>\n<\/div>

Other innovations:<\/p>\n

Build 15540 (09\/27\/2023):<\/em><\/p>\n