Sale!

Test C2010-508: IBM Endpoint Manager V9.0 Fundamentals

$108.00 $68.00

Product Description

Exam Code: C2010-508

Exam Name: IBM Endpoint Manager V9.0 Fundamentals

Q & A : 47 Q&As

Version: PDF

Sample: C2010-508 Free Online Test

Product Description

Test information:

Number of questions: 47
Time allowed in minutes: 75
Required passing score: 78%
Languages: English

Objectives:

Section 1:IBM Endpoint Manager Architecture

Given the need to understand IBM Endpoint Manager (IEM) architecture and component configuration, describe the IEM architechure and component configuratuion so that it can be accurately explained to a client.
With emphasis on performing the following tasks:
IEM server – A collection of interacting services, including application services, a Web server, and a database server, forming the heart of the IEM system.
IEM Console – The IEM Console allows an authorized user to quickly and simply distribute content to each computer that needs them without impacting any other computers in the network.
Agent – Agents are installed on every device that you want to manage using IEM.
IEM relay – IEM relays Increase the efficiency of the system. Instead of forcing each networked computer to directly access the IEM server, relays spread the load. Hundreds to thousands of IBM Endpoint Manager clients can point to a single IEM relay for downloads, which in turn makes only a single request to the server.
Web Reporting – IEM Web Reporting is a high-level Web application that complements and extends the power of IEM. It connects to one or more IEM databases to aggregate and analyze your entire network. It allows you to visualize your data, with both charts and data listings, in any standard web browser
Given a need to perform patch management on endpoints, define the supported patching platforms so that systems can be effectively patched.
With emphasis on performing the following tasks:
Windows
Red Hat
OS X
AIX
CentOS
VMWare ESX & ESXi
HP-UX
Solaris
SUSE
Ubuntu
Given a need to perform supported 3rd party applications on endpoints, define the supported 3rd party applications so that applications can be effectively patched.
With emphasis on performing the following tasks:
Adobe Acrobat Flash Player
Adobe Acrobat
Adobe Reader
Adobe Shockwave Player
Apple iTunes
Apple Quicktime
Google Chrome
Mozilla Firefox
RealPlayer
Skype
Oracle Java Runtime Environment
Winamp
WinZip
Given a need to troubleshoot agents on endpoints, define the content and default location of agent logs so that agent log review is possible.
With emphasis on performing the following tasks:
The agent log defines the status of what the agent is doing including:
Relay Registration
Content Applicability
Site Subscriptions
Action Result Status
Windows – C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\__Global\Logs or C:\Program Files \BigFix Enterprise\BES Client\__BESData\__Global\Logs
Linux – /var/opt/BESClient/__BESData/__Global/Logs
OS X – /Library/Application Support/Bigfix/BES Agent/__BESData/__Global/Logs
AIX – /var/opt/BESClient/__BESData/__Global/Logs
Given a need to troubleshoot agents on endpoints, define the name of the IEM service so that troubleshooting is possible.
With emphasis on performing the following tasks:
Windows – BES client
Linux – BESClient
OS X – BESAgent
AIX – SBESClientd
Given the need to ensure certain endpoints cannot be targeted by an action, define how to lock and unlock an endpoint so that there is an existing mechanism to stop actions from being taken on an endpoint.
With emphasis on performing the following tasks:
Definition:
Locking a computer lets you exclude specific computers or groups of computers from the effects of fixlet actions. This could be useful if you want to insulate certain development computers from any changes or updates. Client computers can be locked forever until explicitly unlocked.
Lock the endpoint:
The end user can use BES Support Task ID 295 – BES Client Setting: Lock computer to manually lock an endpoint so that actions cannot be taken against it.
The end user can also right click on a computer, select Edit Computer Settings, check the Locked box, and hit okay to lock a specific endpoint
Unlock the endpoint:
The end user can use BES Support Task ID 296 – BES Client Setting: Unlock computer to manually unlock an endpoint so that actions can be taken against it.
The end user can also right click on a computer, select Edit Computer Settings, uncheck the Locked box, and hit okay to unlock a specific endpoint
Computer Maintenance Window:
The end user can use Maintenance Window Dashboard located under BigFix Management -> Maintenance Windows Management in conjunction with BES Support Task ID – 769: Enforce Maintenance Window with Client Locking to automatically manage the locking and unlocking of a computer on a schedule.

Section 2:IBM Endpoint Manager Console

