ibm bigfix: webui user's guide · document v iews the w ebui’s document views pr esent...

IBM BigFixVersion 9.5

WebUIUser's Guide

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 53.

This edition applies to version 9, release 5, modification level 0 of IBM BigFix and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2016.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Welcome . . . . . . . . . 1

Chapter 2. Meet the WebUI. . . . . . . 3Overview Page . . . . . . . . . . . . . 3Navigation Bar . . . . . . . . . . . . . 5List Views . . . . . . . . . . . . . . . 5Document Views . . . . . . . . . . . . . 6Filters and Search Tools. . . . . . . . . . . 6Text Search . . . . . . . . . . . . . . . 8List Controls . . . . . . . . . . . . . . 9Select All . . . . . . . . . . . . . . . 9Permissions and Their Effects. . . . . . . . . 9WebUI Workflow and Deploy Sequence . . . . . 10

Chapter 3. Get Started with Devices . . 11The Device List . . . . . . . . . . . . . 11Device Documents . . . . . . . . . . . . 12

Chapter 4. Get Started with Patches . . 15The Patch List . . . . . . . . . . . . . 15Patch Documents . . . . . . . . . . . . 16

Chapter 5. Get Started with Software 19The Software Package List . . . . . . . . . 19Software Documents . . . . . . . . . . . 19Software Catalog Operations . . . . . . . . 20

Add a Software Package . . . . . . . . . 20Edit a Software Package . . . . . . . . . 23Delete a Software Package . . . . . . . . 23

Chapter 6. Get Started with CustomContent . . . . . . . . . . . . . . 25The Custom Content List . . . . . . . . . . 25Custom Content Documents . . . . . . . . . 26

Chapter 7. BigFix Query . . . . . . . 27Run a Pre-Defined Query. . . . . . . . . . 28Build a Query . . . . . . . . . . . . . 30

Chapter 8. Take Action: The DeploySequence . . . . . . . . . . . . . 33Deploy Sequence Summary . . . . . . . . . 33

Deploy Procedure . . . . . . . . . . . . 33Configuration Options. . . . . . . . . . 35

Chapter 9. Get Started withDeployments . . . . . . . . . . . . 37The Deployment List . . . . . . . . . . . 37Deployment Documents . . . . . . . . . . 38Monitoring Deployments: State, Status, and Result 38

Device Results . . . . . . . . . . . . 38Deployment Status . . . . . . . . . . . 39Deployment State . . . . . . . . . . . 40Evaluating Deployments With Multiple Actions 40

Stop A Deployment. . . . . . . . . . . . 41

Appendix A. Glossary . . . . . . . . 43A . . . . . . . . . . . . . . . . . . 43B . . . . . . . . . . . . . . . . . . 43C . . . . . . . . . . . . . . . . . . 44D . . . . . . . . . . . . . . . . . . 45E . . . . . . . . . . . . . . . . . . 46F . . . . . . . . . . . . . . . . . . 46G . . . . . . . . . . . . . . . . . . 46L . . . . . . . . . . . . . . . . . . 46M . . . . . . . . . . . . . . . . . 46N. . . . . . . . . . . . . . . . . . 47O . . . . . . . . . . . . . . . . . . 47P . . . . . . . . . . . . . . . . . . 47R . . . . . . . . . . . . . . . . . . 48S . . . . . . . . . . . . . . . . . . 48T . . . . . . . . . . . . . . . . . . 49U . . . . . . . . . . . . . . . . . . 49V . . . . . . . . . . . . . . . . . . 49W . . . . . . . . . . . . . . . . . 50

Appendix B. Support. . . . . . . . . 51

Notices . . . . . . . . . . . . . . 53Trademarks . . . . . . . . . . . . . . 55Terms and conditions for product documentation. . 56

© Copyright IBM Corp. 2016 iii

iv IBM BigFix: WebUI User's Guide

Chapter 1. Welcome

Welcome to IBM BigFix WebUI. The WebUI delivers a powerful set of functions forBigFix operators. It simplifies BigFix workflow, speeds access to data, andimproves flexibility, visibility, and performance.

No prior BigFix experience is needed to learn and use the WebUI. A browser, theWebUI URL, and a BigFix user name and password are all that is required.Supported browsers include Internet Explorer (10,11, Edge), and the latest versionsof Safari, Firefox, and Chrome.

Administrators and operators familiar with the BigFix console will find a usefulintroduction to the WebUI in this guide. For information about installing andadministering the WebUI, see the IBM BigFix WebUI Administration Guide.

To open the WebUI use the URL provided by your administrator and enter yourBigFix user name and password. Single Sign On users will bypass the BigFix loginscreen and authenticate through their service provider. Following a successful loginthe BigFix Overview displays.

© Copyright IBM Corp. 2016 1

2 IBM BigFix: WebUI User's Guide

Chapter 2. Meet the WebUI

Take a quick tour of the WebUI screens, controls, and workflow. A detaileddescription of each of the main WebUI screens, including the Deploy Sequence andits options, begins in Chapter 3, “Get Started with Devices,” on page 11. For anintroduction to BigFix terms and concepts, see the Appendix A, “Glossary,” onpage 43.

Overview Page

The WebUI Overview provides a summary of your environment. Its interactivecharts and rich set of links make it easy to move quickly to areas that requireimmediate attention. Refresh the screen to see the latest data. The Overview is theWebUI's default landing page. Display it from any WebUI screen by clicking thehome icon on the WebUI navigation bar, or on the BigFix logo.

The Executive Overview dashboard provides information of particular interest toIT Officers, Security Officers, and Analysts. To display it click the Overview buttonbeneath the navigation bar and select Executive Dashboard. Use the Overviewbutton to move between dashboards.


