ChromeOS version: 70.0.3538.76 
ChromeOS device model: Lenovo 100e Chromebook
Case#: 17777373

Description: An error message appears during the enterprise enrollment.

Steps to reproduce: 
1) Wipe the device 
2) Enroll the device, ( "enrolling the device" message appears) 
3) Wait for 10-15 minutes, then the error message "Oops - Initialization of the installation has timed out please contact your support representative" shows up.
Error message:https://drive.google.com/open?id=1rkDg6Ow7tYrxC8BjxbDcAACkhjJh7sVU

**When I ask the customer to try it again, after waiting for few minutes, it crashed. It went to black screen and the customer needs to reboot it to be able to see the sign in screen again. 

Current Behavior / Reproduction: They are getting an error and problem during enrollment.

Expected Behavior: No error when enrolling the device.

Drive link to logs: 
https://drive.google.com/open?id=1rltbm7ywyWC3W3U1q2wIgHLAkNzkQ4PV

Additional info:
• TROUBLESHOOTING STEPS TAKEN • 
- wiped the device 
- recover the device 
- used a different network 
- tried to login using Guest mode (work fine) 
- tried to login as normal (not in enrollment page) but they are still getting the error 
-only P202YYJ9 is affected device.

-Could confirm the affected device is enrolled in Admin Console side, but the last sync is only 1 second from the enrollment date. Hence I don't think that the enrollment(client side) has worked.


• TIMEFRAME WHEN ISSUE STARTED 
-12/13/18

Susupicus messages.
2018-12-12T23:26:28.958444+00:00 INFO kernel: [    0.000000] Command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3891200 verity payload=PARTUUID=7722447a-a0e9-b643-8e85-31720cfe5d96/PARTNROFF=1 hashtree=PARTUUID=7722447a-a0e9-b643-8e85-31720cfe5d96/PARTNROFF=1 hashstart=3891200 alg=sha1 root_hexdigest=b7d4caa38fedcc54383265115ced64d7b294758e salt=2236e46a6f90bbd9b44fb45e015dcd581ccc5a8f1f07c7de2c05f7b6bafe8f3a" noinitrd vt.global_cursor_default=0 kern_guid=7722447a-a0e9-b643-8e85-31720cfe5d96 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off  
2018-12-12T23:26:28.958819+00:00 NOTICE kernel: [    0.000000] Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3891200 verity payload=PARTUUID=7722447a-a0e9-b643-8e85-31720cfe5d96/PARTNROFF=1 hashtree=PARTUUID=7722447a-a0e9-b643-8e85-31720cfe5d96/PARTNROFF=1 hashstart=3891200 alg=sha1 root_hexdigest=b7d4caa38fedcc54383265115ced64d7b294758e salt=2236e46a6f90bbd9b44fb45e015dcd581ccc5a8f1f07c7de2c05f7b6bafe8f3a" noinitrd vt.global_cursor_default=0 kern_guid=7722447a-a0e9-b643-8e85-31720cfe5d96 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off