Is LOGINventory5 compatible with Windows Server 2008 R2?

We support LOGINventory5 on Windows 2008 R2 without any restrictions!

In terms of Microsoft’s policy guidelines and technical requirements, the question cannot be answered with just one word. Please make your own decision ...

General Policy

All server components must be tested on 64-bit Windows Server 2008 R2 Enterprise edition. All client components that are part of server applications must be tested and verified concurrently.
If a Server application has client components that will be typically used on a Server Computer then such components must be tested on Windows Server 2008 R2 Enterprise 64-bit edition.
If client components will be typically deployed on a Client Computer, then such components must be tested on any Windows 7 64-bit edition.
All testing must be performed within a Virtual machine running on top of Microsoft Hyper-V.
Applications must not hide unhandled exceptions from Windows Error Reporting (WER).

Prerequisites

Conduct tests on both Windows Server 2008 R2 Enterprise 64-bit editions for Server components and Windows 7 64-bit operating systems (any edition) for Client components.
Support 64-Bit version of Windows running on multiple processors
Multi-language requirements
Follow best practices in Security and Reliability
Maintain compatibility with Antivirus software
Do not cause services to unexpectedly become unavailable
All drivers must be WHQL (Windows Hardware Quality Labs) signed

Application Eligibility

The Server application is primarily designed to run on Windows Server operating systems
The Server application must be installed using a commercially available installer application (MSI based or otherwise)
A Server application that can be installed using a custom installer application (MSI based or otherwise)
A Windows Server application that requires other prerequisites (like SQL Server) to be installed
A Java or .NET application or similar hosted run time environment application

Installer Verification

Use Windows Components for Installation
Correctly configure package identity
Installer Custom Action Restrictions

Functionality

Perform primary functionality and maintain stability
Comply with driver related requirements
Do not overwrite non proprietary files with older versions
All executables must be signed
Install shared components to correct location
Do not install 16-bit binaries