Given the need to troubleshoot missing content in the IBM Endpoint Manager (IEM) Console, perform the steps necessary to clear the cache and refresh the IEM Console so that the console forces an update to the console data.
With emphasis on performing the following tasks:
In the IEM Console, click “Refresh Console” button to update the console information.
Determine if expected content is now present in the IEM console.
Select option to clear cache:
File -> Preferences -> clear Cache
Restart IEM Console.
Log in to IEM Console and determine if missing content is now present.
Given the need to search for content in the List Panel of IBM Endpoint Manager (IEM) Console, log in to the IEM Console and navigate to the List Panel so that you can search for the appropriate information.
With emphasis on performing the following tasks:
Log in to IEM Console.
Click on anything in the Navigation Tree to show the List panel. Searches can be performed on anything in the List panel.
Given the need to update the content of the IEM Console, select the “Refresh Console” button so that you can refresh the content of the IEM Console.
With emphasis on performing the following tasks:
The Refresh Console button will reload the content from the database for the IEM Console display.
Given a need to force a client to check in to IEM server and update properties in the IEM Console, execute a “Send Refresh” option against a client so that the client will report to the IEM server.
With emphasis on performing the following tasks:
Explain the agent Send Refresh option.
Select the Computer.
Select the option “Send Refresh”.
The agent Send Refresh option sends a UDP packet telling the client to report to the IEM server.
Given the need to show hidden content and show non-relevant content within the IEM Console, select the box “Show Hidden Content” and “Show Non-Relevant Content” in the IEM console so that you can view all content for the appropriate information.
With emphasis on performing the following tasks:
Log in to IEM Console.
Select “Show Hidden Content” to show content that has been hidden by an operator.
Select “Show Non-Relevant Content” to show all content in the IEM Console regardless of relevance.
Given the need to navigate in the IEM Console, list the Endpoint manager domains and their purpose so that the user can efficiently find the items they need in the console.
With emphasis on performing the following tasks:
All Content – This contains every item that exists in the IEM Console.
BigFix Management – This contains all the content related to the management of the Endpoint Manager infrastructure.
Endpoint Protection – This contains content related to Anti-Virus, DLP, Device Management, and Self Network Quarantine.
Mobile Device Management – This contains all content related to the management of Mobile Devices, such as iOS and Android.
Patch Management – This contains content related to the updating of Operating systems and specific applications.
Security Configuration – This contains content related to the Security Configuration Checklists such as DISA STIG, FDCC , and CIS, and also Vulnerability Content.
Systems Lifecycle – This contains content related to Asset Discovery, Inventory, Software Distribution, OS Deployment, Software Usage Analysis, Remote Control.
Server Automation – This contains content related to Virtualization Platform management, using the Automation engine, and middleware content.
BigFix Labs – This contains beta and homegrown content to be used at the user’s own risk.
Certain domains may not be viewable depending upon licensing or permissions.
Given the need to create a grouping of endpoints, explain the difference between an automatic and manual group so that the most effective group is used at the appropriate time.
With emphasis on performing the following tasks:
Definition:
A manual group is a group whose members are static, until a user specifically adds or removes an endpoint to the group.
An automatic group is a group whose members are dynamically set by some type of membership relevance that can include anything from a value of a property to the membership of another group.
Addition and removal of members:
Manual:
-Addition – an endpoint is added to a manual group, by right clicking on it and selecting add to manual group, and then completing the manual group menus.
– Deletion – a member is removed from a manual group, by right clicking on it and selecting remove from manual group while in the computer group menu item, All Content -> Computer Groups. Computers deleted from the IEM Console are removed from manual groups.
Automatic:
– Members are automatically added and removed by the relevance created for group membership. If an endpoint needs to be included or removed from the group, the relevance will need to be changed.
Additional Notes:
New endpoints will join the Automatic groups when they become relevant for the group definition.
Manual groups cannot be exported.
Given an environment that has enough endpoints to require the grouping of computers, explain the process for creating, modifying, and deleting computer groups so that an operator can successfully manage their environment.
With emphasis on performing the following tasks:
Create Groups:
Manual:
– From the Tools menu, or from the Computer Group Menu (All Content -> Computer Groups), right click in the windows containing the existing groups.
– Select Create New Manual Group.
– Enter Group Name and hit Create.
Automatic:
– From the Tools menu, or from the Computer Group Menu (All Content -> Computer Groups), right click in the windows containing the existing groups.
– Select Create New Automatic Group.
– Enter Group Name, select the site in which it should be created, the domain in which it should be created, use the wizard to create the relevance that will include the endpoints in the group and hit Create.
Delete Groups:
In the Computer Group menu, right click on the existing group to remove and the select remove or after selecting the group, hit the remove button in the bottom window pane.
Modify Groups:
Addition and removal of members:
-Manual:
-Addition – an endpoint is added to a manual group, by right clicking on it and selecting add to manual group, and then completing the manual group menus.
-Deletion – a member is removed from a manual group, by right clicking on it and selecting remove from manual group while in the computer groups menu item.
-Automatic:
-Members are automatically added and removed by the relevance created for group membership. If an endpoint needs to be included or removed from the group, the relevance will need to be changed.
Editing the group:
-The only modification a manual group allows is if the membership is determined by console assignment, or by client settings. This can be changed by from the Computer Group menu (All Content -> Computer Groups), right click on the existing group and selecting edit or by selecting the existing group, and hitting edit in the lower pane.
-An automatic group allows you to edit the domain it is in as well as editing the relevance that is determining group membership.. This can be changed by from the Computer Group menu (All Content -> Computer Groups), right click on the existing group and selecting edit or by selecting the existing group, and hitting edit in the lower pane.
Given the need to identify the patches to which an endpoint is vulnerable, define ways to see the patch vulnerability status, so an operator can determine which patches are needed to resolve any vulnerability issues.
With emphasis on performing the following tasks:
Via the Console:
Via the Computer View:
-Browse to All Content domain-> Computers in the console.
-Select a computer of which you wish to find a status.
-Select the Relevent Fixlets and Tasks tab.
-Expand the tree on the left to filter as needed, the content will be displayed in the Work Area.
Via the Group View:
-Browse to All Content domain -> Computer Groups in the console.
-Select the computer group for which you wish to find a status.
-Select the Relevent Fixlets or ApplicableTasks or Relevant Baseline tab.
-Expand the tree on the left to filter as needed; the content will be displayed in the Work Area.
Via the Patch Overview Dashboard:
-Browse to Patch Management -> Patch Overview Dashboard.
-Select the patch site in the pull down on the right.
-The dashboard will provide statistics on patch status as well as the most relevant critical items in the deployment.
Via the Content View:
-Via All Content:
-Browse to All Content domain-> Fixlets and Tasks.
-Expand the tree in the Domain Panel to filter as needed; the content will be displayed in the List Panel.
-Via Patch Content:
-Browse to Patch Management domain.
-Select the sub content in the Domain Panel, and expand the tree as needed, the content will be displayed in the List Panel.
Via Web Reports:
Log in to Web Reports.
Select Report List.
Select Open Vulnerabilities.
Filter the report as appropriate.
Section 3:Properties and Analyses
Given the need to perform IBM Endpoint Manager (IEM) Console operations in a customer’s network and console access as a non master operator in the customer’s environment, define managed properties and explain how they can be utilized in the context of action targeting and reporting so that fixlets and tasks can be accurately actioned and reported upon after completion.
With emphasis on performing the following tasks:
Define a managed property.
A Managed Property is a predefined variable and data pair.
The data is gathered from endpoints and returned back to the server on a configurable scheduled frequency.
Using a Managed Property allows for establishing regular reporting intervals without redefining the data points for each report.
Managed Properties can be defined by Master and Non Master Operators, though a Non Master Operator’s ability to action the Property can be limited by his or her computer management rights.
Define a retrieved property.
A Retrieved Property is a special kind of Managed Property. Like a Managed Property, a Retrieved Property is a predefined variable and data pair.
A Retrieved Property is by default assigned to Action Site and can only be configured by a Master Operator, requiring the property to reside in Action Site.
Because of the requirement to reside in Action Site, Retrieved Properties are generally reserved for values that are global to the implementation, or properties that would be defined for the majority of the endpoints.
Retrieved Properties can be used as column headers within the IEM console. #Retrieved Properties can be used as targeting filters for an action.
Given the need to perform IEM Console operations in a customer’s network, and +$Given console access as a non master operator in the customer’s environment so that fixlets and tasks can be accurately actioned and reported upon after completion.
With emphasis on performing the following tasks:
Explain the methods to view computer properties in the IEM Console.
Navigate to an analysis. View the results.
-Log on to the IEM Console.
-Navigate to All Content Domain.
-Navigate to Analyses node.
-Select an analysis from the List Panel.
-Select the results tab in the workspace.
View a Retrieved Property as a Console Filter.
– Log on to the IEM console.
-Navigate to All Content Domain.
-Navigate to Computers node.
-At the top of the List Panel, right click on the column headers. A dialog will pop giving a list of columns that can be added.
-Select a property name.
-The column will display on the far right in the List Panel of the console.
-If there are results in the field that can be used for filtering, the property is receiving returned results from the endpoints.
View a Retrieved Property from the Console Edit menu.
-Log on to the IEM Console.
-Navigate to Tools, Manage Properties.
-Properties are viewable in the dialog and can be filtered by content type for easier navigation.
Explain the method to view computer properties in IEM Web Reports.
Log on to Web Reports.
Select Explore Data.
Select Computers.
In the Computers section, select Edit Columns.
Select the Property name.
The property column is displayed with results for computers that were targeted with the property.
Explain methods to view computer property definitions in IEM Console.
Navigate to an analysis. View the property definitions.
-Log on to the IEM console.
-Navigate to All Content Domain.
-Navigate to Analyses node.
-Select an analysis from the List pane.
-Each property and its definition can be found by selecting the Details tab.
View a Retrieved Property definition from the Console Edit Menu.
-Log on to the IEM Cconsole.
-Navigate to Tools, Manage Properties.
-Select a property. It’s definition will display underneath the property name.
Explain the methods to verify properties are returning results.
Navigate to an analysis. View the results.
-Log on to the IEM Console.
-Navigate to All Content Domain.
-Navigate to Analyses node.
-Select an analysis from the List Panel.
– Select
-If the results tab displays property names and results, the property is returning results.
Add a Retrieved Property as a Console Filter.
-Log on to the IEM Console.
-Navigate to All Content Domain.
-Navigate to Computers node.
-At the top of the List Panel, right click on the column headers. A dialog will pop giving a list of columns that can be added.
-Select a property name.
-The column will display on the far right in the List Panel of the console.
-If there are results in the field that can be used for filtering, the property is receiving returned results from the endpoints.
View the property results in Web Reports.
-Log on to Web Reports.
-Select Explore Data.
-Select Computers.
-In the Computers section, select Edit Columns.
-Select the Property name.
– Validate that the column is populated with results for computers that were targeted with the property.
Explain the method to determine the frequency that a Managed Property is evaluated by an endpoint.
In the IEM console, navigate to Tools, Manage Properties.
-Select the property from the list
-The evaluation frequency will be at the bottom of the dialog in a field next to the word “Evaluate.”
In the IEM Console, navigate to All Content Domain.
-Navigate to Analyses.
-Select the analysis from the List Panel.
-In the details for the analysis, locate the managed property name.
-Underneath the property name will be an interval value next to the word “Period.”
Given the need to perform IEM console operations in a customer’s network, and given console access as a non master operator in the customer’s environment, define managed properties and explain how they can be utilized in the context of action targeting and reporting so that fixlets and tasks can be accurately actioned and reported upon after completion.
With emphasis on performing the following tasks:
Define an analysis and explain how it is used.
An analysis is a collection of one or more managed properties that can be evaluated by an endpoint.
The property definition is contained within the analysis.
An analysis is IEM Content in that it can be actioned like a fixlet and a task can be actioned.
An analysis has applicability relevance that determines which endpoints should return results for the properties.
An analysis is typically used for collections of like data and is often created as a report souce for content deployment. For example, an analysis for a software deployment might contain three properties.
-Property A – names of endpoints that are true the software deployment task applicability relevance.
-Property B – names of endpoints where the software being deployed has already been successfully installed along with the installation date.
-Property C – names of endpoints where the software was installed but failed, along with the date of most recent attempt, and the failure exit code.
Explain how to create an analysis.
Log on to the IEM Console.
Navigate to All Content.
Navigate to Analyses.
In the List Panel, right click and select Create New Analysis.
Define the Name.
Select the site and domain for the analysis to reside.
Populate the Description tab.
Populate the Properties tab, multiple properties can be created. Each must have a name and defintion.
-Property Name
-Property Definition
Populate the Relevance tab, this is applicability relevance for the entire analysis. All endpoints that resolve to True would return results for the analysis if they are subscribed to the site where the analysis resides.
The analysis must be activated in order to return results. By default a newly created analysis will activate on Save.
To avoid automatic analysis activation, deselect the Automatically activate this analysis after it is created check box.
Explain how to modify an analysis.
Log on to the IEM Console.
Navigate to All Content.
Navigate to Analyses.
Select the analysis in the List Panel.
Right-click on the analysis, select Edit.
The analysis can be modified. No changes will take place until the modified analysis has been saved.
Note that analyses in external sites may not be modified.
Explain how to delete an analysis.
Log on to the IEM Console.
Navigate to All Content.
Navigate to Analyses.
Select the analysis in the List Panel.
Right-click on the analysis, select Delete.
Note that analyses in external sites may not be deleted.

