Generating software legitimacy reports

The whole reason why we are auditing the software assets and installations for the organization is so that we can use this information to generate software legitimacy reports. This may be for simple piece of mind or it may be to identify unnecessary licenses or the requirement for additional licenses. It may be the case that before starting the process your organization had no idea what the end result would be and, in this case, you’ll most likely be looking at one of the last two scenarios (massive under or over licensing of products).

At the end of the day, your objectives in collecting all of this information are your own and how you interpret the data that gets stored in your ENT Inventory is up to you. The software legitimacy reports that we provide with the software constitute one way of interpreting this data which we hope will be very useful to most organizations, but if you wanted to build your own software legitimacy reports to interpret this data differently you certainly could.

Before you go off reinventing the wheel however, it certainly wouldn’t hurt to understand the software legitimacy reports that we built work. It may be the case that you can simply modify certain reports that we ship with the software, to tweak these to your own particular ends, and we’ll include an example of one such “tweaked report” in section 5.5 below.

To start with though, we’ll cover some reports that provide basic information about installations that are covered by User Licenses, Site Licenses and Proprietary Licenses.