For more information about the Executive Dashboard and its tiles, see the WebUIAdministration Guide.

Operator permissions and site and role assignments govern which page and dataelements display on WebUI pages. For example, an operator who does not haveaccess to the Software Distribution component will not see the Add Softwarebutton on the Overview. For more information, see “Permissions and Their Effects”on page 9.

WebUI sessions close automatically after a period of inactivity. If your sessionexpires, you will be returned to the page that you were on the next time you login.

Note: When a tile on a dashboard takes over 10 seconds to load, a messagecontaining load time details displays. Click Close to clear the message and returnto the dashboard. Performance is not static, and various factors can influencedashboard response times. These include hardware changes, changes in thenumber of endpoints, and the amount of data you have access to. Share the loadtime data with your BigFix administrator if you wish.


http://www.ibm.com/support/knowledgecenter/SSTK87_9.5.0/com.ibm.bigfix.webui.doc/WebUI/Admin_Guide/c_editing_dashboards.html

http://www.ibm.com/support/knowledgecenter/SSTK87_9.5.0/com.ibm.bigfix.webui.doc/WebUI/Admin_Guide/c_editing_dashboards.html

Navigation Bar

Use the navigation bar to access the Overview and Device, Content, andDeployment screens.

Links throughout the WebUI provide shortcuts between views.

List Views

List views show your BigFix environment in directory form: a flexible, searchableindex of devices, deployments, and content. Click the title on a card to open thecorresponding document. (To preview a title too long for its card, hover over itwith the mouse.) To take an action, for example, to deploy a patch or target adevice, highlight its card and click the Deploy button. For more information, seeChapter 8, “Take Action: The Deploy Sequence,” on page 33.

Chapter 2. Meet the WebUI 5

Document Views

The WebUI’s document views present detailed information about a particulardevice, deployment, or piece of content. Use document navigation links to drilldown into the data on associated views. The diagram shows a patch document.

Key details are summarized in the right side panel; the Deploy button appears onall device and content documents.

Filters and Search Tools

Use the WebUI filters to reduce a long list to a short list of specific items. Forexample, filter the Software list by Operating System to see software for OS Xcomputers. Combine filters, for example, to find expired deployments issued by aspecific operator at particular time.


The list of active filter groups are displayed across the top of the list.

The filter panel appears in a closed state on some screens.


Close the filter panel using the icon in its upper left corner.

Text Search

Use a text search to find items based on words or characters they contain. Forexample, search the Device list for “2” to find every device with the character “2”in its name.

Use a multiple word search to find any items that contain those terms. Forexample, results for a search for “MS13-035 Vista” would include the patch“MS13-035 MSHTML Security Vulnerability Vista”. Searches are not case-sensitive.For example, a patch list search for the word “advisory” returns patches witheither “advisory” or “Advisory” in their name.


Wildcard searches, and searches for text within the body of a document, are notcurrently supported.

List Controls

Sort a list, adjust the number and appearance of list items, and move betweenpages with the list view controls.

Select All

The Select All check box selects or clears every item on a page.

Permissions and Their Effects

The elements that are shown on a WebUI screen reflect the permission levels of theuser, and the device, site, and group assignments set for them by the BigFixadministrator. For example, an operator responsible for patching Windowsmachines might not see Linux patches in their patch list or Linux machines in theirdevice list. An operator who deploys software but does no patching might not seethe Patch content or Custom content options in the Content submenu. For moreinformation about permissions and their influence on WebUI screens and dataelements, see the IBM BigFix WebUI Administrators Guide.


WebUI Workflow and Deploy Sequence

To deploy means to dispatch content to one or more endpoints for execution. Youcan start a deployment two ways: by selecting content and targeting one or moredevices, or by selecting devices and targeting the content that you want to deploy.Start a deployment from any device or content screen, or from the Overview page.

Here is an overview of the process. For details, see Chapter 8, “Take Action: TheDeploy Sequence,” on page 33.1. Select devices or content for deployment.2. Select content or device targets.3. Configure any deployment options.4. Review selections and deploy.


Chapter 3. Get Started with Devices

Use the Device screens to see a list of all devices (as determined by permissionlevels), find specific devices, access device documents, and select devices fordeployment.

The Device List

v Operator permission settings, device, and site assignments govern list contents.v See a list of devices eligible for software in your catalog using the Relevant

Devices with applicable software filter.v BigFix Lock – A machine with a BigFix lock on it does not run BigFix actions

until it is unlocked.v See a list of devices used by a specific person with the Most Recent User filter.

If a device has one user account, the device holder is listed. If a device hasmultiple user accounts the the last person to log on is listed.


Device Documents

Click a device name to see its properties, status, relevant content, deploymentstatus, and history. Drill further into device details by using the associated views.

The Device document views:v Properties – Detailed description of the device.v Custom – Custom content relevant to this device.v Patches – Patches relevant to this device.v Software – Software relevant to this device.v Deployments – Deployment history for this device.

An operator’s permission settings govern which views display. For example, anoperator without access to custom content will not see the Custom view. Operatorswho do not have access to the Query application will not see the Query button.v Critical Vulnerabilities – High severity patches available for this device.v Last Seen – The amount of elapsed time (minutes, hours, days) since a device

last reported to BigFix.v Add/Remove Properties – Display the list of available properties and select the

ones that you want to appear in the device properties view.

v Add Property Group – Customize the Device Properties view by adding orremoving sets of property data from the page.


v Filter Deployment by Status – On the Deployments view, filter the list usingStatus.

Chapter 3. Get Started with Devices 13

Chapter 4. Get Started with Patches

Use the Patch screens to list patches, find specific patches, and view detailed patchinformation including known issues, vulnerable devices, and deployments.

