IBM Endpoint Manager for Software Use Analysis Version Beta Features Guide

Transcription

1 IBM Endpoint Manager for Software Use Analysis Version Beta Features Guide

2 Beta Features Guide This edition applies to IBM BigFix Inventory 9.2 (product number 5725-F57) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2002, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Chapter 1. Introduction Chapter 2. Usage of other license metrics Viewing the usage of other license metrics Disabling the collection of other license metrics... 6 Chapter 3. Extended discovery of Oracle Database Supported operating systems Coverage of licensable options Discovering Oracle Database software Chapter 4. Identifying computers on public clouds Chapter 5. Creating audit snapshots of PVU and RVU MAPC usage Content of audit snapshots Notices Trademarks Terms and conditions for product documentation.. 19 Copyright IBM Corp. 2002, 2015 iii

4 iv IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

5 Chapter 1. Introduction Functionalities that are delivered in the third drop of BigFix Inventory and open beta include discovering Oracle databases, monitoring usage of license metrics other than PVU and RVU MAPC, identification of computers running on public clouds, and adding comments to the audit snapshot. Providing your feedback Your feedback is crucial for the development team and your comments and suggestions are very much appreciated. Test the new features and let us know what you think and what can be improved. Use the following communication channels to provide your feedback: v Write a post on the beta forum v us at: [email protected] Copyright IBM Corp. 2002,

6 2 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

7 Chapter 2. Usage of other license metrics BigFix Inventory collects data about the usage of license metrics other than PVU and RVU MAPC for products that deliver software license metric tags. The data is presented on the License Use Data report and includes: v The type and subtype of license metrics that a product uses v The first and last time when each metric was reported v The maximum usage of each license metric over the last 30 days. If a particular product is unused, no license use data is available, or the data is older than 30 days, the value in the Maximal Trend Value column is 0. v Trend value of the maximum usage over the last 30 days Note: When the graph in the Maximal Trend Value History column shows 0 for a specific period, it either means that a) there is no data, or b) there was no license consumption during this period. To recognize which is the case, click Export History to save the report to a file. Then, open the file, and check if the entries that show 0 in the UI also show 0 in the file. If they do, it means that the license consumption during this period equals to 0. If there are no such entries, the data from this period was not reported. The data that is displayed on the report is not aggregated. It means that if a product can use five license metrics, five rows are shown on the report. What is more, all metrics that are available for a product are displayed, not only the metrics that are defined by your license agreement. If you want to aggregate the data according to your license agreement, export the history of license metric usage and aggregate it outside of BigFix Inventory. Apply all necessary filters on the License Use Data report, and click Export History. The csvhistory.zip file is downloaded to your computer. It contains the lu_export_history.csv file that provides initially processed data about the average and maximum usage of each license metric for each product. Important: If you click CSV or PDF, only data that is visible on the user interface is exported. Example IBM Product is an application that is licensed based on the number of users who simultaneously log in to that application per hour. Figure 1 on page 4 is a visualization of the license metric usage data that is retrieved from the software license metric tag for IBM Product. Copyright IBM Corp. 2002,

8 Figure 1. License metric usage data retrieved for IBM Product The data undergoes initial processing during which the average daily usage of the license metric is calculated. Information about the maximum usage, including its value and time, is preserved. Figure 2 on page 5 is a visualization of the license metric usage data for IBM Product after initial processing. It shows that on average, four users were simultaneously logged in to the application. The maximum usage occurred between 2:00 p.m. and 3 p.m. when 10 users were simultaneously logged in to IBM Product. 4 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

9 Figure 2. License metric usage data for IBM Product after initial processing The lu_export_history.csv file contains license metric usage data after initial processing. It does not contain all data that was collected from the endpoints in your infrastructure. Table 1 shows a fragment of the lu_export_history.csv file that corresponds to the data that is presented in Figure 2. The first row corresponds to the average license metric usage before the peak. The second row corresponds to the peak usage. The third row corresponds to the average usage after the peak value. Table 1. A fragment of the lu_export_history.csv file Computer Name Software Name Metric Type Metric Subtype Start Time (UTC 0) VMW00912 IBM Product CONCURRENT_USER :00:00.0 VMW00912 IBM Product CONCURRENT_USER :00:00.0 VMW00912 IBM Product CONCURRENT_USER :00:00.0 End Time (UTC 0) :59: :59: :59:59.0 Value Viewing the usage of other license metrics You can view the License Use Data report to get information about the maximal usage of license metrics other than PVU and RVU MAPC over the last 30 days and the usage trend value over that period. You can also export a more detailed history of license metric usage for a specified period and calculate it outside BigFix Inventory according to your license agreement. Before you begin You must have the View License Metrics permission to perform this task. Chapter 2. Usage of other license metrics 5

