Can I audit the Windows 7 operating system using iInventory v7?
iInventory v7 is fully compatible with Windows 7. The iInventory console may be installed on Windows 7 machines (x86 versions) and used for both software and hardware data auditing (x86 and x64 versions). Audits can be achieved using either remote auditing or the Windows audit agents (agent32.exe). However because of the increased security levels provided by User Account Control within Windows 7 some configuration changes may be required to allow remote auditing to take place effectively. The article below from Microsoft explains which changes may be required to successfully audit your computers remotely. Handling Remote Connections Under UAC Whether you are connecting to a remote computer in a domain or in a workgroup determines whether UAC filtering occurs. If your computer is part of a domain, connect to the target computer using a domain account that is in the local Administrators group of the remote computer. Then UAC access token filtering does not affect domain accounts in the local Administrators group. Do not use a local, non-domain account on the remote computer, even if the account is in the Administrators group. In a workgroup, the account connecting to the remote computer is a local user on that computer. Even if the account is in the Administrators group, UAC filtering means that a script runs as a standard user. A best practice is to create a dedicated local user group or user account on the target computer specifically for remote connections. The security must be adjusted to be able to use this account because the account never has administrative privileges. Give the local user: If you use a local account, either because you are in a workgroup or it is a local computer account, you may be forced to give specific tasks to a local user. For example, you can grant the user the right to stop or start a specific service through the SC.exe command, the GetSecurityDescriptor and SetSecurityDescriptor methods of Win32_Service, or through Group Policy using Gpedit.msc. Some securable objects may not allow a standard user to perform tasks and offer no means to alter the default security. In this case, you may need to disable UAC so that the local user account is not filtered and becomes a full administrator. Be aware that for security reasons, disabling UAC should be a last resort. Disabling Remote UAC by changing the registry key that controls Remote UAC is not recommended but may be necessary in a workgroup. The registry key is HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system\LocalAccountTokenFilterPolicy. When the value of this key is zero (0), Remote UAC access token filtering is enabled. When the value is 1, remote UAC is disabled.