bkharmon1 Absent Member.
Absent Member.

Detecting Text file to ID Image

When creating our Universal image, I created a .txt file on the image in system32 to ID this image from last years image. Is it at all possible to create a query and Local product using this .txt file?
Labels (1)
3 Replies
bkharmon1 Absent Member.
Absent Member.

Re: Detecting Text file to ID Image

OK, so the query isn't such a big deal. I know how to create a custom query for a specific file existence. However, the specified .txt file isn't in the database or being scanned for.
Anonymous_User Absent Member.
Absent Member.

Re: Detecting Text file to ID Image

The only thing I can think of doing is within the Manager under the
Default Option Set--Collector Tab is to check the Collect Software File
Information and then the Additional Extensions and add txt to the field
box (note: not .txt, just txt). Then you could do your query against that
filename.txt. Note that this will scan ALL txt files. I haven't seen or
know of a way myself to go after just one particular txt file. I know you
go after a registry key, so what you could perhaps do is get the machines
that have this image with the scan described above and then push a
registry key to them that identifies this image. Then going forward make
sure all the machines with whatever image have a key to identify it and
then you could do a UDF based on that key in the registry and then you
could turn off scanning for all txt files in the manager. Hopefully
someone else might have a better suggestion. The only other thing I can
see doing is adding the path and filename in the Retrieve Configuration
Files section, but that will only show up in Auxiliary data and I don't
think you can query against that anyway.

Anonymous_User Absent Member.
Absent Member.

Re: Detecting Text file to ID Image

I agree with Dan's suggestion:

ZAM can read:
- Registry entries
- System environment variables
- WMI-accessible data (e.g. BIOS)

Therefore if you can push that information into any of these three
formats, you can pick them up into a UDF.

Maybe write a script (in VBScript or using AutoIT would be good) to find
the text file, parse it for version information within the file, and put
this information into a custom registry entry of your choice.

You can tell ZAm to collect individual files, such as whatever.tx, but
this retrieves the entire file and stores it outside the database - it
does not read the contents into the workstation record.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.