( All opinions are my own, and does not reflect my employer.)
Ramblings on how to create some fixlets on BigFix.
Background: Big Fix is an IBM application used to deploy patches, upgrade or install rules and can monitor servers/clients that needs this patch - It will automatically inform the client and the client will do a pull (versus a push of the patch from the server ) which is more effective.
Up until IBM bought this, it was called Big Fix and now it is Tivoli End Point manager.
A fixlet is a composition of Rules, Actions and Relevance that describes the patch or an install on the client.
Once this fixlet is deployed with the above, TEM will constantly monitor the clients and deploy them.
My blog here shows a sample on how to write fixlets using different relevance rules on TEM ( Tivoli End Point Manager -Previously called Big Fix )
Note : I am only showing the different relevance rules that can possibly be applied to check if the rpm is present.
Note : Here I am interested in "expect"
Snapshot shows how a relevance is written - that identifies the clients as Linux:
Picture :
One other way to deploy is to identify a specific server on which the package will be deployed.
Picture 3:
Picture 4: Once this is identified - User will write appropriate action scripts to deploy the package.
Ramblings on how to create some fixlets on BigFix.
Background: Big Fix is an IBM application used to deploy patches, upgrade or install rules and can monitor servers/clients that needs this patch - It will automatically inform the client and the client will do a pull (versus a push of the patch from the server ) which is more effective.
Up until IBM bought this, it was called Big Fix and now it is Tivoli End Point manager.
A fixlet is a composition of Rules, Actions and Relevance that describes the patch or an install on the client.
Once this fixlet is deployed with the above, TEM will constantly monitor the clients and deploy them.
My blog here shows a sample on how to write fixlets using different relevance rules on TEM ( Tivoli End Point Manager -Previously called Big Fix )
Note : I am only showing the different relevance rules that can possibly be applied to check if the rpm is present.
Note : Here I am interested in "expect"
Snapshot shows how a relevance is written - that identifies the clients as Linux:
Picture :
One other way to deploy is to identify a specific server on which the package will be deployed.
Picture 3:
Picture 4: Once this is identified - User will write appropriate action scripts to deploy the package.
No comments:
Post a Comment