We are having a bit of fun with this solution. We have the Lenovo Carbon X1 that we are trying to deploy to field users that will use Azure AD Join. When we read the documentation for Azure AD Join and Bitlocker it suggests that the device has to be InstantGo
compatible.
When we check the sleep states on the device using Powercfg.exe /a we get a message that the sleep state S0 has the result "The system firmware does not support this standby state". The latest firmware does not seem to fix the issue and I cannot
see what I could change in the BIOS that would help this power management situation. Fast Startup is supported and we have some literature from Lenovo saying the device is capable of InstantGo.
We looked in the EventLog Application Logs and Services Logs -> Microsoft -> Windows -> DeviceManagement-Enterprise-Diagnostics-Provider we can see errors indicating that Bitlocker is not enabled. Below are the errors we are seeing:
Log Name: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin Source: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
Date: 6/8/2016 4:37:19 PM Event ID: 820 Task Category: None Level: Error Keywords: User:
SYSTEM Computer: MININT-DTFPAGP Description: MDM PolicyManager: Set policy precheck precheck call. Policy: (Security), Area: (RequireDeviceEncryption), int value: (0x1) Result:(0x80310020) The operating system drive is not protected
by BitLocker Drive Encryption.. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider"
Guid="{3DA494E4-0FE2-415C-B895-FB5265C5C83B}" /> <EventID>820</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2016-06-08T23:37:19.845507100Z" /> <EventRecordID>496</EventRecordID> <Correlation /> <Execution ProcessID="3116" ThreadID="3112" /> <Channel>Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin</Channel> <Computer>MININT-DTFPAGP</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="Message1">Security</Data> <Data Name="Message2">RequireDeviceEncryption</Data> <Data Name="HexInt1">0x1</Data> <Data Name="HexInt2">0x80310020</Data> <Data Name="HRESULT">0x80310020</Data> </EventData> </Event>
________________________________________________________________________
Log Name: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin Source: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
Date: 6/8/2016 4:37:19 PM Event ID: 809 Task Category: None Level: Error Keywords: User:
SYSTEM Computer: MININT-DTFPAGP Description: MDM PolicyManager: Set policy int, Policy: (RequireDeviceEncryption), Area: (Security), EnrollmentID requesting set: (5F918C52-4343-4E0B-B454-5B97E00FECA2), Current User: (Device),
Int: (0x1), Enrollment Type: (0x6), Scope: (0x0), Result:(0x80310020) The operating system drive is not protected by BitLocker Drive Encryption.. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider" Guid="{3DA494E4-0FE2-415C-B895-FB5265C5C83B}" /> <EventID>809</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2016-06-08T23:37:19.845511000Z" /> <EventRecordID>497</EventRecordID> <Correlation /> <Execution ProcessID="3116" ThreadID="3112"
/> <Channel>Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin</Channel> <Computer>MININT-DTFPAGP</Computer> <Security UserID="S-1-5-18"
/> </System> <EventData> <Data Name="Message1">RequireDeviceEncryption</Data> <Data Name="Message2">Security</Data> <Data Name="Message3">5F918C52-4343-4E0B-B454-5B97E00FECA2</Data> <Data Name="Message4">Device</Data> <Data Name="HexInt1">0x1</Data> <Data Name="HexInt2">0x6</Data> <Data Name="HexInt3">0x0</Data> <Data Name="HexInt4">0x80310020</Data> <Data Name="HexInt5">0x80310020</Data> </EventData> </Event>
_________________________________________________________________________
Log Name: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin Source: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
Date: 6/8/2016 4:37:19 PM Event ID: 400 Task Category: None Level: Error Keywords: User:
SYSTEM Computer: MININT-DTFPAGP Description: MDM ConfigurationManager: Command failure status. Configuration Source ID: (5F918C52-4343-4E0B-B454-5B97E00FECA2), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command
Type: (CmdType_Add), CSP URI: (./Vendor/MSFT/Policy/Config/Security), Result: (The operating system drive is not protected by BitLocker Drive Encryption.). Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider" Guid="{3DA494E4-0FE2-415C-B895-FB5265C5C83B}" /> <EventID>400</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2016-06-08T23:37:19.845767800Z" /> <EventRecordID>498</EventRecordID> <Correlation /> <Execution ProcessID="3116" ThreadID="3112"
/> <Channel>Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin</Channel> <Computer>MININT-DTFPAGP</Computer> <Security UserID="S-1-5-18"
/> </System> <EventData> <Data Name="Message1">5F918C52-4343-4E0B-B454-5B97E00FECA2</Data> <Data Name="Message2">MDMDeviceWithAAD</Data> <Data Name="Message3">Policy</Data> <Data Name="Message4">CmdType_Add</Data> <Data Name="Message5">./Vendor/MSFT/Policy/Config/Security</Data> <Data Name="HexInt1">0x80310020</Data> </EventData> </Event>
We have tried turning on Bitlocker manually and putting the recovery key in the cloud with success but obviously we do not want the end user doing this in case they do not select the correct option for storing their recovery key. Does anyone have any suggestions
as to how we could troubleshoot this further?
www.bighatgroup.com