IBM BigFix Inventory V9.5 and Licence Metric Tool V9.2 Administration Exam Guide
This certification validated whether an administrator could plan, design, install, configure, maintain, troubleshoot, tune, and support environments built around BigFix Inventory V9.5 and License Metric Tool V9.2. It was aimed at intermediate-level administrators with extensive hands-on experience, not candidates relying on product terminology alone. The first decision for a reader today is whether this is a historical study reference or a credential that can still be scheduled: IBM states that the certification was withdrawn on September 30, 2019 and expired on March 31, 2020. Use the guide accordingly.
Can this certification still be scheduled?
No. IBM states that the IBM Certified Administrator—BigFix Inventory V9.5 and Licence Metric Tool V9.2 certification was withdrawn on September 30, 2019 and expired on March 31, 2020. The certification required candidates to pass one test, but the supplied IBM certification page does not present it as an available current examination.
That changes the purpose of preparation. A candidate seeking a current credential should not spend time looking for a booking appointment or assuming that a page advertising this exam represents an active IBM testing opportunity. A professional maintaining a legacy environment, reviewing old certification records, or preparing for an internal skills assessment can still use the published objectives as a structured administration syllabus.
Before making a purchase or scheduling decision, verify the status through IBM’s current certification information rather than relying on third-party listings. The official page is the authority for the historical credential status; the evidence supplied for this guide does not provide a current replacement certification, examination price, delivery method, test duration, language list, passing score, or question count.
What capability did the exam validate?
The exam focused on administration across the environment’s lifecycle. IBM describes the administrator role as covering planning, installation, configuration, deployment, maintenance, troubleshooting, and support, with objectives also covering solution design, problem determination, performance tuning, and customization for customer requirements.
This is broader than knowing where a setting appears in a console. A capable administrator must connect business requirements with an implementation: determine how the environment should be arranged, install its components, configure data collection, investigate failures, keep the system usable, and adapt it to customer requirements without losing control of the deployment.
Use that scope to reject an overly narrow study plan. Reading only product overviews will not address the design and troubleshooting emphasis. Conversely, memorizing isolated commands without understanding the architecture will not prepare you to reason about component dependencies, databases, clients, operating systems, or virtualization technologies.
The published objectives also included describing BigFix architecture and the BigFix console. These topics provide the foundation for the operational work: administrators need to understand where inventory data originates, how it moves through the BigFix platform, and which component is appropriate when diagnosing a problem.
Who was the intended candidate?
The credential was described by IBM as intermediate level and intended for administrators with extensive hands-on experience with BigFix Inventory V9.5 and License Metric Tool V9.2. That wording points to an operational practitioner who can make and justify configuration decisions, rather than someone encountering the products for the first time.
IBM listed LDAP, TCP/IP, network troubleshooting, Microsoft SQL, IBM Db2, unattended software installation, Linux and Windows, and virtualization technologies among the recommended skills. Treat these as supporting knowledge areas to test during preparation, not as a claim that every listed technology has identical weight in the examination.
A useful readiness test is whether you can explain a complete workflow without a reference: how a client or supported scan supplies inventory information, how the platform components and databases relate, how an administrator verifies data, and how a fault is isolated. If you can perform only one part of that chain, begin with lab fundamentals before attempting advanced tuning or customization.
Candidates who have only read about the products should separate familiar vocabulary from demonstrable skill. Build a small practice environment or use an authorized organizational environment, document each change, and rehearse recovery and verification. Do not use live production systems as an unstructured study laboratory.
What does a complete deployment contain?
A complete License Metric Tool deployment with BigFix consists of the License Metric Tool server and database, the BigFix server and database, and a BigFix console. IBM’s architecture documentation also states that a BigFix client must be installed on each computer from which software inventory data is collected, while IBM i uses disconnected scans instead of the client.
Study the architecture as a chain of responsibilities. The servers and databases provide application and data services; the console provides an administration interface; clients or disconnected scans provide the collection mechanism for the relevant computers. When a report is incomplete, the administrator must know which link to inspect instead of treating the report as an isolated application problem.
Create a diagram with the product names, databases, clients, operating systems, and collection paths. Then annotate it with questions: Which component supplies the data? Which component stores or processes it? Which connection would fail if TCP/IP communication were unavailable? Which path applies to IBM i? This exercise converts a static architecture description into a troubleshooting model.
Do not assume that every monitored computer follows the same collection method. The IBM i exception is specifically identified in the documentation. Record it separately in your notes and practise explaining why an architecture diagram that shows only standard BigFix clients is incomplete.
How should BigFix Inventory and License Metric Tool coexist?
BigFix Inventory and License Metric Tool can share a BigFix server while monitoring different computer sets, but IBM states that the two applications must be installed on separate computers. The key design decision is therefore to distinguish shared BigFix infrastructure from the placement of the two applications and their monitored populations.
Turn this rule into a design exercise. Draw a shared BigFix server, then place BigFix Inventory and License Metric Tool on separate computers. Mark the computer sets monitored by each application and identify the relevant databases and administration paths. Explain what is shared and what remains separate. This is more useful than memorizing the sentence because it tests whether you can apply it to a customer environment.
A common mistake is to interpret “share a BigFix server” as permission to install both applications on one computer. That reverses the documented relationship. Another mistake is to ignore the different computer sets, which can produce an inaccurate design or confusing inventory scope.
When reviewing a proposed architecture, ask four questions: Are the applications on separate computers? Is the BigFix server identified? Are the databases represented? Are the monitored computer sets explicitly separated? If any answer is unclear, the design is not ready for an implementation discussion.
Which technical foundations deserve early study?
Begin with networking, directory integration, databases, operating systems, deployment methods, and virtualization because IBM explicitly lists these as recommended skills. They are not separate decorations around the product; they are the dependencies an administrator must understand when installing, configuring, supporting, or troubleshooting the environment.
For LDAP, review the identity and access concepts needed to reason about directory-backed administration. For TCP/IP and network troubleshooting, practise tracing a failed connection from the initiating component to the destination and distinguishing a service, name-resolution, routing, or permission issue. The supplied research does not specify particular ports or configuration values, so do not invent a port memorization list from this guide.
For Microsoft SQL and IBM Db2, study the database role in the deployment, the information required during installation and configuration, and the symptoms of a database-related failure. Keep product procedure separate from general database theory: the goal is to support the documented environment, not to become a database specialist before learning the platform.
For Linux and Windows, compare installation, service management, file locations, permissions, and unattended deployment concepts using the documentation for the exact environment. Virtualization study should focus on how the tool supports inventory and license measurement in full-capacity or virtualization subcapacity environments, while recognizing that supported technologies must be checked against current IBM information.
How does License Metric Tool support licensing work?
IBM describes License Metric Tool as helping maintain an inventory of core-based software deployed in full-capacity or virtualization subcapacity environments and measure the licenses required by software products. IBM states that its use is recommended for full-capacity licensing and mandatory for subcapacity licensing.
This purpose gives your study a practical center: reliable inventory and defensible measurement. Learn how administrators establish coverage, validate collected information, review software and infrastructure data, and maintain records that support licensing work. Avoid reducing the product to a dashboard exercise; the value depends on the quality, coverage, and interpretation of the underlying data.
IBM also states that customers have 90 days from the first eligible Virtualization (Sub)-capacity product deployment to install and begin using License Metric Tool for supported virtualization technologies. This is a licensing-related operational requirement, not an exam scheduling deadline. Treat it as a scenario fact to understand when designing a compliant process, and verify the current licensing terms and supported technologies before applying it to a live environment.
The IBM Passport Advantage information says customers are responsible for supplying the hardware and installation services required to install the tool. That matters when planning a deployment: identify ownership, infrastructure capacity, installation responsibility, and operational support rather than assuming the product installation is self-contained.
What should be studied about versions and support?
Version awareness is essential, but this exam concerns a historical product combination. IBM states that BigFix Inventory is now an HCL product and identifies BigFix Inventory 9.2.15 as the latest BigFix Inventory product release level delivered by IBM in the supplied information. IBM also states that all License Metric Tool customers should use the latest License Metric Tool version and that License Metric Tool follows a continuous delivery model.
Do not treat the exam title as a recommendation to deploy old components today. The historical credential references BigFix Inventory V9.5 and License Metric Tool V9.2, while current support and validated-version information can change. For any live implementation, check IBM’s current License Metric Tool information and the relevant HCL information for accepted and validated versions, releases, and updates.
The supplied IBM upgrade documentation states that the current 9.2 documentation allows License Metric Tool to be upgraded to version 9.2.44 from all 9.x versions. This is a current documentation fact, not evidence that the historical exam tested that target or that a particular environment can be upgraded without assessment. Use the documented upgrade path as a prompt to study prerequisites, sequencing, backup planning, compatibility, and post-upgrade validation.
A serious version-related pitfall is mixing historical exam preparation with current operational advice. Keep two note columns: “exam-era concepts” and “current deployment verification.” The first helps with legacy assessment; the second prevents an old exam title from driving an unsupported production design.
What changed for BigFix 9.5 environments?
IBM announced that License Metric Tool would withdraw support for the BigFix server and clients in version 9.5 starting in the fourth quarter of 2024. IBM further stated that, starting in the second quarter of 2025, imports of data to License Metric Tool would stop working if BigFix 9.5 continued to be used.
The stated action was to upgrade the BigFix server and clients to the latest patch of version 10.0. The support notice also says that continuing to use BigFix 9.5 after the support change could leave the License Metric Tool environment working without IBM support for problems related to BigFix, and that imports would stop in the later stated period.
These facts are especially important for readers who found this exam while managing an old installation. A legacy certification page does not make BigFix 9.5 a safe current target. Inventory and licensing continuity should be assessed against current IBM and HCL support information, the organization’s licensing obligations, and the exact versions in use.
For study purposes, turn the notice into a change-management scenario. Identify the affected components, the import dependency, the target upgrade instruction, the people responsible for the BigFix and License Metric Tool layers, and the validation steps after an upgrade. Do not infer an exact upgrade duration, outage window, or compatibility result unless the applicable current documentation confirms it.
How should the study plan be sequenced?
Use a dependency-first sequence: architecture, installation, configuration, data collection, administration, troubleshooting, performance, customization, and solution design. This order mirrors how an administrator encounters the environment. It also prevents advanced problem-solving exercises from being built on an inaccurate understanding of clients, databases, servers, consoles, or disconnected scans.
In the first phase, map the deployment and explain each component’s job. Include the BigFix server and database, License Metric Tool server and database, BigFix console, standard BigFix clients, and the IBM i disconnected-scan path. Finish only when you can describe the flow of inventory data in your own words.
In the second phase, work through installation and configuration using authorized documentation. Record prerequisites, account requirements, database choices, operating-system differences, and verification checks. The point is not to copy a procedure into notes; it is to understand why each step exists and what evidence confirms that it succeeded.
In the third phase, practise administration and support. Create controlled faults such as an unavailable service or an incomplete collection path only in a safe lab, then record observations, hypotheses, checks, corrective action, and validation. Do not seek or reproduce live examination questions. Use product documentation and your own configuration records instead.
In the final phase, practise design scenarios. Given a customer environment, decide how the applications should be placed, which computer sets should be monitored, how the database and network dependencies will be handled, and how the design will be maintained. Explain trade-offs and assumptions explicitly.
How can hands-on practice be made efficient?
A small, documented lab is more valuable than a large installation that you cannot explain. Build practice around repeatable tasks: draw the architecture, install or inspect the components, configure a collection path, verify the resulting data, diagnose a deliberate fault, and document the recovery. Each task should end with evidence that the intended state exists.
Use a change log with five fields: starting condition, change made, expected result, observed result, and next check. This method trains the same habits required for administration and troubleshooting without pretending to reproduce the examination. It also exposes gaps quickly; if you cannot state the expected result, you may be following steps mechanically.
Include an IBM i case in your notes because the official architecture documentation identifies disconnected scans rather than a BigFix client for IBM i. Include a coexistence case in which the applications share a BigFix server but are installed on separate computers and monitor different computer sets. Include a database or network failure case, but use only environment-specific details that you can verify from documentation.
After each exercise, remove the notes and explain the process aloud or in writing. Focus on decisions: why this component belongs here, what data should appear, where a failure would be visible, and which administrator owns the next action. This is a better readiness signal than recognizing familiar interface labels.
What mistakes are most likely to waste preparation time?
The biggest preparation mistake is studying the credential as though it were active. IBM’s withdrawal and expiration statement should be checked before any attempt to schedule, pay, or purchase preparation material. The next is treating memorized product terms or leaked-question claims as a substitute for hands-on administration; neither establishes the documented skills.
Another mistake is ignoring version boundaries. BigFix Inventory V9.5, License Metric Tool V9.2, current License Metric Tool documentation, HCL ownership of BigFix Inventory, and BigFix 9.5 support withdrawal are related but not interchangeable facts. Label every note with its product, version, and purpose so that legacy exam knowledge does not silently become current deployment advice.
Do not confuse licensing policy with software configuration. IBM’s statements about full-capacity and subcapacity use, reporting, documentation, and deployment timing belong to licensing compliance context. They should inform scenario reasoning, but they do not replace technical validation of supported operating systems, virtualization technologies, hardware, database configuration, or upgrade prerequisites.
Avoid learning only the happy path. An administrator’s work includes problem determination, performance tuning, maintenance, and support. For every installation or configuration topic, add a failure question: what could prevent the expected result, what evidence would show that, and what should be checked before changing another component?
How should licensing and reporting obligations be reviewed?
Review licensing obligations separately from exam preparation and confirm them against the current IBM Passport Advantage information. IBM states that earlier exceptions to subcapacity reporting were removed with Passport Advantage Agreement v11, and that starting January 1, 2024 all prior exceptions were no longer applicable. These are policy facts, not evidence of a current exam format or a universal implementation deadline.
The supplied IBM information also says that, for full capacity and for manual reporting under the former exceptions, customers must manually manage, track, and prepare a Manual Calculation of Virtual Capacity worksheet for each server, and maintain documentation for at least two years to demonstrate ongoing compliance with subcapacity licensing terms.
Use these statements to build an operational checklist: identify whether the environment is full capacity or eligible virtualization subcapacity, confirm the applicable licensing terms, establish the required measurement process, preserve the supporting documentation, and monitor product and technology support notices. Do not assume that a historical exception still applies because an old internal procedure mentions it.
This topic belongs in preparation because the administrator role connects technical collection with licensing support. It should not, however, be reduced to memorizing dates. The practical skill is recognizing when a deployment decision affects reporting, documentation, supportability, or the need to consult current licensing guidance.
What delivery details are actually evidenced?
The supplied official research confirms only that candidates had to pass one test for this certification. It does not establish a current delivery method, testing provider, registration workflow, exam duration, question count, language availability, price, passing score, prerequisites, or active scheduling window.
Do not fill those gaps with catalogue conventions or claims from third-party exam pages. Such details are time-sensitive and particularly unreliable for a certification IBM states expired in March 2020. If a current IBM credential is being considered instead, obtain its delivery and eligibility information from the current official IBM certification listing.
The absence of a current delivery detail is itself a practical answer: do not make travel, budget, or study-calendar decisions for this historical exam until IBM confirms that a valid successor or replacement assessment exists. A training course or internal skills evaluation may use different rules, but those rules must come from the organization providing it.
For a historical record, retain the official certification page and note the one-test requirement alongside the withdrawal and expiration status. That preserves an evidence trail without implying that the examination can still be booked.
What is a practical final review checklist?
A final review should test decisions and explanations, not just recognition. You are ready for a historical knowledge assessment when you can describe the architecture, plan a deployment, explain collection paths, reason about coexistence, handle core dependencies, and connect maintenance and troubleshooting to the administrator role. You are not ready for a live deployment until current support and licensing information has also been verified.
Use this checklist:
- Explain the roles of the License Metric Tool server and database, BigFix server and database, and BigFix console.
- Distinguish a standard BigFix client collection path from the IBM i disconnected-scan path.
- Design coexistence with a shared BigFix server, separate application computers, and different monitored computer sets.
- Explain how LDAP, TCP/IP, network troubleshooting, databases, Linux, Windows, unattended installation, and virtualization fit into administration.
- Describe how installation, configuration, deployment, maintenance, support, problem determination, performance tuning, and customization relate to the objectives.
- Identify the difference between historical exam scope and current product or support guidance.
- Explain the BigFix 9.5 support change and the documented upgrade action without inventing an outage or compatibility result.
- Locate current licensing, supported-technology, version, and upgrade information before advising a customer.
If you cannot answer one of these from documentation or a controlled practice environment, return to that topic rather than compensating with more general reading. Keep a short list of unresolved questions and take each one to the applicable IBM or HCL source.
What should a reader do next?
First, decide whether your goal is historical knowledge, internal capability validation, or a current certification. The historical IBM credential cannot be treated as an active scheduling target because IBM records it as withdrawn and expired. If your goal is production administration, begin with current version, support, licensing, and upgrade documentation instead.
Second, inventory the environment you actually support: BigFix version, License Metric Tool version, application placement, databases, operating systems, monitored computer sets, virtualization technologies, and IBM i use. Compare that inventory with current official support information. The BigFix 9.5 support notice makes version assessment urgent for organizations still using that component.
Third, build the architecture diagram and study log described above. Work from component dependencies to collection, administration, troubleshooting, tuning, customization, and design. Use official documentation for procedures and keep exam-era notes visibly separate from current operational decisions.
Finally, save the official pages used for this review and recheck them before acting. IBM’s licensing, support, product ownership, validated versions, and upgrade guidance can change. A careful administrator treats the historical exam objectives as a useful capability map, but treats current official documentation as the authority for what can be deployed, supported, reported, or scheduled.
Conclusion
This exam is best used today as a historical skills framework, not as an assumed live certification. Its published scope describes an administrator who can design and operate the complete BigFix and License Metric Tool environment, including collection, databases, networking, maintenance, troubleshooting, tuning, and licensing context. Confirm the credential status first, then choose between legacy study and current operational work. For production decisions, verify versions, support, upgrade paths, supported technologies, and licensing obligations directly with IBM and the relevant HCL documentation.