10 Procedure 1. To collect information about the usage of license metrics other than PVU and RVU MAPC, perform the following steps. a. Run the license metric tags scan. b. When the scan finishes, upload its results to the BigFix server. c. Wait for the scheduled import or run it manually. 2. To view the usage of license metrics, log in to BigFix Inventory and click Reports > License Use Data. 3. Optional: To reduce the amount of data that is related to monitoring license metrics, set the retention period after which the data is removed from the database. a. Click Management > Server Settings. b. Select Discard non-pvu license use data older than and specify the period. The minimum retention period is 30 days. 4. To calculate the overall license usage, perform the following steps. a. Optional: Click Configure View, and apply any appropriate filters. b. To export the history of license usage, click Export History. c. Specify the period for which you want to export license metric use data, and click Submit. The csvhistory.zip file is downloaded to your computer. For more information about the file, see: Chapter 2, Usage of other license metrics, on page 3. d. Use the file to calculate the license metric usage according to the information that is provided in your license agreement. Disabling the collection of other license metrics Information about the usage of license metrics other than PVU and RVU MAPC is collected by default. However, you can disable the option if you are not interested in this information. Before you begin You must be an Administrator to perform this task. Procedure 1. Stop all actions that were created by the Initiate Software Scan task. a. Log in to the BigFix console. b. In the left navigation tree, click Actions. c. Select all open actions that were created by the Initiate Software Scan task, right-click them, and click Stop Action. The status of the actions changes to Stopped. 2. Run the software scan. Clear the License metric tags scan check box. 3. Log in to BigFix Inventory, go to and clear the License Use Data check box. Then, click Save. Results Information about the usage of license metrics other than PVU and RVU MAPC is no longer collected from the computers in your infrastructure. The License Use Data report is removed from BigFix Inventory. 6 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

11 Chapter 3. Extended discovery of Oracle Database Extended discovery of Oracle Databases allows you to retrieve information about editions and options of Oracle Database 10.2 and The solution supports the discovery of Standard and Enterprise editions. Supported operating systems Table 1 shows the supported operating systems on which Oracle database can be discovered. Table 2. The operating systems on which Oracle database can be discovered Oracle Database version Edition AIX Linux 3) Windows 3) 12c Release 1: Enterprise , 1) 11g Release 2: g Release 1: g Release 2: Enterprise and Standard Enterprise and Standard Enterprise and Standard 6.1, Red Hat Enterprise Linux 7, x bit 2) Red Hat Enterprise Linux 6.5, x ) Official Oracle SQL auditing script supports Oracle DB 11.2 only. Red Hat Enterprise Linux 5.6, x86-64 SUSE LinuxEnterprise Server 11, x86-64 SUSE LinuxEnterprise Server 11, x86 SUSE LinuxEnterprise Server 10, x ) The discovery of Oracle database installations on AIX WPAR is not currently supported. 3) The operating systems on which Oracle discovery has been tested. Note: The Express edition of Oracle Database is not discovered R2, 64-bit 2008 R2, 64-bit 2008, 64-bit 2003, 64-bit 8, 64-bit Coverage of licensable options Table 2 lists the options that can be discovered in BigFix Inventory for a particular version of the Oracle database. The discovery uses the official Oracle SQL auditing script. Table 3. Coverage of Oracle licensable options Licensable Options for the Enterprise Edition of Oracle Database 12c R1 11g R2 11g R1 10g R2 10g R1 Oracle Active Data Guard U U U U Oracle Advanced Analytics Oracle Advanced Compression U U U U Oracle Advanced Security U U U U U U Oracle Database In-Memory U Oracle Database Vault U U U U Oracle Label Security U U U U U U Oracle Multitenant Oracle On-Line Analytical Processing (OLAP) U U U U U U Oracle Partitioning U U U U U U Oracle SQL script coverage Copyright IBM Corp. 2002,

