SMS 2.0 Query for Executable Lists computers that do not have it. 1

[cohoonma]

We have an SMS 2.0 environment. We run the following query to find versions of MS Word. This query is listing a few machines that do not have the executable with the specified version. I have run the client cleaner on the computers with a /scrub parameter, and deleted the system in the SMS console. I then re-install the sms client and yet the version of winword reported is v8 not the 11 that it should be. Can anyone offer some insight or tip to get the machines to report correctly? The query is:

select distinct PC.Name, Last.FullUserName, PC.OperatingSystemNameandVersion, PC.IPSubnets, sw.FileName, sw.FileVersion, Last.UserName, PC.ResourceID, PC.ResourceType from SMS_R_System as PC inner join SMS_G_System_SoftwareFile as sw on sw.ResourceID = PC.ResourceId full join SMS_R_User as Last on Last.UserName=PC.LastLogonUserName
where (sw.FileName = "winword.exe" and sw.FileVersion like "8.%")

Thanks,
Michael

 

[tbrennans]

Any chance this machine has both? The other thing that can happen is say the machine was upgraded from version 8 to 11, in the SMS database 8 will still show up for the default of 90 days before its cleaned out as old data, and my findings over the years was this wasn't set in stone (meaning in 2.0 it didnt always clean it out like you wanted) but for the most part it will clean it out over time as long as you have the task set in the maint tasks container in the admin console.

 

[cohoonma]

tbrennans,

I have scanned the drive, so no chance of there being both version, however, you were correct in that these were upgrades from office 97 to office 2003.

I looked at the help files for the Delete Aged inventory task but that appears to work on hardware inventory records. Am I mistaken or will it work on software inventory records as well? If so, I could tweak the scheduling of the task to try and help cleanup the old entries.

Thanks,
Michael

 

[tbrennans]

Yes, I think your right about the hardware sorry about that... I dont beleive 2.0 has Delete Inactive Client Discovery Data task...but I do think it has: (which will make it delete everything old..)

Delete Aged Discovery Data
This SMS predefined maintenance task deletes aged discovery data of resources. If client discovery methods are enabled at the site or at any of its child sites, then SMS is collecting discovery data from resources and is storing that data in the site’s database.

Use this task to delete from the SMS site database all data associated with resources that are no longer considered part of the SMS hierarchy. This task identifies resources that have not reported any discovery data in more than the number of days specified in the task properties dialog box. The task deletes from the SMS site database all data (including hardware inventory, software inventory, and software metering data) referencing that resource, deleting the resource from the site.

The Delete Aged Discovery Data task is similar to the Delete Inactive Client Discovery Data task, with the following exceptions:

• It operates on all resources. The Delete Inactive Client Discovery Data task operates only on resources that are SMS clients.

• It checks for the existence of records from any discovery method. The Delete Inactive Client Discovery Data task checks for the existence of only Heartbeat Discovery records.


This task is enabled by default and scheduled to run every Saturday between midnight and 5:00 A.M., and to delete data older than 90 days

 

[cohoonma]

I can work with that. Thanks a bunch for the suggestions.
Michael