Whoa! Well, personally, I'd say wipe them out of File Collection. If you all you want to know if the version of that. ocx file, put them in the tab with the *.exe rules (Inventory Collection). You only want to know the versions of those files.
you don't actually *need* the files themselves, do you? i.e., a rule like flash*.ocx, location %windir%, search subdirs yes, and do not Exclude files in the Windows directory. Then at your convenience, wipe out all those historical collected files. What queries do you have that are based on collected files? Quite honestly. If for whatever reason you do need the files themselves, at least check on your primary site, regedit, HKLM\Software\Microsoft\SMS\Components\SMS_Software_Inventory_Processor, the Maximum Collected Files. You might want to bump that down from the default of 5 to something less-so you don't keep lots of versions of each file from a client.Ĭorrect, you'd want a collection query something like this (test it in Queries first) select SMS_R_System.NetbiosName, SMS_G_System_SoftwareFile.FileName, SMS_G_System_SoftwareFile.FilePath, SMS_G_System_SoftwareFile.FileVersion from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName like "%flash%.ocx" For me, I'd also run the query, then check the FilePath.
and make sure that if you "happen" to have files like Flash%ocx in odd path locations (like backup locations), that you put in the Where statement to also limit to known good filepath locations, like the below, but only if you happen to have a lot of odd FilePath, and you wanted to be sure.
I'd also guess that you would add in something to check for specific FileVersions (I'm guessing). sometimes FlashPlayer, when you installed the newest version, never actually bothered to delete the old versions' ocx files. They weren't in use, but the files still existed.
where SMS_G_System_SoftwareFile.FileName like "%flash%.ocx" and ( SMS_G_System_SoftwareFile.FilePath like "%system32\macromed%" or SMS_G_System_ Not Registered or Missing Error Truly a PIA to figure out sometimes, especially w/Flash. Typically, VSFLEX7.OCX errors are caused by attempting to load a corrupt or missing ActiveX control (Object Linking and Embedding control) associated with P-touch PT-1950/1960. Ordinarily, installing a new version of the OCX file will repair the problem creating the error.
0 kommentar(er)
