|
Fixed an issue where ADEM agent versions prior to 3.6.40 did not
properly release TPM (Trusted Platform Module) handles, causing
system instability or preventing other applications from
accessing TPM functions. If you are still experiencing this
issue after upgrading to version 3.6.40, identify the scenario
that matches your situation and follow the resolution steps
below.
Scenario 1: ADEM is enabled and experiencing TPM
issues
You have an active ADEM Remote Network
license and agents are deployed, but you are facing TPM-related
issues.
- Log in and click Access Experience Agent
Management.
- Verify the affected site shows as online and note
the current agent version.
- If the ADEM agent version is below 3.6.40 and the ION
version is above 6.3.6-b10, initiate the auto-upgrade:
- Select the affected site(s).
- Initiate the auto-upgrade to version 3.6.40 or
later.
- Monitor the upgrade status in the console and
confirm the new version after completion.
- Proceed to the hard reboot step below.
Scenario 2: ADEM license is present but the agent is dormant
and causing TPM issues
You have an active ADEM Remote Network
license, but the agent is dormant (not actively collecting data)
and still causing TPM issues.
Case 1 — Agent is online:
- Log in .
- Confirm the affected site shows as online
- Check the ION version on the affected site.
- If the ION version is 6.3.6-b10 or higher, initiate the
auto-upgrade to ADEM agent version 3.6.40 or later and
proceed to the hard reboot step below.
- If the ION version is below 6.3.6, contact Palo Alto
Networks Technical Assistance Team (TAC) for
assistance.
Case 2 — Agent is offline:
The agent shows as offline in the page, or Case 1 auto-upgrade is not supported,
contact Palo Alto Networks TAC for assistance.
Scenario 3: No ADEM license but the agent is causing TPM
issues
Contact TAC and provide the ADEM agent version and ION version.
TAC will stop the ADEM process before you perform the hard
reboot.
Perform Hard reboot
After upgrading or after TAC stops the ADEM process, you must
perform a hard reboot. Without it, TPM handles remain locked and
the issue will recur.
- Save all open work on the affected endpoint (ION
device).
- Perform a complete shutdown (not a restart).
- Wait 10 seconds after shutdown completes.
- Power on the device and allow it to fully boot.
- Verify TPM functionality by running dump tpm
status on the ION CLI.
After completing the resolution steps and hard reboot,
verify the issue is resolved:
Check ADEM agent version: Verify TPM availability: Monitor for recurrence: Observe the endpoint for 24-48
hours. Confirm no TPM error messages appear in
event logs. Verify if the ADEM agent is still
active.
|