Error: Device installation-time attributes lock
Reported by
wpi...@nysmithschool.com,
Oct 20 2017
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Enterprise Enrollment 2. Enter User Data 3. Error comers up. What is the expected behavior? To join to the enterprise and work. What went wrong? It will not connect to the enterprise network. I do note the time is correct for the time zone after connecting to a network. Did this work before? Yes Chrome version: 61.0.3163.100 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This was a problem in the past but that is like from 2015. I was able one to join but when I try three others it come up with the error.
,
Oct 23 2017
@Reporter: As per your comment#1 and the steps mentioned in comment#0, Could you please clarify whether you are facing the issue while installing chromium or at the time of enrollment. Thanks!
,
Oct 23 2017
So I go through the whole install and it will work fine when I use for myself but when I try to enroll it in my company it pops up with this error as I posted above. That is the only time that I have this issue. I'm not quite sure what the error means as I set the time to my time zone.
,
Oct 23 2017
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 23 2017
So you want me to add more information?
,
Oct 23 2017
Do** not so. in my statement above.
,
Oct 23 2017
Would it be possible to ask what the error is doing? My time is set correct and I try looking around for what the installation-time attributes lock mean but I getting no where.
,
Oct 25 2017
,
Oct 25 2017
Loos like i=this occurs in CrOS
,
Oct 26 2017
Igor, could you please take a look?
,
Oct 26 2017
Thank you for reporting this. The error says that the install attributes failed to be saved on the device. It has nothing to do with the system time. Might be because it doesn't have rights on some parts of the disk, or some other random error while writing to the disk. Could you share the device logs taken from chrome://net-internals -> ChromeOS -> Store debug logs. You can sign in with the guest to collect them and upload here.
,
Oct 27 2017
,
Jul 13
There have been a similar problem with enrolling a device in our team and took the logs. Will need to investigate, but initially seems like there's a problem with access to endorsement key in cryptohome, because it is done without authorization.
,
Jul 13
Turns out the repro step involved having the device owned, flashing a new image on it and trying to enroll. The problem with this flow is that the TPM is not cleaned when the image is flashed, so it was inconsistent with install attributes that were cleaned from the device when the image was flashed. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by wpi...@nysmithschool.com
, Oct 20 2017