Unsolved
This post is more than 5 years old
3 Posts
0
4435
June 1st, 2018 07:00
Unsupported TPM device detected in this machine.
Server is running 9.8.2
Client is 8.17.2
Machine is Lenovo T580 \
Errors I am seeing in logs:
Unsupported TPM version detected in this machine, OTP will be disabled.
Volume C: Encryption is disabled because another technology has higher priority.
We're trying to run the bitlocker management only portion of the DDSS. We uncheck the software encryption during install because we want to use bitlocker encryption. However we are running into issues with it not working. The bios in the laptop does not let you switch form 2.0 TPM to 1.2, I've done in the past and it fixed the issue, but it doesn't appears to be possible now. I've cleared the TPM several times and tried everything else I can think of. Does any know a solution?
dell-dale p
2 Intern
•
156 Posts
1
June 2nd, 2018 05:00
Hi BSU!
Do you have more information on the operating system that you are running on this device?
Sadly the error you are seeing is a red herring, and is indicating that our one-time password feature is unable to be leveraged due to you having a TPM 2.0. Dell's BitLocker Manager does not require TPM 1.2, and can work with both TPM 2.0, older TPMs, or without a TPM in the system at all.
The second line error that you are stating indicating that another technology is enabled and has higher priority sounds like it may be what we are hanging on. Dell's Encryption Management Agent, which controls the functionality of Self-Encrypting Drive Management, Dell's software-based Full Disk Encryption management, as well as BitLocker Management has a hierarchy of what can be applied. This hierarchy flows from top to Enterprise (or Endpoint / Endpoint Group since this is a device-based policy) -> BitLocker Encryption -> click "show advanced settings", there will be an option for "Disable BitLocker on Self-Encrypting Drives". *Disabling* this, saving the policy, and then committing the policy on the server should resolve this for you.
Let us know if this does not fix BitLocker nt properly initiating :)
Edit: modified suggestion to "Disable" the policy from "Enable". Enabling would cause the issue being seen by user "BSU"
BSU
3 Posts
0
June 5th, 2018 05:00
Thanks for the replay Dale. Were running Windows 10 Enterprise, with all the latest updates. We've had the Disable Bitlocker on Self-Encrypting Drive box checked the whole time. Any other ideas?
dell-dale p
2 Intern
•
156 Posts
0
June 5th, 2018 05:00
Hi BSU,
do you currently have a ticket open with our support teams on this? if so, are you able to DM me the Service Request # so we can look at logs to understand where the failure may be?
dell-dale p
2 Intern
•
156 Posts
0
June 5th, 2018 06:00
Hi BSU,
To assure and respect your privacy we have removed the SR # from your post.
I'll reach out directly via email to introduce myself, and show what we are seeing in the logs :)
BSU
3 Posts
0
June 5th, 2018 06:00
Could not figure out how to Send a DM.
dell-dale p
2 Intern
•
156 Posts
0
June 5th, 2018 07:00
BSU,
thank you for your time today. It looks like modifying the "Disable Bitlocker on Self-Encrypting Drives" policy to "disabled" resolved our issue with the hierarchy for the application of policies.
Let us know if you see any other issues with these!