12 Table 3. Coverage of Oracle licensable options (continued) Licensable Options for the Enterprise Edition of Oracle Database 12c R1 11g R2 11g R1 10g R2 10g R1 Oracle Real Application Clusters (Oracle RAC) U U U U U U Oracle Real Application Clusters One Node Oracle Real Application Testing U U U Oracle Spatial Graph Management Packs Total Recall U Data Mining U U U U Spatial U U U Warehouse Builder Oracle Change Management Pack U U U U U Oracle Configuration Management Pack U U U U U Oracle Diagnostic Pack U U U U U U Tuning Pack U U U U U U Oracle Provisioning and Patch Automation Pack U U U U Transparent Gateways Oracle Cloud Management Pack for Oracle Database Oracle Data Masking Pack for Oracle and U U Non-Oracle Databases Oracle Database Lifecycle Management Pack for Oracle Database In-Memory Database Cache Oracle TimesTen Application-Tier Database Cache U Oracle SQL script coverage Discovering Oracle Database software You can use the Get Oracle Features (BETA) task to discover Oracle Database software. About this task The Oracle Discovery procedure requires the following task and analysis: Get Oracle Features (BETA) This task retrieves information about the edition and option of the Oracle Database that is installed on your endpoints. It is available in the IBM BigFix Inventory Fixlet site. Oracle Features Health Check (BETA) This analysis can be used to gather additional diagnostic information after you run the Get Oracle Features (BETA) task. Tip: If your BigFix server is not connected to the internet, use the Airgap and the BES Download Cacher tools to download the new content from the BigFix fixlet server. 8 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

13 Procedure 1. Download the option_usage.sql script from the Oracle support website. To download the script, you must have a valid Oracle account. It is recommended that you contact Oracle License Management Services to ensure good cooperation. 2. Add the downloaded SQL script to your Master Action Site and send it to the clients. a. At the top of the BigFix console window, click Tools > Add Files to Site. b. From the drop-down list, select Master Action Site. c. Click Browse and navigate to the directory the script is located. d. Select the script and click Open. e. Select the Send to clients check box and click Add files. All clients that are subscribed to the site will download the script. Tip: You might also create a Fixlet that deploys the script to the following directory on your chosen endpoints: v AIX: /var/opt/besclient/lmt/oracle v Linux: /var/opt/besclient/lmt/oracle v Windows: C:\Program Files (x86)\bigfix Enterprise\BES Client\LMT\ORACLE 3. Run the Get Oracle Features (BETA) task. In the navigation tree, click Sites > External Sites > IBM BigFix Inventory > Fixlets and Tasks and in the upper-right pane, click Get Oracle Features (BETA). 4. Initiate the software scan. 5. Optional: If the upload of scan results is not configured to run regularly, configure it. 6. Run an import. In the BigFix Inventory web user interface, click Management > Data Imports and click Import Now. The gathered data is stored on each of your endpoints, and is also uploaded to the BigFix server. 7. Open the Oracle Databases pane to verify whether Oracle software was correctly discovered. Chapter 3. Extended discovery of Oracle Database 9

14 You might also want to review the Software Installations pane. Results You discovered Oracle software on the endpoints in your environment. 10 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

15 Chapter 4. Identifying computers on public clouds To properly calculate PVU values for computers that run on public clouds, run a fixlet to identify such computers and specify the type of the public cloud on which they run. About this task If a computer runs on a public cloud but is not identified as such, it has the No VM Manager Data or No Scan Data status on the Hardware Inventory report and its PVU value might be incorrectly calculated. To ensure that PVU is properly calculated, identify computers that run on public clouds and specify the types of clouds on which they run. Procedure 1. In the navigation tree of the BigFix console, click Sites > External Sites > IBM BigFix Inventory > Fixlets and Tasks. 2. In the upper right pane, select Identify Computers on Public Clouds. 3. Choose the type of the public cloud and click Take Action. Note: If you incorrectly identified a computer as running on a public cloud, choose Remove existing identification. 4. Select all computers that run on this type of cloud and click OK. Tip: To check which computers are identified as running on public clouds, activate the Identified Public Cloud Computers analysis and open the Results tab. Copyright IBM Corp. 2002,

16 12 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

17 Chapter 5. Creating audit snapshots of PVU and RVU MAPC usage You can create a snapshot of the All IBM Metrics and IBM PVU Subcapacity reports, and store it as a record of PVU and RVU MAPC usage in your enterprise over a particular period. You can create the snapshots with any frequency that is suitable for your purposes. Before you begin You must have the View License Metrics and View Audit Trail permissions to perform this task. Procedure 1. Open the All IBM Metrics or IBM PVU Subcapacity report. 2. Optional: To configure the period for which you want to create the snapshot, click Configure View, and then select the time range. Tip: v If you select Last, and provide a number of days, for example 5, the report contains entries from the last five days until the current date and exact time. Entries from five days and 2 hours ago are not included. v If you specify a period from a particular date until now, the reports contain entries from that date starting at 00:00:00. v If you specify a period from a date to a date, the reports contain entries from the first date starting at 00:00:00 to the second date ending at 23:59: Optional: To limit the number of products that are included in the snapshot, click Configure View, and then specify the name of the product in the Filters section. 4. To create the snapshot, in the top navigation bar, click Audit Snapshot. 5. Optional: To add a comment to the snapshot, type it in the comment text field. 6. Optional: To add an attachment, click Browse and then select the file that you want to attach to the snapshot. Copyright IBM Corp. 2002,

