(imported topic written by SystemAdmin)
After upgrading our dev environment to v8.0 a few weeks ago, we are trying to sort out some of the new behaviors we are seeing. I’m interested to see if anyone else has experienced what we are seeing.
In post http://forum.bigfix.com/viewtopic.php?id=5531, I detail how a NMO action on a NMO created custom task in a custom site fails. Interestingly, a MO can successfully take action on the NMO’s task to the same target machines.
I’m finding some strange baseline behavior in v8.0. For example, I have a several individual custom tasks in a custom baseline. Target machines are relevant for each individual task. When the baseline containing the same individual tasks is run on target machines, I get unexpected and incomplete results. Some tasks show a mix of expired, complete, and not relevant when they should all be complete. If I run the same individual tasks manually in the same sequence, they work as expected.
In another case, the tasks marked as Expired should have been Not Relevant. The tasks listed as Not Relevant actually finished correctly and should have a Complete status.
In another example, I sometimes incorporate one or more reboots within a baseline. It seems that after the first reboot, the baseline shows “complete†, but the remaining tasks expired or not relevant (both incorrect).