kroberts210What is the error written to the script log when it fails? Is it possible that these machines haven't finished completely writing the file to disk before the next script command starts trying to execute? I've run into this a few times. Might try adding a pause for a few seceonds between the "Write File" and the "Execute" to allow for any write and scan operations to finish. But again this is just a guess without knowing any of the errors.
djmundyThis is really cool, however one thing I would like to also report on in this area is duplicate license keys. Is this possible?
eg. I have several clients who have just one or two OEM Office CDs floating around and have it installed on many PCs. When I go to Audit > Software Licenses and click on an agent, it shows all of the license codes and a number (with a hyperlink) next to those which are duplicated on other agents.
Benjamin.Lavalley@kaseya.comI can't get into doing that - I'm only able to work within the confines of our scripting / script log / supported reporting methodology...
We can generate reports to show you machines and the licenses they use. You can look at these reports to see if multiple machines are using the same license code, perhaps exporting them to excel and doing some of your own automated parsing of the data.
kroberts210I modified the script a bit to generate a ticket if a blocked VLK is found.
kroberts210No, just an extra step in the script
mbeardenBen - any update on the changes you mentioned making about adding invalid / blocked keys reported from this to the event logs? That would be extremely helpful!
Otherwise - thanks - this will be fantastic!
tmcninchOnce the script has run, how can I create a report to show this information?