Video Screencast Help

Inventory of Windows Components

Created: 01 Aug 2012 • Updated: 02 Aug 2012 | 12 comments
This issue has been solved. See solution.

By default we don't get inventory of things like .NET framework versions, Internet Explorer versions etc.

How do people turn this on if they need it?

Comments 12 CommentsJump to latest comment

JimChud's picture

Andykn have you gone in to the advanced options on your Inventory Policies and ticked all the software options?

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

andykn101's picture

in the NS log to do with date and time formats being wrong. We let the AV server maintain the AV data.

It's because the windows directories are excluded by default, I just wondered how others get, for example, .NET versions.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

JimChud's picture

Andy,

If you run this do you get anything back?

 

SELECT
   [vri2_Computer].[Guid] AS [_ItemGuid],
   [vri2_Computer].[Name],
   [dca3_AddRemoveProgram].[DisplayName],
   [dca3_AddRemoveProgram].[InstallDate],
   [dca3_AddRemoveProgram].[DisplayVersion],
   [ajs5_vHWComputerSystem].[Model],
   [dca4_AeX AC Identification].[Hardware Serial Number]
FROM
   [vRM_Computer_Item] AS [vri2_Computer]
      LEFT OUTER JOIN [Inv_AddRemoveProgram] AS [dca3_AddRemoveProgram]
         ON ([vri2_Computer].[Guid] = [dca3_AddRemoveProgram].[_ResourceGuid])
      LEFT OUTER JOIN [Inv_AeX_AC_Identification] AS [dca4_AeX AC Identification]
         ON ([vri2_Computer].[Guid] = [dca4_AeX AC Identification].[_ResourceGuid])
      LEFT OUTER JOIN [vHWComputerSystem] AS [ajs5_vHWComputerSystem]
         ON ([vri2_Computer].[Guid] = [ajs5_vHWComputerSystem].[_ResourceGuid])
WHERE (
         ([dca3_AddRemoveProgram].[DisplayName] LIKE N'Microsoft .Net%')
      )

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

SOLUTION
andykn101's picture

That probably would be enough to determine the .NET versions available.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

JimChud's picture

Its definitely gathering something then.

Are you looking for specific versions then? because if you know what DLL's etc are found you could probably gather that from what versions if you know what you are looking for

Would this work better:

SELECT [vc].[Name]
   ,[vc].[User]
      ,[Product Name]
      ,[Manufacturer]
      ,[Product Version]
      ,[File Version]
      ,[File Name]
      ,[File Size (MB)]
      ,[Modification Date]
      ,[Path]
      ,[Internal name]
      ,[Virtualized (Y/N)]
      ,[File Description]
      ,[File Extension]
  FROM [RMV_Installed_File_Inventory] vif
  RIGHT OUTER JOIN [vcomputer] vc on [vif].[_ResourceGuid] = [vc].[Guid]
  where [File Name] = 'iexplore.exe'
  order by [Product Version] ASC

 

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

andykn101's picture

funny, I though Internet Explorer was excluded but couldn't find the exclusion when I checked on the Advanced options earlier.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

JimChud's picture

i've had nightmares trying to find specific things even though you would have expected them to be inventoried.. the standard answer is usually custom inventory.. i can understand in some cases because of searching through system files or the size of the data that would potentially need to be kept but yeah... oh well.

hopefully i helped get you closer :)

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

andykn101's picture

Some really useful SQL queries.

For stuff in our base build, like .NET, I like to have policies to roll out to all existing PCs with a detection check but also an exclusion for all machines with that program installed. But I didn't want to have too many custom inventories.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

JimChud's picture

Thats understandable.

We just have a core software policy that has all windows frameworks in .net, IE, MSXML, etc in then it just runs compliancy checks on startup. It seems to work ok and isn't too intrusive.

I was thinking of creating a dynamic filter for it that checked on the software installed but it seemed easier to let the compliancy do the work for me.

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

andykn101's picture

I have one each for .NET 1.1, .NET 2.0, .NET 3.5 and .NET 4.0 and find they clutter up the Agent window. And separate ones for Adobe Reader, Flash, Air and Shockwave.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

JimChud's picture

yeah we have one containing:

.net 1.1, 2.0, 3.0, 3.5, 4.0. MSXML6, Adobe reader, Flash, Shockwave, Java, Visual C++, Media Player Upgrades, Windows Installer Upgrades etc.

applied to our top level Organisational Groups so all core software effects all machines regardless.

Definitely works, worth giving it a try and see what happens.

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.

JimChud's picture

oh the only thing i've found is correctly applying restarts on successes during the policy otherwise some jobs start to fail to install.

Regards Jim.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem and give a thumbs up to useful comments, articles and downloads.