We have added version 11.4.402.278 of Adobe Flash Player to the Installer Library but while we were testing it out we noticed something odd.
The wrong version was being reported in the Uninstall portion of the Windows registry. This is the same registry key that Windows uses when it displays installed software in Control Panel > Programs or Add/Remove Programs in XP. This is also the same key that PDQ Inventory uses to determine installed applications.
Adobe acknowledged the mistake in their Flash support forums:
Adobe states that the next release will show the appropriate version. This issue, incidentally, only affects Adobe Flash Player if it was installed via the MSI. If you installed using their EXE the correct version will be reported to Windows and PDQ Inventory.
If you are using PDQ Inventory or another software inventory application just keep in mind that version 11.4.402.267 will be shown instead of 11.4.402.278. The image below shows how PDQ Inventory reports the version (based on MSI version reported in the registry) and the actual file properties of the installed Flash Player Plugin.
You do have some other options on how you can be sure that your computers have version 278. You can always scan for the Flash files and then build your collections or reports based on the file versions. To do this you will need to add some File Scanners to a Scan Profile. Customizing Scan Profiles requires PDQ Inventory Pro mode.
Here is a screenshot of my Applications scan profile. I simply added to File Scanner entries which instructs this Scan Profile to scan for .EXE files in %systemroot%\system32\Macromed and %systemroot%\SysWOW64\Macromed.
After I added these two file scanners I simply re-scanned all my computers with the Applications scan profile.
The Collection below will contain all computers which have Flash ActiveX version 11.4.402.278. (If you want to look for Flash Plugin you can use File Name matches pattern Flash*Plugin*.exe)
To see more about Scan Profiles feel free to check out the following articles.
Introducing File and Registry Scanners (older article but very relevant)
Find Oracle Client Versions using File Scanners
Let us know if you have any questions.
Oracle Version Challenges
If you are a Sys Admin and have worked with the Oracle client for Windows then you probably know that it doesn't behave like other Windows' applications. For one, the installation isn't registered in Windows, therefore you can't uninstall via Control Panel > Programs (or Control Panel > Add/Remove Programs on XP/2003).
PDQ Inventory (like many other Inventory tools) determines which applications are installed by scanning the same area in the Registry that Windows uses in Control Panel > Programs.
So if the Oracle client doesn't show up as an installed application how can you:
- Determine which computers have the client installed and
- Determine which versions are installed across your network?
How to get your Oracle version
You can easily determine this if you run PDQ Inventory in Pro Mode. The point here is not just to show you how you can inventory your Oracle clients but also to help you understand how you can use PDQ Inventory to collect all sorts of other data.
If you are running PDQ Inventory in Free mode, feel free to start a trial of Pro mode. It's quick and you will quickly see the evil power that you hold in your hands. (ahem)
In the case of the Oracle client I am going to revert to scanning for specific files. In this case I am going to scan computers for the file oraocci11.dll. This, obviously will only work with Oracle 11 versions. If you have other versions of Oracle, I would suggest that you find an Oracle file that you can use to determine the version.
Here is a screenshot of the properties of oraocci11.dll on an XP and a Windows 7 computer.
Let's tell Inventory what we want to scan for. To do this we will create a new Scan Profile.
Step 1. Create a new Scan Profile (or edit an existing one if you'd prefer). You create new Scan Profiles via the Preferences window.
Give your new Profile a name and then add a "Files" scanner.
After you select "Files" you need to specify A) where to search for the files and B) which files to look for. In this example I chose to look in the %SystemDrive% directory (usually C:\). In the File Patterns field I entered ora*.dll. This will look for any file that begins with ora and ends with .dll.
After you finish editing your Scan Profile go to your All Computers collection and scan computers using the Oracle Client profile. Don't hit the usual Scan Computers instead select the button next to it. This will drop down a menu of all of your Scan Profiles.
Now let's create some new Collections to organize our Java client computers. Hit CTRL+N (or go to Collection > New Collection). Below is a screenshot of what our collections will look like when we are done.
Create the Oracle Client collection.
Then create a collection underneath Oracle Client called Oracle Client (latest version)
Note that for File Version we are using the version equals condition. All conditions that begin with the word Version will process a string of numbers stopping at the fourth dot (.) or comma (.). If the version value being compared is 220.127.116.11.34.65 the condition will only evaluate 18.104.22.168
Next we will create a collection underneath Oracle Client called Oracle Client (old version)
Notice that in this case we are using the version lower than condition. Here are some example of versions that pass this condition:
Here are some examples of versions that would NOT pass this condition:
Finally, we are going to create one last collection called Systems missing Oracle Client
Notice how the conditions still look for file name that equals oraocci11.dll inside a path which contains the word client. The magic comes by changing the Match rule near the top of the Collection window. In this case we select Don't Match Any. This means that computers meet these two conditions will NOT be shown in this collection. This way we can find which computers don't have the Oracle Client.
You can also, of course, create a new report to give you some more in-depth data about the Oracle Client. Go to the menu: Report > New Report > Basic
Give your new report a name. I called mine Oracle Client Versions. Under the Columns tab select Add Column > Computer > Name. Then choose Add Column > File > File Name. You can review this image to see which Columns I chose to show in this report.
After you have chosen which columns to display, go to the Filters tab Push the Add Filter button. A new filter will be created called Filter 1. Inside the Filter panel push the Add Column button. Add File > File Name. Use the equals condition and type oraocci11.dll. Add a new Column and select File > File Path. Using the contains condition type, client.
Save your report and hit the Run button (blue triangle) to see your results. Make sure your collection source is set appropriately. You will which collection you are running this against listed under the name of your Report. You can see in this example that I am using the collection All Computers.
There you have it.
We love the Spiceworks community.
If there is a sys admin tool out there in the wild, the chances are very good that someone at Spiceworks has used it.
About 6 months ago we provided an entry level integration between Spiceworks inventory and PDQ Deploy. It's the ability to push software from PDQ to computers listed in Spiceworks Inventory.
That little piece of integration has caused quite a stir. Just today we surpassed 1,000 followers on our Spiceworks vendor page. Even better, we're not done with our integration into the Spiceworks tool.
JJ has been feverishly slaving on the next iteration. We have had to hit the pause button while we finish up our PDQ Deploy 2.0.2 beta, but JJ will be back at it very shortly.
We're keeping our new Spiceworks integration features close to our chest at the moment, but suffice it to say we are looking forward to our pro mode users being able to launch PDQ Deploy from within the Spiceworks console.
A huge thanks to the Spiceworks community. We're excited to bring some cool features that are at the top of our requested features list.
I just received the love letter from Microsoft informing that the Server 2012 release-to-manufacturing version is now available for evaulation.
Microsoft has simplified its licensing model with Server 2012. There are only two core SKU's:
- Datacenter Edition
- Standard Edition
There are two lesser editions of note with the emphasis that these have no virtualization rights.
The Datacenter Edition provides Server 2012 virtualization (unlimited number of vm's per processor).
We've been looking at Server 2012 and Windows 8 for a few weeks now. We'll hold our review of 2012 for a little longer while we kick the tires. As far as Windows 8, why regurgitate what seemingly everyone else is already saying.
As far as the new licensing model is concerned; bravo. Keep it simple. Nothing worse than needing an engineer to determine which licenses you require.
The price reported for Datacenter seems steep ($4,809), but when you consider that it includes unlimited vm's it starts to make the price a little easier to swallow.