The Patch List

v Operator permission settings, device, and site assignments govern list contents.v See patches for the most critical threats or a specific threat level using the

Severity filters. Patch Severity is assigned by the patch vendor (for example,Microsoft), not IBM BigFix.– Critical– Important– Moderate– Low– Unknown - patch has no vendor-assigned rating.

v See patches required by many devices by entering a value in the VulnerableDevices field.

v See the latest patches using the Release Date field. Specify a date range to seepatches that were issued during a specific time period.

v See patches associated with a specific task using the Category filters:– Security – Apply a software change to address a vulnerability.– Service Pack – Apply patches to installed software. A collection of updates,

fixes, or enhancements delivered in a single installable package. Typicallyused to update existing files, but can also be used to fix bugs, close securityholes, or add new features.


– Audit – Type of BigFix patch that is used to detect conditions that cannot beremediated and require the attention of an administrator.

– Enhancement – Apply a change that provides new features.– Bug Fix – Apply a change that fixes one or more bugs.– Configuration – Apply a change that addresses a configuration issue.

v Show Hidden Patches – Control the display of audit, corrupt, and supersededpatches in the patch list.

v Supported Patch Sites - Only patches from these sites appear in the WebUI;future releases will include more patch sites.– Windows– Red Hat Linux– Mac OS X– CentOS– Windows Applications (Adobe Acrobat, Adobe Flash Player, Adobe Reader,

Adobe Shockwave, Google Chrome, ImgBurn, Mozilla Firefox, Notepad++,Nullsoft, Oracle, Real Networks, Skype, Winamp, Winzip)

Patch Documents

Click a patch name to see its description, vulnerable devices, and deploymenthistory. Drill further into patch details using the links to associated views. Payparticular attention to the Notes and Important Notes in a content document: theycontain valuable information, including known issues associated with the content.

The Patch Document views:v Overview – Detailed description of the patch.v Vulnerable Devices – Machines eligible for this patch.v Deployments – Patch deployment history.


The material in the Available Actions section is pulled directly from the BigFixdatabase, so options and formatting can vary. A link to the vendor’s release notesis often included. For example, “Click here to see the release notes for WindowsXP SP3.”

Chapter 4. Get Started with Patches 17

Chapter 5. Get Started with Software

Use the Software-related screens to list software packages, find specific software,and view detailed package information. A BigFix software package is the collectionof Fixlets used to install software on a device. The package includes the installationfiles, the Fixlets that install them, and information about the package itself. Use thesoftware screens to add, edit, and remove packages from your organization’ssoftware catalog.

The Software Package List

v Items shown reflect the operator’s device and site assignments, and whether aparticular package was shared or marked private by the owner.

v Add Software to your catalog with the Add Software link. The link does notdisplay if the operator does not have permission to add software.

Software Documents

Click a software package name to see its description, applicable devices, anddeployment history. Drill further into package details using the links provided inthe associated views. The Software Document views:v Overview – Detailed description of software package.v Applicable Devices – Machines eligible for this software.v Deployments – Software deployment history.v Software operations: Add, edit, delete.


v Edit or remove a software package from your catalog using the Edit Softwarelink.

v Quickly deploy this software package using Deploy this action.

Software Catalog Operations

This section shows how to add software to your catalog, edit software packages,and delete packages from the catalog. Note that the permissions used for addingsoftware to the catalog and the permissions used for editing and deleting softwareare calculated differently.

A single BigFix console setting determines whether or not an operator haspermission to add software. Permission to edit and remove software from thecatalog is also affected by who owns the software package, whether it was createdusing the BigFix console or the WebUI, and whether a package created in theWebUI was later modified using the console. If you run into permission issuesattempting to edit a software package, talk with your BigFix administrator.

Add a Software Package

Use this procedure to add a software package to BigFix.1. Click Add Software, on either the Software list or the WebUI Overview, to

open the Upload Software Package dialog.


2. Click Choose File to browse to a local file, or enter a URL to download apackage.

3. Click Upload.4. Complete the catalog record for the software. The appearance and behavior of

this screen changes if the uploaded file is a recognized file type or not.

These fields are required:v Software Namev Version numberv Publisher

Chapter 5. Get Started with Software 21

v Site – BigFix site where the software is stored.v Command Line. For known file types this field is populated with a string

appropriate for the file type. However, if the file type is unknown, acommand line must be entered.

5. Optionally:v Describe the software and any instructions that will aid the operators

responsible for deploying it.v For Windows systems, select the Run Command As setting. Commands that

are executed by the BigFix client default to System User. (On OS X, UNIX,and Linux computers software is installed as root.) However, in some casesyou might want to install using the credentials and local context of the userwho is logged on. Check with your BigFix administrator for furtherguidance.

v For Windows systems, add installation parameters. Select from the list ofavailable parameters, or enter your own. Verify that the command line iscomplete and correct using the Preview field. Note that the InstallationParameters field is not shown if you are editing the command line directly.

6. Click Save to add the software.


The following file extensions have predefined installation commands. Thepredefined commands can be edited if needed:v .DMGv .EXEv .MSIv .MSPv .MSUv .PKGv .RPM

Edit a Software Package1. Open the Software Package document that you want to update.2. Click the Edit Software link in the right side panel.3. Make any wanted changes to the package data, or deployment options.4. Click Change, at the upper left of the dialog to update the executable file.5. Click Save.

Delete a Software Package1. Open the Software Package document you want to delete.2. Click the Edit Software link, located in the right side panel.3. Click Delete in the lower left corner of the dialog, and confirm at the prompt.

Chapter 5. Get Started with Software 23

Chapter 6. Get Started with Custom Content

Use the Custom Content screens to view custom content, find specific content, andview related information, including applicable devices and deployments.