Section 4: Fixlets, Tasks and Baselines

Given the need to perform IBM Endpoint Manager (IEM) Console operations in a customer’s network, and given console access as a non master operator in the customer’s environment, determine whether the use of a fixlet or task is more appropriate for a use case.
With emphasis on performing the following tasks:
Define a fixlet.
A fixlet is an object with content that can be applied to one or more endpoints in an IEM environment.
A fixlet typically makes configuration changes to an endpoint such as installing a file or modifying an Operating System setting.
A fixlet has applicability relevance that forces an endpoint to report whether the content is relevant or not. If relevant, the fixlet can be applied or actioned.
A fixlet has configurable success criteria to determine whether the change was successful, or “fixed.” By default, success criteria is that the applicability relevance evaluated to false after the fixlet has been applied.
A fixlet is typically used to enforce a policy because the state of the endpoint is checked before and after the fixlet is applied.
List the action states for a fixlet.
Once applied, an action will proceed through one or more states. If the action was applied to a fixlet, the following action status can be defined as:
Not Relevant – Before running the action, the IEM Client checked the relevance for the action and it is no longer true.
Evaluating – The IEM client has received the action targeted at it and will evaluate the action to see if it is time to run, the issue is still relevant, etc.
Running – The IEM client is currently running the action.
Fixed – The IEM client has run the action and the relevance is now false (meaning that not only did the action run, but it fixed the issue). *This is unique to a fixlet. A task action can not report this status.
Failed – The IEM client has run the action and the fixlet is still relevant (even if the action ran successfully). Note that in the cases of fixlets, ‘Failed’ usually means the action script completed successfully, but failed to meet the success criteria. *Failed if the action completed successfully means the applicability relevance still evaluates to True. This issue is unique to a fixlet.
Locked – The IEM client is in the “Locked” state that prevents it from running actions until unlocked.
Pending Download – The IEM client is waiting to receive the complete file. This state will persist until the download makes it to the IEM Server -> IEM Relay -> IEM Client.
Pending Restart – The action was completed, but the action status of ‘Fixed’ or ‘Failed’ cannot be assessed until the computer is restarted. *This is unique to a fixlet. A task action does not typically wait for a restart.
Waiting – The IEM Client is waiting for some condition to actually run the action. The waiting conditions include: waiting for user input, waiting to retry after failure, waiting for a time/date range, waiting for a distribution time, waiting for a user to login, and waiting until the custom constraints property becomes relevant.
Restricted – The IEM client can’t run the action because the IEM license is expired or the number of computers is exceeded.
Cancelled – The user clicked the “cancel” button when prompted with a message box.
Expired – The action expired before the IEM client could run the action.
Not Reported – No report has yet been received from the endpoint for the action taken. We cannot confirm if the action has been propagated, mirrored, gathered, processed, or reported until this status changes to something else.
This result status means the console is not able to process the status report it received from the endpoint. This usually occurs when the server is an earlier version than the client.
Constrained – When the constraint for the action has not been met.
Define a task.
A task is an object with content that can be applied to one or more endpoints in an IEM environment.
A task has no typical definition other than including action script that can make a change to an endpoint or its client settings.
A task has applicability relevance that forces an endpoint to report whether the task is relevant or not. If relevant, the task can be applied or actioned.
A task does not have success criteria. The only success definition for a task is that all lines of the action script have completed successfully.
A task is typically not used for policy enforcement. It is often used for one-time configuration changes or situations where the endpoint state does not need to be checked after the task has been applied or executed.
List the action applications and completion states for a task.
Once applied, an action will proceed through one or more states. If the action was applied to a fixlet, the following action status can be defined as:
Not Relevant – Before running the action, the IEM client checked the relevance for the action and it is no longer true.
Evaluating – The IEM client has received the action targeted at it and will evaluate the action to see if it is time to run, the issue is still relevant, etc.
Running – The IEM client is currently running the action.
Failed – The IEM client has run the action and failed at one or more of the action script lines.
Locked – The IEM client is in the “Locked” state that prevents it from running actions until unlocked.
Pending Download – The IEM client is waiting to receive the complete file. This state will persist until the download makes it to the IEM Server -> IEM Relay -> IEM client.
Waiting – The IEM client is waiting for some condition to actually run the action. The waiting conditions include: waiting for user input, waiting to retry after failure, waiting for a time/date range, waiting for a distribution time, waiting for a user to login, and waiting until the custom constraints property becomes relevant.
Restricted – The IEM client can’t run the action because the IEM license is expired or the number of computers is exceeded.
Cancelled – The user clicked the “cancel” button when prompted with a message box.
Expired – The action expired before the IEM client could run the action.
Completed – The action has completed and no other actions are required. *This is unique to a task. A fixlet would report either “fixed,” or “failed,” if it had completed and no other actions were required.
Not Reported – No report has yet been received from the endpoint for the action taken. We cannot confirm if the action has been propagated, mirrored, gathered, processed, or reported until this status changes to something else.
This result status means the console is not able to process the status report it received from the endpoint. This usually occurs when the server is an earlier version than the client.
Constrained – When the constraint for the action has not been met.
Given the need to perform IEM Console operations in a customer’s network, and given console access as a non master operator in the customer’s environment, create, edit, delete a baseline and sychronize the components of a baseline.
With emphasis on performing the following tasks:
Define a baseline.
A baseline is a collection of related content that is intended to be targeted at a selection of endpoints.
The purpose of a baseline is to streamline the creation and management of actions. For example, rather than create 5 actions for 5 separate fixlets to the same set of endpoints, one action can be created for a baseline containing all 5 fixlets.
Each content item inside the baseline, such as a fixlet or task, is referred to as a component of that baseline.
If the component has been updated, the baseline requires an update for the new version of that component. Updating a baseline in this manner is sometimes called “synchronizing components.”
List the action states for a baseline.
Once applied, an action will proceed through one or more states. If the action was applied to a baseline, the following action status can be defined as:
-Not Relevant – Before running the action, the IEM client checked the relevance for the action and it is no longer true.
-Evaluating – The IEM client has received the action targeted at it and will evaluate the action to see if it is time to run, the issue is still relevant, etc.
-Running – The IEM client is currently running the action.
-Fixed – All the fixlet components of the baseline have completed successfully.
-Failed – The IEM client has run the action and one or more fixlets are still relevant (even if the action ran successfully). Note that in the cases of fixlets, ‘Failed’ usually means the action script completed successfully, but failed to meet the success criteria. *Failed if the action completed successfully means the applicability relevance still evaluates to True. This issue is unique to a fixlet, whether the fixlet is in a baseline or not.
-Locked – The IEM client is in the “Locked” state that prevents it from running actions until unlocked.
-Pending Download – The IEM client is waiting to receive the complete file. This state will persist until the download makes it to the IEM Server -> IEM Relay -> IEM Client.
-Pending Restart – The action was completed, but the action status of ‘Fixed’ or ‘Failed’ cannot be assessed until the computer is restarted. *This is unique to fixlet components.
-Waiting – The IEM client is waiting for some condition to actually run the action. The waiting conditions include: waiting for user input, waiting to retry after failure, waiting for a time/date range, waiting for a distribution time, waiting for a user to login, and waiting until the custom constraints property becomes relevant.
-Restricted – The IEM client can’t run the action because the IEM license is expired or the number of computers is exceeded.
-Cancelled – The user clicked the “Cancel” button when prompted with a message box.
-Expired – The action expired before the IEM client could run the action.
-Not Reported – No report has yet been received from the endpoint for the action taken. We cannot confirm if the action has been propagated, mirrored, gathered, processed, or reported until this status changes to something else.
– This result status means the console is not able to process the status report it received from the endpoint. This usually occurs when the server is an earlier version than the client.
-Constrained – When the constraint for the action has not been met.
Create a baseline.
Add to New Baseline.
-Log on to the IEM Console.
-Navigate to All Content.
-Navigate to Fixlets and Tasks node.
-In the List Panel, right-click on content and select Add to New Baseline.
Create New Baseline.
-Log on to the IEM Console.
-Navigate to All Content.
-Navigate to any node with fixlet or task content.
-In the List Panel, right-click on content and select Create new Baseline
-Give the baseline a name.
-Select the site and domain for the baseline location.
-Save
Modify a baseline.
Deleting or re-arranging baseline content.
-Log on to the IEM Console.
– Navigate to All Content.
-Navigate to Baselines node.
-In the List Panel, right-click on baseline and select Edit. * Note that subscription baseline content may not be edited.
-The baseline may now be edited.
-Click Save to retain edits.
Add a component to an Existing Baseline.
– Log on to the IEM Console.
-Navigate to All Content.
-Navigate to Fixlets and Tasks node.
-In the List Panel, right-click on content and select Add to Existing Baseline.
Delete a baseline.
Log on to the IEM Console.
Navigate to All Content.
Navigate to Baselines node.
In the List Panel, right-click on baseline and select Remove. * Note that subscription baseline content may not be removed.
Synchronize the components of a baseline.
Edit Baseline.
-Log on to the IEM Console.
-Navigate to All Content.
– Navigate to Baselines node.
-In the List Panel, right-click on baseline and select Edit. * Note that subscription baseline content may not be edited.
-Select the Components Tab.
-Click “Sync all Components” Button.
– Click Save to retain edits.
Via Dashboard.
-Log on to the IEM Console.
-Navigate to All Content.
-Navigate to Dashboards node.
-Navigate to BES Support.
– Select Baseline Synchronization Dashboard.
-In the workspace, select the baseline(s) to synchronize.
-Click the “Sync Baselines” Button.Note: non master operators can only synchronize baselines that they have created.

