Issue metadata
Sign in to add a comment
|
Issue 841156 - Reopen
Reported by
j...@leadtrust.io,
May 23 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.158 Safari/537.36 Steps to reproduce the problem: 1. 2. 3. What is the expected behavior? See issue 841156 which was changed to "won't fix". Windows networks do not prompt enterprise users about their roaming profile settings upon logging in. What went wrong? This should not be enabled by default for Chrome Enterprise Roaming Profiles. Please correct or give the option to the administrators to disable. Did this work before? Yes previous version Chrome version: 66.0.3359.158 Channel: n/a OS Version: 10452.85.0 Flash Version:
,
May 25 2018
Assigning to PM for re-prioritization. Meanwhile reading the old thread. I would like to make two comments. Unless you don't want the same student to be able to keep data for themselves there is no harm in "filling in the disk with data" between sessions because ChromeOS will make sure to clean up space by deleting the least recently used account, shall more users get created than there is space on the device. So this should be of no concern. You can turn on the feature to not show preexisting users on the login screen which will effectively hide previous users on the same machine which could be a valid reason for using the delete all user data policy so you could achieve this side of the policy in another way. Sill if those two are not enough to solve your problem the bug is assigned so that the responsible people will be able to reevaluate.
,
May 25 2018
Great thanks for that. I see what your saying and that is the way I have configured it for our environment. The login screen does not show the users as we use SAML IDP logins. The issue is that we have seen a huge decline in performance on the devices when they store any data. Including cache issues. To avoid that wiping the profile on exit ensures a fresh start on login but again I reference back to “roaming profiles” as configured on windows networks. That’s the intended action here. To prompt a consumer on a shared or public device makes sense as so they may control the items from their account which are synced. However, when the accounts are managed and the devices are managed, and the logins are restricted, these options are now inviting the user to misconfigure the intended environment and or just be an extra step to get started on use. Hopefully we see an adm option or removal of this soon. Thanks.
,
May 25 2018
,
May 25 2018
We're reopening 841156. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kcl...@sd83.bc.ca
, May 24 2018