The Custom Content List

The category filters listed in the filter panel reflect the categories associated withthe content displayed in the list.

The category filters listed in the filter panel reflect the categories associated withthe content displayed in the list.v Operator permission settings, device, and site assignments govern list contents.v Category filters speed access to content associated with specific administrative

tasks. Categories can include:– Configuration– Installation– Security updates– Software distribution– Uninstallation

v Show More - Some filter groups contain more options than fit on the screen.Click Show More to select from a list of all available filters.

v Site filters - Use the Site filters to display content stored in a particular site.


Custom Content DocumentsClick a custom content name to see its description, list of applicable devices, anddeployment history. Use the links to see details that are provided in the associatedviews.

The Custom Content views:v Overview – detailed description of custom content.v Applicable Devices – machines eligible for this content.v Deployments – list of deployments for this piece of content.

If a piece of custom content involves multiple actions, as for a baseline, forexample, the names of its components are listed in the Overview. For informationabout the differences between Single tasks and Baselines, see the Appendix A,“Glossary,” on page 43.


Chapter 7. BigFix Query

Use the WebUI’s BigFix Query to retrieve data from endpoints through a dedicatedquery channel, where memory on each relay minimizes impact to normal BigFixprocessing.v Query individual computers and manual computer groups.v Test Relevance expressions as you develop content.v Export query results to a comma-separated value (.csv) file.v Create a library of custom queries; keep collections private or share them with

others.

Start with 34 pre-defined queries focused on applications, files, devices, network,processes, registry, and policy. Customize them, and build your own. The categorycards display alphabetically left-to-right, row by row. Query titles are listedalphabetically in each category.v Select targets from a searchable list of endpoints.v Filter by property to quickly locate devices.v Open a device document from query results to investigate or apply a fix.

An introduction to the editor and instructions for using the pre-defined queriesfollow. For information on building your own queries, see “Build a Query” onpage 30.


Run a Pre-Defined Query1. Click a query to display it in the editor. Use the Category control to change

which categories display.

v To find a specific query type its name in the Search field. The searchfunction cannot be used to search for strings inside a query.

v Query titles in hidden categories do not appear in search results. Redisplay acategory to include its queries in a search.

2. Click the Devices Targeted link to open the target list. Click the Devices andGroups radio buttons to control which list of targets displays.

3. Click the names of the devices or manual computer groups where you want thequery to run. The items that are listed reflect the permissions of the user.Master Operators see all devices and groups. Non-Master Operators might seea subset of the complete list. Use the sort, search, and filtering tools to quicklylocate targets. For an introduction to these tools, see Chapter 2, “Meet theWebUI,” on page 3.v To find a specific device or group, type its name into the Search field.v Sort a list of devices by device name or time last seen; sort a list of groups

by group name, or member count.v Use filters to locate devices with specific properties. Click the funnel icon to

open and close the filter panel.When device or group selection is complete click OK to return to the editor.The Devices Targeted button displays your total.


Note: When pairing queries and targets, keep in mind that queries that areconcise, and queries that are limited in scope, execute the most efficiently.Broad queries return larger data sets and use more resources.

4. Click Execute, or the keyboard shortcut Control + Enter, to run the query. Youcan cancel a query while the results load.

5. Review your results. Devices report in real time, and new arrivals areappended to the list as clients report in.

v Click the Expand View toggle to switch to full screen mode and see moreresults. Click it again, or press the Escape key to exit full screen mode.

v The icons in the lower right corner of the list show row totals, and numberof devices reported so far.

Click a device name to open its document.

Click Query to return to the Query editor with the device targeted for a query.Click Reload Devices to return to the full list of devices in the editor.

Chapter 7. BigFix Query 29

Click the Download button to open the results in an Excel spreadsheet, or savethe file in comma-separated values format (.csv).

Consider including the date and some descriptive information in the file nameto help you identify it later.

Build a Query

To create a new query, type it directly into the editor. Or save an existing queryunder a different name to create a copy you can customize. It is helpful to knowsome Relevance when building queries, but you don’t need to be fluent. To learnmore about Relevance, go to https://developer.bigfix.com/.

The principles that apply when you work with queries in the BigFix console applyin the Query editor as well. Concise queries that are limited in scope execute mostefficiently. Broad, general queries that return large data sets consume moreresources. Problems associated with poorly performing Relevance in the consolecan also occur in the Query editor.v Shared and Private Queries

To reserve a query that you have written for your own use, save it in the PrivateQueries category. Only you can see and use the queries stored there. To share aquery that you have written with other users, save it in any other category.Shared queries can be seen, modified, and deleted by others. To see the name ofthe last person to edit a query, hover the mouse over its icon.

v Pre-Defined and Operator-Defined QueriesQueries you and other users create are marked with the operator icon.Pre-defined queries are marked with the lock icon. Pre-defined queries cannot bedeleted or modified.


https://developer.bigfix.com/

Save a Query

To save a query, click the Save button.

To make a customizable copy of an existing query, save it under a different name.1. Click Save.2. Enter a descriptive title for the query.3. Select a category for the query.

A query’s title and its category constitute its unique ID. In other words, it ispossible for two queries to have the same name, but not in the same category.

Delete a Query

To delete a query, click its trash bin icon.

Chapter 7. BigFix Query 31

Chapter 8. Take Action: The Deploy Sequence

To deploy means to dispatch content to one or more endpoints for execution, forexample, to update a patch, install software, or restart a machine. Collectively, thescreens that are used to create deployments are collectively called the DeploySequence. The workflow is straightforward; you might find it similar to making apurchase online.

Deploy Sequence Summary

In summary:1. Select devices or content for deployment.2. Select content or device targets.3. Configure deployment options.4. Review and deploy.