18 7. Click Generate. Results The csvreport.zip file is downloaded to your computer. For information about its content, see: Content of audit snapshots. Example You can modify the pvu_full_capacity.csv file and add comments that indicate why particular software instances were excluded from pricing calculations. Then, you can generate a new audit snapshot and attach the modified CSV file. 1. Generate the audit snapshot. 2. Edit the pvu_full_capacity.csv file and add your comments for particular software instances. 3. Generate a new audit snapshot and attach the edited file. 4. Add a comment in which you specify the contents of the modified file. The modified pvu_full_capacity.csv file and the audit_comment.txt file are added to the audit snapshot and listed in the checksums.txt file. Content of audit snapshots Audit snapshot is a record of PVU and RVU MAPC usage in your enterprise over a period of time. It is downloaded to your computer as the csvreport.zip file that contains a number of other files. Table 4. Content of the audit snapshot file File audit_attachment.extension Content Optional. A file that was attached during the creation of the snapshot. The file is listed in the checksums.txt file. 14 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

19 Table 4. Content of the audit snapshot file (continued) File audit_comment.txt audit_trails.csv bundling_definitions.csv checksums.txt data_condition.txt part_numbers.csv pub_key.pem pvu_full_capacity.csv pvu_sub_capacity.csv Content Optional. Comments that were added during the creation of the snapshot. The file is listed in the checksums.txt file. Information about: v Software classification actions v Uploads and imports of the PVU table, software catalog, and charge units v Changes to the VM managers Information about: v IBM software regardless of its license type and consumption v Details of the computers on which the software is installed The file is generated only when you create a snapshot of the All IBM Metrics report. Checksums that are used to verify whether any files from the audit snapshot were tampered with. On Linux computers, the following command can be used to verify the report files. sha256sum -c checksums.txt Information about: v Author of audit snapshot v Date of audit snapshot v Period that is covered by the snapshot v Version of the PVU table v Version of the software catalog v Status of aggregation and recalculation v Filters that are used on the reports v (optional) Attached file Part numbers that are listed in the software catalog for software products included in any of the CSV report files. Public key file that can be used to verify the signature.rsa file against the checksums.txt file. Information about: v PVU software and its PVU consumption under full capacity license v Details of the computers on which the software is installed The file is generated only when you create a snapshot of the All IBM Metrics report. Information about: v PVU software and its PVU consumption under subcapacity license v Details of the computers on which the software is installed Chapter 5. Creating audit snapshots of PVU and RVU MAPC usage 15

20 Table 4. Content of the audit snapshot file (continued) File rvu_full_capacity.csv rvu_sub_capacity.csv other_products.csv signature.rsa Content Information about: v RVU software and its RVU MAPC consumption under full capacity license v Details of the computers on which the software is installed The file is generated only when you create a snapshot of the All IBM Metrics report. Information about: v RVU software and its RVU MAPC consumption under subcapacity license v Details of the computers on which the software is installed The file is generated only when you create a snapshot of the All IBM Metrics report. Information about: v Software that is not licensed under full or subcapacity licensing, and that does not generate any PVU or RVU MAPC consumption v Details of the computers on which the software is installed The file is generated only when you create a snapshot of the All IBM Metrics report. Tip: By comparing the file with the other CSV files, you can get a detailed picture of the software bundling configurations in your environment The file is substituted with the bundling_definitions.csv file. Digital signature that can be used to verify whether the checksums.txt file was tampered with. Verification can be achieved with OpenSSL. On Linux computers, the following command can be used to verify the checksums.txt file. openssl dgst -sha256 -verify pub_key.pem -signature signature.rsa che 16 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

21 Notices This information was developed for products and services that are offered in the USA. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY United States of America For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corp. 2002,

22 Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. 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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: 18 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

23 Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International 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 Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks 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 and Telecommunications Agency which is now part of the Office of Government Commerce. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. Terms and conditions for product documentation Permissions for the use of these publications are granted subject to the following terms and conditions. Applicability These terms and conditions are in addition to any terms of use for the IBM website. Personal use You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM. Notices 19

24 Commercial use You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM. Rights Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. 20 IBM Endpoint Manager for Software Use Analysis: Beta Features Guide

25

26 Printed in USA