(imported topic written by nberger91)
Is there an updated version to support db/console v8.1.551.0 running on Win2008 ? http://support.bigfix.com/bes/misc/actionregenerator.html
(imported comment written by nberger91)
Any update ?
Mon Mar 14 05:51:00 2011: Running ActionRegenerator…
Mon Mar 14 05:51:00 2011: WARNING! Could not find the BES API installed version key. The BES API may not be installed correctly or at all.
Mon Mar 14 05:51:00 2011: WARNING! The installed version of the BES API () does not match the installed version of the BES Server (8.1.551.0). The BES Action Regenerator may not function correctly with this installation configuration.
Mon Mar 14 05:51:02 2011: ERROR: Could not find a valid action for the Fixlet specified (Fixlet 4089 of site “actionsite”).
(imported comment written by BenKus)
You should see Fixlets to update the BigFix API in the “BigFix Management” domain.
You only need a new version of the BigFix API and don’t need a new version of the Action Regenerator.
Ben
(imported comment written by nberger91)
How do I skip the option if the associated fixlet doesn’t have a SHA1 for the download ?
Fri Mar 25 07:04:48 2011: ERROR: Can’t seem to find the SHA1 value in the action 0 of Fixlet 4089 of site “actionsite”. (Perhaps it is a different actionid?)
Thanks.
(imported comment written by BenKus)
I think try this line in the config file:
skipverification=1;
Ben
(imported comment written by nberger91)
Tried that, doesn’t work. (used to before upgrading to 8.1.551.0)
Seems to skip if there’s a hash in the action. If the download isn’t hashed, it fails.
My action creates a vbs on th fly, and downloads a txt file which changes daily (hence no hash)
I’ve got the latest api, and latest actionregenerator.exe … ??
(imported comment written by BenKus)
Hey nberger,
Sorry, I gave you wrong information…
The skipverification flag is to skip the verification on the local client (which is a mechanism to make sure that someone was not trying to trick your script into running an unauthorized Fixlet).
For running an action that doesn’t contain an SHA1, I don’t think that will work (and the code hasn’t changed in a few years and from what I can see, it shouldn’t have worked ever)… The reason that it needs to be there is that this SHA1 value of the file is the way the actionregenerator knows to regenerate the action.
I think you can effectively trick the actionregenerator into skipping the error and always reissuing the action by just adding a SHA1 looking string in the action (maybe in a comment). You will need to change it each time you change the action… For instance add:
//sha1:abcdef1234567890123456890123456789012345
Ben
(imported comment written by nberger91)
Thanks Ben, that worked perfectly.