Prompts, status information, and selection tallies are shown in the side panel. Atthe top of the page the status bar reflects your location in the deploy sequence.Embedded help (question mark icon) is available for some options.

v Not all content can be deployed. If non-deployable content (such as an auditaction) is selected, you will be prompted to remove it from the deployment.

v No Default Action – If content without a default action is selected, you will beprompted to choose one.

v Action Parameters Required – If content that requires a parameter is selected,you will be prompted to supply one.

Deploy Procedure1. Select devices or content for deployment; click Deploy.v Use the List views, filter, and search tools to find the records you want.v Review the content documents to ensure that you understand their effects.

2. Select content or device targets, respectively; click Next.v Use the lists, filters, and search tools, and review device and content

documents as needed.v Alternatively, you can deploy an action directly from the Software Document

as described in “Software Documents” on page 19.


3. If the “Require decision” or "Non-deployable" prompts display, one or moreactions require input.

a. Click the Selected actions link (Tasks, Patches, or Software) to open theDecision dialog.

Note: Multiple Action Groups can be reordered by clicking and draggingindividual actions. This is a feature of the BigFix® WebUI that cannot beperformed in the traditional BigFix console.1) Specify any missing default actions.v Fixlets with no default and multiple actions:

a) Select an action from the drop-down list. For example, a singlesoftware package might be used to both install and uninstall anapplication.

v Fixlets with no default and a single action:a) Review the content document. The Fixlet® author is saying,

“Proceed with caution.” Pay close attention to any Notes®,Warnings, or Known Issues in the document and make aninformed decision.

b) To remove the action, click the x next to its name. To deploy theaction, select “Click here to initiate the deployment process” fromthe drop-down list.

2) Enter action parameters as required.a) Select the action that is presented in the drop-down list to display

the Enter Parameters link.


b) Click Enter Parameters and type in the required information, such asa path name or service name.

3) Remove any non-deployable actions, such as audits or supersededpatches.

b. Click Apply to return to the deploy sequence.c. Click Next to open the Configuration page.

4. Select configuration options for the deployment; click Next. See ConfigurationOptions for descriptions of each option.

5. Review your selections. Use the Edit icon to make any adjustments.6. Click Deploy.7. Monitor deployment results with the Deployment views.

Configuration OptionsSet Start and End Time

Schedule a deployment to start at a specific time, for example, to reducenetwork load and device-holder inconvenience.

Select Client time or UTC timeUse these options to further refine when a deployment runs. Client Time isthe local time on a BigFix client's device. Coordinated Universal Time(UTC) is the primary standard for regulating clocks and time worldwide.

Set as Open-ended deploymentAn open-ended deployment has no end date, running continuously andchecking whether endpoints comply. For more information, see theAppendix A, “Glossary,” on page 43.

Download required files nowPre -cache deployment-related files, transferring them from a vendor’sserver to a BigFix server for temporary storage before deployment. Savetime when you are working with large files or a tight maintenance windowby completing this part of the job first.

Send a NotificationTrigger an email alert when a deployment fails or completes.v Send on Failure – enter a threshold value (1 - 250,000) to receive an

email if the deployment fails on the specified number of devices.

Chapter 8. Take Action: The Deploy Sequence 35

v Send on Completion – check the box to receive an email when thedeployment completes on all targets. Note: this notification option is notavailable when targeting computer groups.

Enter one or more recipients in the To: field, separating multiple addresseswith a comma ([email protected], [email protected], [email protected]). Note:To use this option the Notification Service must be running in the BigFixconsole and permission to use Custom Content must be enabled

Send this as an offerEnable the device holder to accept or decline an action and exercise somecontrol over when it runs. For example, to decide whether to install a pieceof software, or to install it over night rather than during the day. Offers areonly visible to those users selected on the Users tab in the BigFix console,and only on those machines where the client’s Offer interface is enabled.

Force restartForce a restart on an endpoint following a deployment and offer the deviceholder a chance to restart the device themselves at convenient time. Set therestart to occur:v Immediately (following completion of the deployment)v 1 day laterv 7 days laterv 15 days later

Send the device holder a message about the pending restart. Use thedefault message that is provided, or enter your own. For example, “Yoursystem administrator is requesting that you restart your computer. Pleasesave any unsaved work and restart. Your device will restart automaticallyin 7 days."

Run all member actions of action group regardless of errorsActions in a multiple action group (MAG) execute sequentially. Normally,MAG deployments stop on the first action that fails. When this box ischecked the MAG ignores the failure and proceeds to the next action. Usethis option when the actions in a MAG do not depend on the actions thatprecede them.

Stagger deployment times to reduce network loadCheck the box and enter an interval in hours and minutes.1. When configuration is complete, click Next.2. Review selections and click Deploy.3. Monitor deployment results with the Deployment views.


Chapter 9. Get Started with Deployments

Use the Deployment views to monitor and verify completion of BigFixdeployments.

The Deployment List

The colored bars on the Deployment list summarize the status of each deployment.Use the filters to find specific deployments by type.

WebUI deployment screens list every deployment. In this they are different fromthe other WebUI screens, where permission settings can limit the number of itemsdisplayed. While operators can see all deployments, permissions continue togovern the actions they can take. For example, an operator who cannot access theWebUI patch screens would see all patch deployments, but would not be able tostop one that was running.

The WebUI displays all actions initiated from The WebUI, the BigFix console, andexternal sites, including BES Support. For this reason, the Deployment list’sApplication Type filter is labeled, “Patch Software Other,” rather than “PatchSoftware Custom.” In this situation Custom includes any external site, not justCustom sites.


Deployment Documents

