As you can see from the image above, you just click the type of information you want inventoried and click “Go”. The great part is that it builds the report into Excel so you can easily work with the data in a format you’re probably familiar with already for data collection.

The application is a single HTML Application (.hta) file that’s only 99KB in size. It runs from a USB drive and works on machines you don’t even have to have admin access rights too. Which was another requirement I had in my search.

System Inventory Lite worked absolutely perfectly for my needs. Don’t get dismayed by the “Lite” portion of the name either. It merely refers to the fact that you can get as much or as little information as you want in your system inventory.

As you can also see, if you have a network of machines and you can access the machines, you can tell the application to grab an inventory off of those networked machines as well.

What an amazing little application in a 99KB package. I couldn’t have asked for much more than this.

Image: Screen grab of Excel spreadsheet and System Inventory Lite interface

Post from: EveryJoe

Amazing App With System Inventory Lite

Microsoft details the problems and error experienced here on their Microsoft Help and Support website.

Basically what happens is that when you try and install he product, the installer can’t find the installation files it needs to finish the installation.

No problem right?

You receive the error message and then just hit the browse button to tell Windows exactly where the installation files reside and you’re on your way. You think it’s even more perfect because the browse mechanism displays exactly what it says you’re missing.

There’s the problem though.

The browse function doesn’t really work for some reason. The problem lies deep within the registry. Here’s Microsoft’s statement of the cause:

The MEDIAPACKAGEPATH property wasn’t properly set. MEDIAPACKAGEPATH is a public property that enables you to define where on the removable media the MSI file is located. This can happen if the media that is currently being used and the media that was originally used to install the program have the MSI file at different relative paths.

For example, this error can occur if the original media had the MSI file in a folder called App1, and the current media has the MSI at the root of the media. This error will not occur if the same media is used for the original installation and the current install operation.

Here’s the further problem I ran into though when I tried to follow their solution for fixing the problem.

The guidance they provide for trying to fix the MEDIAPACKAGEPATH you need to look for registry keys that look something like the following:

HKCU\Software\Microsoft\Installer\Products\<Compressed ProductCode>\SourceList\Media

Did you notice the "<CompressedProductCode>" part? How do I find out which product is the one I’m looking at with the error easily? I’ve got hundreds of products installed, at the time, most of which were having problems and errors.

Post from: EveryJoe

Error 1706 "No Valid Source Could Be Found"