Section 5:Actions

Given the requirement to understand Default Actions, explain what a Default Action is and how it is used, so that the IBM Endpoint Manager (IEM) Console operator can understand the impact of the Default Action on a fixlet or task.
With emphasis on performing the following tasks:
Explain how to determine if a fixlet or task have a Default Action.
Open the IEM Console.
Locate desired fixlet/task.
Right click on fixlet/task to see pop-up menu.
-If the “Take Default Action” is enabled, click on it to open the Take Action dialog.
-If the “Take Default Action” is disabled, there is no default action available for this task.
Allow for actions to be taken quickly by right clicking on the fixlet/task and selecting “Take Default Action”.
Note: if there is not a Default Action set, this usually means that there is some special instruction for the fixlet or task. This will require the operator to review the Description tab to determine the correct course of action.
Explain how the use of the Default Action impacts different functions.
-Allow for actions to be taken quickly by right clicking on the fixlet/task and selecting “Take Default Action”.
-Allow for quick creation of multiple action groups (MAG) by selecting multiple fixlets/tasks and then right clicking and selecting “Take Default Action”.
– If added to a Basline, the Default Action is used automatically as the action. If there is no defined Default Action, the desired action has to be manually selected.
Given access to the IEM Console, identify the options available to execute an action so that a successful action can be taken.
With emphasis on performing the following tasks:
Explain the use of the Target tab.
Select Devices – selectable list of computers that are relevant to the fixlet.
Dynamically target by property – the action selects any IEM client computer with the retrieved property specified.
Enter device name – manually entered list of targets to be used by the action.
Explain the use of the Execution tab.
Contraints – allow for the start and end dates/times along with other scheduling requirements.
Behavior – options set for how the action will be performed. This includes failure retry, reapplication, download pre-caching and download staggering.
The Execution tab is also used to set up the action as a Policy Action.
-Use the Ends on field to set the expiration of an action. But deselecting the Ends on checkbox, the action will continue to run until manually stopped.
– Use the Reapply this action section to allow the action to be executed again if it becomes relevant.
Explain the use of the Users tab.
Run only when there is no user logged on – only allow action to start when there is no user logged on to the target system.
Run independently of user presence, and display the user interface to the specified users – will run the action no matter if there is a user logged in or not. Also allows for the selection of user ids for running user interfaces.
Run when at least one of the specified users is logged on, and only display the user interface to those users – requires a specified user id to be logged in before the action can be taken.
Explain the use of the Messages tab.
Display message before running action – will display an interface to the user notifying of an action that is going to be taken.
-Set Deadline – allows for a deadline for the action to occur, once the deadline is reached, the action can be taken automatically or a message is kept topmost until the user accepts the action.
Display message while running action – Allows for a message to be displayed while the action is being taken.
Note: additional configuration may be required for this to be visible by the end user.
Explain the use of the Offer tab.
The Offer tab you can advertise a list of actions (typically optional patches or updates) to the IEM client user.
Note: additional configuration may be required for this to be visible by the end user.
Explain the use of the Post-Action tab.
The Post-Action tab you can set to restart or shut down the client computer after the action has completed.
Explain the use of the Pre-Execution Action Script tab.
The Pre-Execution Action Script tab of the Take Multiple Actions dialog you can create an action script that runs before the chosen set of actions is run.
Explain the use of the Post-Execution Action Script tab
The Pre-Execution Action Script tab of the Take Multiple Actions dialog you can create an action script that runs after the chosen set of actions is run.
Explain the use of the Applicability tab.
The Applicability tab you can specify the criteria to use to judge the relevance of a Fixlet action. This can be the relevance from the source fixlet/task or custom relevance.
Explain the use of the Name field.
Name of the action as it appears in the action list. Entering meaningful names will help with searching for submitted actions.
Explain the use of Presets.
Presets allow for common action options to be saved for use on future actions.
Given access to the IEM Console and the requirement to review the status of the targets for an action, identify the steps required to provide the IEM Console operator with the detailed status for an action so that the operator can determine the current status of the targets for an action.
With emphasis on performing the following tasks:
Open IEM Console.
Navigate to the All Content domain- > Actions.
Search for desired action.
Open action and click on Summary tab.
Review the various statuses.
Running: The Action is currently running.
Evaluating: The Action is still evaluating its relevance.
Failed: The Action has failed to run correctly.
Cancelled: The user has canceled the Action.
Download Failed: The Action failed to complete the download.
Locked: The computer is locked and cannot run the action.
Offers Disabled: Offers cannot be presented on the specified client, so the Action will never run.
Waiting: The Action is waiting for a user response.
Pending Downloads: The Action is waiting for downloads.
Pending Restart: The Action is waiting for a restart from the Client computer.
Pending Message: The Action is waiting for the user to accept the Action message.
Pending Login: The Action is waiting for the user to log in for a user-assisted Action.
Pending Offer Acceptance: The Action is waiting for the user to accept the offer.
Constrained: The Action has been constrained by a Relevance statement set in the Execution tab of the Take Action Dialog.
Expired: The Action has passed its expiration date.
Postponed: The Action has been postponed by the client.
Invalid Signature: The Action cannot run due to an invalid signature.
Not Relevant: The Action is not relevant on this client.
Not Reported: The Action has not reported its success or failure.
Error: The Action has resulted in an error.
Fixed: The Action has completed, resolving the issue.
Given access to the IEM Console, navigate to the Actions list and review the various types of “states” so that you can determine the status of each action.
With emphasis on performing the following tasks:
Open IEM Console.
Navigate to the All Content domain- > Actions.
Search for desired action and review current state.
Open – The action is active on one or more computers. It remains open until its expiration date elapses, or an operator stops it.
Expired -Expired means that the action has reached the end date and will no longer be executed on the targets.
Stopped – The action was stopped by an operator. It remains stopped until its expiration date elapses or it is removed.
Given the failure of an IEM action on a Windows endpoint, use various troubleshooting techniques to determine the failure cause so that remediation can be done to allow for a successful action to be taken.
With emphasis on performing the following tasks:
Ensure the IEM client is running on the target system.
Launch “services.msc”.
Remotely connect to target system from the Services window.
Find “BES Client” service.
Start service if not in running state.
Review contents of IEM client log file for possible error messages.
Remotely connect to target system.
In Windows Explorer, navigate to (default path) “C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData\__Global\Logs”.
Open most recent file in Notepad.
Review log file for error message related to action. Search for action id or command line.
Review action status for specific target for detailed failure message.
Open IEM Console.
Navigate to the All Content domain -> Actions.
Search for desired action.
Open action and click on Target tab.
Search for failed target and double click to open the “View Action Info” dialog.
Review the information in the Summary section for detailed information.
Utilize the BES Client Diagnostics utility.
Open the IEM Console.
Navigate to the All Content domain-> Select the Fixtlets and Task node.
Filter the List Panel using the word diagnostics.
Take action on the task TROUBLESHOOTING:Run BES Client Diagnostics (353 in the BES Support site).
Evaluate the BES Client Diagnostic results.

 

Reviews

There are no reviews yet.

Be the first to review “Test C2010-508: IBM Endpoint Manager V9.0 Fundamentals”