Click a deployment name to see its deployment status, behavior (set atconfiguration), and targeting information. Drill further into deployment detailsusing the links to associated views.

The Deployment Document views:v Overview – detailed description of this deployment: status, behavior, targeting,

and more.v Device Results – target status – the state of the deployment on each endpoint.v Component Results – for content with multiple actions: the deployment status of

each component on targeted devices, expressed as a percentage of success.

Monitoring Deployments: State, Status, and Result

Interpret deployment results correctly by understanding the difference betweenDevice Results, Deployment Status, and Deployment State.

Device Results

Device Results describe the state of a deployment on a particular endpoint. Thereare many different BigFix Device Result codes. The most common ones seen in theWebUI include:v Fixed, or Completed – The deployment succeeded (on this device).v Failed – The deployment failed (on this device).v Pending Restart – Eventual success is implied.v Not Relevant – The action is not relevant to this device.v Runningv Evaluatingv Pending Download

Software deployments might have an associated log file. This log can be viewed inthe Device Results screen. The presence of a viewable log file is denoted by anicon. Note that log files are only available for software deployments.


Click the log icon to display the associated log data. The entire log can bedownloaded by clicking the log file name.

Note: Log files can only be viewed for software deployments. In addition, to viewlog files in the BigFix WebUI, the current user must be subscribed to the SoftwareDistribution Site in the traditional BigFix Console, and Analysis 11 of the SoftwareDistribution Site must be activated.

Deployment Status

Deployment Status is formulated using Device Results.v For deployments with single actions, Deployment Status is the cumulative

deployment status of each targeted device, expressed as a percentage of success.v For deployments with multiple actions, Deployment Status is the cumulative

deployment status of each component on each targeted device, expressed as apercentage of success.

Chapter 9. Get Started with Deployments 39

v Green – Fixed (patches), or Completed (software, custom content).v Dark gray – Other. The category can include Pending Restart, Running,

Evaluating,v Pending Download, and more.v Light gray – Not yet reported, or not relevant.v Red – Failed.v No Status Bar – No relevant devices.

Deployment State

Deployment State describes the eligibility of a deployment to run on endpoints. Itis not involved in calculating Deployment Status. Deployment State has threevalues:v Open – The deployment is eligible to be run by endpoints.v Expired – The deployment is no longer eligible to run because the end time has

passed for all possible endpoints in all time zones.v Stopped – The deployment is no longer eligible to run because an operator or

administrator stopped it.

In summary: Device Result is the result of a particular deployment on a specificdevice. Deployment State describes the eligibility of a deployment to run.Deployment Status provides the cumulative results of a deployment on targetedendpoints.

Evaluating Deployments With Multiple Actions

To obtain an accurate picture of the state of a deployment with multiple actions,such as those involving a group or baseline, check the status of its individualcomponents. In other words, if a deployment group’s status is less than 100%,check to see which of its components has not yet completed.


1. Open the Deployments list.2. Use the Deployment Type filter to display a list of Group deployments.3. Select the Deployment that you want and open its document.4. Click Component Results.

Stop A Deployment

Not every deployment completes successfully the first time. Use the StopDeployment button on any Deployment list or document view to terminate adeployment, if needed. Reasons to stop a deployment include:v Starting to see failures on many devices.v Starting to get blue screens on the targeted devices.v You have updated a baseline (or Fixlet) and need to stop the old one.

Use the Deployment views and the custom tools provided by your BigFixadministrator to diagnose and fix deployment problems. Work with them to learnmore about why deployments fail and effective methods for resolving issues whenthey arise. Reasons a deployment can fail include:v A computer is offline.v A computer is being rebuilt or reimaged.v A computer has insufficient disk space.v A computer is not communicating with the BigFix update server.v The BigFix agent is not running on the computer.v The computer is missing some dependent software.

Chapter 9. Get Started with Deployments 41

Appendix A. Glossary

This glossary provides terms and definitions for the [product name] software andproducts.

The following cross-references are used in this glossary:v See refers you from a nonpreferred term to the preferred term or from an

abbreviation to the spelled-out form.v See also refers you to a related or contrasting term.

For other terms and definitions, see the IBM Terminology website (opens in newwindow).

“A” “B” “C” on page 44 “D” on page 45 “E” on page 46 “F” on page 46 “G” onpage 46 “L” on page 46 “M” on page 46 “N” on page 47 “O” on page 47 “P” onpage 47 “R” on page 48 “S” on page 48 “T” on page 49 “U” on page 49 “V” onpage 49 “W” on page 50

Aaction

1. See Fixlet.2. A set of Action Script commands that perform an operation or

administrative task, such as installing a patch or rebooting a device.

Action ScriptLanguage used to perform an action on an endpoint.

agent See BigFix agent.

ambiguous softwareSoftware that has an executable that looks like another executable, or thatexists in more than one place in a catalog (Microsoft Word as a standaloneproduct or bundled with Microsoft Office).

audit patchA patch used to detect conditions that cannot be remediated and requirethe attention of an administrator. Audit patches contain no actions andcannot be deployed.

automatic computer groupA computer group for which membership is determined at run time bycomparing the properties of a given device against the criteria set forgroup membership. The set of devices in an automatic group is dynamic,meaning it can and does change. See also computer group.

Bbaseline

A collection of actions that are deployed together. A baseline is typicallyused to simplify a deployment or to control the order in which a set ofactions are applied. See also deployment group.

© Copyright IBM Corporation 2016 © IBM 2016 43

http://www.ibm.com/software/globalization/terminology/

BigFix agentThe BigFix code on an endpoint that enables management and monitoringby BigFix.

BigFix clientSee BigFix agent.

BigFix consoleThe primary BigFix administrative interface. The console provides a full setof capabilities to BigFix administrators.

