Baseline and computer group questions

(imported topic written by hanspjacobsen)

I’m trying to set up two computers groups that use the same fixlet messages but carry out the actions in different ways.

The first computer group should be an aggressive one that automatically implements all fixlet actions once they apply no matter if the fixlet was created 10 minutes ago.

The second group should not implement fixlets until it has gone two or three weeks since it was release.

I’ve read the Bes Console guide and the Bes admin guide and haven’t found any answer to my question.

Also is there a way to automatically add new critical fixlets messages to a baseline?

Thanks

Hans Petter

(imported comment written by BenKus)

Hi hans,

By design, there is no way to automatically add Fixlets to a Baseline. This is done as a security and change control protection feature (so you can guarantee that nothing will change “from underneath you” if we update Fixlets or publish new Fixlets). You must approve all changes in your environment by adding the Fixlets to the baseline and taking the action or taking the aciton directly from the Fixlet.

Ben

(imported comment written by hanspjacobsen)

But is it possibel to do the following

I’m trying to set up two computers groups that use the same fixlet messages but carry out the actions in different ways.

The first computer group should be an aggressive one that automatically implements all fixlet actions once they apply no matter if the fixlet was created 10 minutes ago.

The second group should not implement fixlets until it has gone two or three weeks since it was release.

(imported comment written by BenKus)

Hans,

You can take two actions from the same Fixlet (or baseline) that is targeted at two different groups. The first group will apply the action immediately and the second group will apply the action in 2 weeks (using the action scheduling abilities).

However, as mentioned, you will need to re-deploy these two actions every time new Fixlets come about because the system requires you authorize new changes… otherwise a new Fixlet might come out that breaks all your computers and you would have no chance to stop it…

Ben