while adding components to baseline I am not able to see all the actions which i have done by taking “custom action” .only few actions are available in tasks .why only few actions are visible?
please help me regarding this issue
Not too sure what you mean.
Are you successful at adding components to a baseline?
Are you referring to the fact that some components do not have default actions and you have to specify which action to execute for that component?
Some fixlet/task components have more than one action available to take, some have 2, 3, or more to choose from.
And some fixlet/task components have only 1 action to choose from but the action is not marked as a default action when you add it to a baseline to prevent you from blindly deploying it in a baseline without having read the important notes in the description of the fixlet/task.
Please clarify the problem you are having.
Also, please take a look at this article I put together on best practices for building baselines:
http://www-01.ibm.com/support/docview.wss?uid=swg21636385
1 Like
In that article you linked:
When taking actions on the baselines, take them as a non-master console operator. This will also help to keep the total size of the master actionsite low.
I would add to this: Don’t do anything as a master operator unless only a master operator can do it. This is important for both Least Privilege reasons, but also to keep the actionsite not just small, but also changing less often.
1 Like
Hi
First of all, an action is something you already have sent to a client, I think you mean Fixlet/Task (which are components for the baseline)?
Is it possible that the component is still non-relevant? This is when you just created an fixlet/task (it needs time to become available in the console) or when there is relevance on your task/fixlet but there are no computers applicable.
When you select a component, make sure to select all tasks (second option)
This will also show the non-relevant Tasks.
The same goes for the console:
Depending what is clicked, you’ll see more/less fixlets/tasks.
But again, as @BigFixNinja asks, please clarify your problem.
1 Like
The impact to the size if the actionsite when this is done is not as dramatic starting in BigFix 9.0 because when you target a computer with an action by name instead of property, it gets deployed via a mailboxsite instead of the actionsite or an opsite. But overall, yes it is still a good practice to separate duties and have non-master console operators take patching actions, reserving the master operator role for deploying administrative types of actions only.
1 Like
what I mean exactly is why all the actions are not visible in tasks even though after enabling “show non relevant content”
Oh, I think I understand what you mean.
If you have a baseline with a bunch of components and you create an action from it, the action history shows up for the baseline and NOT for the individual fixlets or tasks that make up the components.
One of the reasons for this is that baselines contain entire copies of the fixlets and tasks they contain. They don’t actually use the original fixlet or task directly, only the copy of it. The reason for this is that the fixlets or tasks that make up the baseline components could be changed after the baseline is created, which would change the behavior of the baseline itself in unexpected ways. You have to intentionally resync baseline components to cause this to happen.
For these reasons, the baseline action and the components it makes up are not technically tied to the fixlets and tasks themselves, so the action history does not show up there.