quote:
it also leaves room for the ever present file locking issue
Theoretically that is true, but in practice how likely is it to cause a problem?

If it is a real concern then the fix is simple - rather than a software section keyed by the update name, have a status file for each PC which has an entry for each update in a similar form to that described above. You now have a simple software update file:
quote:
update.ini
[SOFTWARE-LIST]
IE60sp1=1
hotfixQ12345=1
...
and for each PC there will be a status file:
quote:
PC02468
[UPDATE-STATUS]
IE60sp1=Ignore
hotfixQ12345=2003-05-30 09:04
Tip: Use a significant part of the workstation name (say the last two digits) to identify a subdirectory for the PC status files. This will stop the number of directory entries getting too large and causing long directory scans.

Advantages are:
  • The status files are very small and quickly scanned/updated
  • A lock on an individual workstations file will not hold up anyone else
  • The status file can be used for recording all manner of useful information about the workstation above and beyond the status of software roll-outs.
Disadvantages are:
  • Only the one really, which is that if you want to disable the update for 100 PCs, you have 100 ini files to edit or create
Of course the overhead of editing many files can be avoided by creating a simple HTML or KiXforms front-end and automating the update.