Cclient A software program or computer that requests services from a server. See

also server.

client timeThe local time on a BigFix client's device.

Common Vulnerabilities and Exposures Identification Number (CVE ID)A number that identifies a specific entry in the National VulnerabilityDatabase. A vendor’s patch document often includes the CVE ID, when itis available. See also National Vulnerability Database.

Common Vulnerabilities and Exposures system (CVE)A reference of publicly known network vulnerabilities which is part of theNational Vulnerabilities Database (NVD), maintained by the US NationalInstitute of Standards and Technology (NIST).

componentAn individual action within a deployment that has more than one action.See also deployment group.

computer groupA group of related computers. An administrator can create computergroups to organize systems into meaningful categories, and to facilitatedeployment of content to multiple computers. See also automatic computergroup, manual computer group.

consoleSee BigFix console.

contentDigitally-signed files containing data, rules, queries, criteria, and otherinstructions, packaged for deployment across a network. BigFix agents usethe detection criteria (Relevance statements) and action instructions (ActionScript statements) in content to detect vulnerabilities and enforce networkpolicies.

content relevanceA determination of whether a patch or piece of software is eligible fordeployment to one or more devices. See also device relevance.

Coordinated Universal Time (UTC)The international standard of time that is kept by atomic clocks around theworld.

corrupt patchA patch that flags an operator when corrections made by an earlier patchhave been changed or compromised. This can occur when an earlier


service pack or application overwrites later files, resulting in patched filesthat are no longer current. The corrupt patch flags the situation and can beused to re-apply the later patch.

custom contentBigFix code created by a customer for use on their own network, forexample, a custom patch or baseline.

CVE See Common Vulnerabilities and Exposures system.

CVE IDSee Common Vulnerabilities and Exposures Identification Number.

Ddata stream

A string of information that serves as a source of package data.

default actionThe action designated to execute when a Fixlet is deployed. When nodefault action is defined, the operator is prompted to choose betweenseveral actions or to make an informed decision about a single action.

definitive packageA string of data that serves as the primary method for identifying thepresence of software on a computer.

deployTo dispatch content to one or more endpoints for execution to accomplishan operation or task, for example, to install software or update a patch.

deploymentInformation about content dispatched to one or more endpoints, a specificinstance of dispatched content.

deployment groupThe collection of actions created when an operator selects more than oneaction for a deployment, or a baseline is deployed. See also baseline,component, deployment window, multiple action group.

deployment stateThe eligibility of a deployment to run on endpoints; includes anyparameters set by the operator, such as “Start at 1AM, end at 3AM.”

deployment statusCumulative results of all targeted devices, expressed as a percentage ofdeployment success.

deployment typeAn indication of whether a deployment involved one action or multipleactions.

deployment windowThe period during which a deployment’s actions are eligible for execution.For example, if a Fixlet has a deployment window of 3 days and aneligible device that has been offline reports in to BigFix within the 3-daywindow, it gets the Fixlet. If the device comes back online after the 3-daywindow expires, it does not get the Fixlet. See also deployment group.

device An endpoint, for example, a laptop, desktop, server, or virtual machinemanaged by BigFix; an endpoint running the BigFix Agent.

Appendix A. Glossary 45

device holderThe person using a BigFix-managed computer.

device propertyInformation about a device collected by BigFix, including details about itshardware, operating system, network status, settings, and BigFix client.Custom properties can also be assigned to a device.

device relevanceA determination of whether a piece of BigFix content applies to applies toa device, for example, where a patch should be applied, software installed,or a baseline run. See also content relevance.

device resultThe state of a deployment, including the end result, on a particularendpoint.

Distributed Server Architecture (DSA)An architecture that links multiple servers to provide full redundancy incase of failure.

DSA See Distributed Server Architecture.

dynamically targetedPertaining to using a computer group to target a deployment.

Eendpoint

A networked device running the BigFix agent.

Ffilter To reduce a list of items to those that share specific attributes.

Fixlet A piece of BigFix content containing Relevance and Action Scriptstatements bundled together to perform an operation or task. Fixlets arethe basic building blocks of BigFix content. A Fixlet provides instructionsto the BigFix agent to perform a network management or reporting action.

Ggroup deployment

A type of deployment where multiple actions were deployed to one ormore devices.

Llocked

An endpoint state that prevents the majority of BigFix actions fromrunning until the device is unlocked.

MMAG See multiple action group.

management rightsThe limitation of console operators to a specified group of computers. Onlya site administrator or a master operator can assign management rights.


manual computer groupA computer group for which membership is determined through selectionby an operator. The set of devices in a manual group is static, meaningthey do not change. See also computer group.

master operatorA console operator with administrative rights. A master operator can doalmost everything a site administrator can do, with the exception ofcreating new operators.

mastheadA collection of files that contain the parameters of the IBM BigFix process,including URLs to Fixlet content. The IBM BigFix agent brings content intothe enterprise based on subscribed mastheads.

mirror serverA BigFix server required if the enterprise does not allow direct web accessbut instead uses a proxy server that requires password-level authentication.

multiple action group (MAG)A BigFix object that is created when multiple actions are deployed together,as in a baseline. A MAG contains multiple Fixlets or Tasks. See alsodeployment group.

NNational Vulnerability Database (NVD)

A catalog of publicly-known information security vulnerabilities andexposures maintained by the National Institute of Standards andTechnology (NIST). See also Common Vulnerabilities and ExposuresIdentification Number.

NVD See National Vulnerability Database.

Ooffer A deployment option that allows a device holder to accept or decline a

BigFix action and to exercise some control over when it runs. For example,whether or not to install a software application, and whether to run theinstallation at night or during the day.

open-ended deploymentA deployment with no end or expiration date; one that runs continuously,checking whether or not the computers on a network comply.

