Taking custom blank actions to troubleshoot and verify deployment operations

Technote (troubleshooting)


Problem(Abstract)

Steps on how to take a blank action for the purpose of testing and verifying deployment operations.

Resolving the problem

Taking a blank action to one, some, or all of your endpoints is useful in determining (at the most basic level) if your client endpoints are online, responding to actions, and properly executing actions to completion. If clients are online and able to successfully respond to actions, you should be able to target them with a blank action and expect them to gather the action through the relay infrastructure, merge the action into the client's evaluation loop on the endpoint, execute the action (given that the execution constraints are met: i.e. date/time constraints in the action are met, it is relevant to execute, etc..), and to report the results of completion of the execution of the action back up to the server through the relay infrastructure. Testing in this way can help to validate that an endpoint (at the most basic level) should be able to receive and process all actions regardless of what product solution you are issuing actions through.

Starting in version 9.0 of IEM there are two different types of actions that can be taken: a mailboxed action and a non-mailboxed action.

Mailboxed actions are sent to the client endpoint's specific mailbox site. And only the client for which a targeted mailbox action is targeted at will be notified that a new action is ready to be gathered and executed.

Non-mailboxed actions are deployed either via the main actionsite (if the action is taken by a master operator). Or via an operator specific opsite (if taken by a non-master operator). The endpoints that are subscribed to to the main actionsite (all clients in the deployment are subscribed to the main actionsite) will be notified of the new version of the actionsite and gather the new version of the actionsite. All computers managed by a specific operator will receive a new version of that non-master operator's opsite every time the non-master operator takes an action.


How to take an actionsite action:

    1. Login to the console as a master console operator.
    2. On the main menu, click Tools > Take Custom Action..



    3. Choose the second the second option in the Target tab
    4. Either click on All Computers (so that it is highlighted) to test deployment wide functionality or choose a specific computer or computer group to limit the test of functionality to specific computers.
    5. Change the name of the action to represent what you are doing (for example: Blank Action)
    6. Click OK.


How to take a mailboxed action:
    1. In the console, on the main menu, click Tools > Take Custom Action..
    2. Choose either the first or third option in the Target tab


    3. Select the computer or computers to target. NOTE: If any of the computers selected still have agent versions less than 9.0, the action will go out either as an actionsite action or an opsite action.
    4. Change the name of the action to represent what you are doing (for example: Blank Action)
    5. Click OK.


How to take an operator specific opsite action:
    1. Login to the console as the non-master console operator you would like to test with
    2. On the main menu, click Tools > Take Custom Action..


    3. Choose the second the second option in the Target tab
    4. Either click on All Computers (so that it is highlighted) to test deployment wide functionality or choose a specific computer or computer group to limit the test of functionality to specific computers.
    5. Change the name of the action to represent what you are doing (for example: Blank Action)
    6. Click OK.


Wait several minutes to an hour for results (depending on the current responsiveness of your deployment). Analyze the results to determine if there might be a deployment issue impacting basic functionality.

Historical Number

1771

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Endpoint Manager

Software version:

Version Independent

Operating system(s):

Platform Independent

Reference #:

1506100

Modified date:

2015-01-29

Translate my page

Machine Translation

Content navigation