This is accomplished by running a small information gathering module at login and/or boot time on every machine within a Microsoft^tm Active Directory environment. The output of this module is then scanned and added to a database that then may be queried to determine such things as:

• How many machines are using a particular piece of software?
• How many machines have a given software patch?
• How many machines are manufactured by a given vendor?
• Which Active Directory policies are actually applied on which machines?
• Which machines have not checked in within a given time frame?

These reports may be augmented by surveying the software in your environment and then catagorizing each title for it's applicability. Furthermore, you may keep tabs on how many licenses you have versus how many installs you have of any given title (a real plus when it comes to compliance verification).

  System Requirements

• Microsoft Internet Explorer 4.01 or newer, with both ActiveX and JavaScript enabled.
• Microsoft Windows XP Professional, 2000, or 2003 (will not run on XP Home Edition)
• Microsoft Internet Information Services, Version 4.0 or newer
• 266 MHz processor
• 256M of memory
• 50M of disk space

Go to the top...

  History of SoftwareAudit

Although all of these more industrial tools do a good job, many of their features were considered overkill for the SMB marketplace. A simpler, more to the point product was needed. Thus SoftwareAudit was born.

Since 2005, SoftwareAudit has grown to include a number of features specific to various customer's needs. New reports and tools were created to help:

• Be able to track "repurposed/reloaded/reused" machines across the enterprise.
• Being able to brand a company defined "asset id" into the registry to help track physical assets.
• Being able to keep track of special case hardware/software installs on a per machine or per software title basis.
• Tracking down a machine by any of:
  • MAC Address
  • IP Address
  • Motherboard serial number
  • Asset IDs