operatorA person who uses the BigFix WebUI, or portions of the BigFix console.

Ppatch A piece of code added to vendor software in order to fix a problem, as an

immediate solution that is provided to users between two releases.

patch categoryA description of a patch’s type and general area of operation, for example,a bug fix or a service pack.

patch severityThe level of risk imposed by a network threat or vulnerability and, byextension, the importance of applying its patch.


Rrelay A client that is running special server software. Relays spare the server and

the network by minimizing direct server-client downloads and bycompressing upstream data.

RelevanceBigFix query language used to determine the applicability of a piece ofcontent to a given endpoint. Relevance asks yes or no questions andevaluates the results. The result of a Relevance query determines whetheran action can or should be applied. Relevance is paired with Action Scriptin Fixlets.

SSCAP See Security Content Automation Protocol.

SCAP checkA specific configuration check within a Security Content AutomationProtocol (SCAP) checklist. Checks are written in XCCDF and are requiredto include SCAP enumerations and mappings per the SCAP template.

SCAP checklistA configuration checklist that is written in a machine readable language(XCCDF). Security Content Automation Protocol (SCAP) checklists havebeen submitted to and accepted by the NIST National Checklist Program.They also conform to a SCAP template to ensure compatibility with SCAPproducts and services.

SCAP contentA repository that consists of security checklist data represented inautomated XML formats, vulnerability and product name relatedenumerations, and mappings between the enumerations.

SCAP enumerationA list of all known security related software flaws (CVEs), known softwareconfiguration issues (CCEs), and standard vendor and product names(CPEs).

SCAP mappingThe interrelationship of enumerations that provides standards-basedimpact measurements for software flaws and configuration issues.

Security Content Automation Protocol (SCAP)A set of standards that is used to automate, measure, and managevulnerability and compliance by the National Institute of Standards andTechnology (NIST).

server A software program or a computer that provides services to other softwareprograms or other computers. See also client.

signing passwordA password that is used by a console operator to sign an action fordeployment.

single deploymentA type of deployment where a single action was deployed to one or moredevices.

site A collection of BigFix content. A site organizes similar content together.


site administratorThe person in charge of installing IBM Endpoint Manager, authorizing andcreating new console operators.

software packageA collection of Fixlets that install a software product on a device. Softwarepackages are uploaded to BigFix by an operator for distribution. A BigFixsoftware package includes the installation files, Fixlets to install the files,and information about the package (metadata).

SQL ServerA full-scale database engine from Microsoft that can be acquired andinstalled into the IBM Endpoint Manager system to satisfy more than thebasic reporting and data storage needs.

standard deploymentA deployment of the IBM Endpoint Manager that applies to workgroupsand to enterprises with a single administrative domain. It is intended for asetting in which all Client computers have direct access to a single internalserver.

statistically targetedPertaining to the method used to target a deployment to a device or pieceof content. Statically targeted devices are selected manually by an operator.

superseded patchA type of patch that notifies an operator when an earlier version of a patchhas been replaced by a later version. This occurs when a later patchupdates the same files as an earlier one. Superseded patches flagvulnerabilities that can be remediated by a later patch. A superseded patchcannot be deployed.

system power stateA definition of the overall power consumption of a system. IBM EndpointManager Power Management tracks four main power states Active, Idle,Standby or Hibernation, and Power Off.

Ttarget To match content with devices in a deployment, either by selecting the

content for deployment, or selecting the devices to receive content.

targetingThe method used to specify the endpoints in a deployment.

task A type of Fixlet designed for re-use, for example, to perform an ongoingmaintenance task.

UUTC See Coordinated Universal Time.

Vvirtual private network (VPN)

An extension of a company intranet over the existing framework of eithera public or private network. A VPN ensures that the data that is sentbetween the two endpoints of its connection remains secure.

VPN See virtual private network.


vulnerabilityA security exposure in an operating system, system software, orapplication software component.

WWake-from-Standby

A mode that allows an application to turn a computer on from standbymode during predefined times, without the need for Wake on LAN.

Wake on LANA technology that enables a user to remotely turn on systems for off-hoursmaintenance. A result of the Intel-IBM Advanced Manageability Allianceand part of the Wired for Management Baseline Specification, users of thistechnology can remotely turn on a server and control it across the network,thus saving time on automated software installations, upgrades, diskbackups, and virus scans.

WAN See wide area network.

wide area network (WAN)A network that provides communication services among devices in ageographic area larger than that served by a local area network (LAN) or ametropolitan area network (MAN).


Appendix B. Support

For more information about this product, see the following resources:v IBM Knowledge Centerv IBM BigFix Support Centerv IBM BigFix Support Portalv IBM BigFix Knowledge Basev IBM BigFix Customer Support Technical Information Newsletterv IBM BigFix Wikiv IBM BigFix Forum


http://www-01.ibm.com/support/knowledgecenter/SSQL82

http://www-01.ibm.com/support/docview.wss?uid=swg21624185

http://www.ibm.com/support/entry/portal/overview/software/security_systems/ibm_bigfix_family

https://www-947.ibm.com/support/entry/myportal/all_documentation_links/security_systems/ibm_bigfix_family?productContext=-2009328398

http://www-01.ibm.com/support/docview.wss?uid=swg27027063

https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Home

https://forum.bigfix.com

Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785United States of America

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.


Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data discussed herein is presented as derived under specificoperating conditions. Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,


modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. _enter the year or years_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM® Corp. and Quantum in the U.S. and other countries.

Notices 55

http://www.ibm.com/legal/us/en/copytrade.shtml

http://www.ibm.com/legal/us/en/copytrade.shtml

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.


Notices 57

IBM®

Printed in USA