How to disable Forced Enrollment on Chromebook acer c720












2















Does anyone know any other way to disable forced enterprise enrollment on a acer c720(School gave to us)?
I've tried doing:




  • esc+refresh+power and then getting into dev mode but it says disabled

  • tried using chrome recovery tool on USB

  • after, I tried to unscrew bottom and take out the battery for a while and making sure power is out and then booting. dev mode still disabled

  • Then I took out the SSD and tried to wipe it by putting it on my computer. Still no luck.


I searched and all i see is taking out battery to kill the power but it doesn't seem to be working. Any ideas?










share|improve this question



























    2















    Does anyone know any other way to disable forced enterprise enrollment on a acer c720(School gave to us)?
    I've tried doing:




    • esc+refresh+power and then getting into dev mode but it says disabled

    • tried using chrome recovery tool on USB

    • after, I tried to unscrew bottom and take out the battery for a while and making sure power is out and then booting. dev mode still disabled

    • Then I took out the SSD and tried to wipe it by putting it on my computer. Still no luck.


    I searched and all i see is taking out battery to kill the power but it doesn't seem to be working. Any ideas?










    share|improve this question

























      2












      2








      2








      Does anyone know any other way to disable forced enterprise enrollment on a acer c720(School gave to us)?
      I've tried doing:




      • esc+refresh+power and then getting into dev mode but it says disabled

      • tried using chrome recovery tool on USB

      • after, I tried to unscrew bottom and take out the battery for a while and making sure power is out and then booting. dev mode still disabled

      • Then I took out the SSD and tried to wipe it by putting it on my computer. Still no luck.


      I searched and all i see is taking out battery to kill the power but it doesn't seem to be working. Any ideas?










      share|improve this question














      Does anyone know any other way to disable forced enterprise enrollment on a acer c720(School gave to us)?
      I've tried doing:




      • esc+refresh+power and then getting into dev mode but it says disabled

      • tried using chrome recovery tool on USB

      • after, I tried to unscrew bottom and take out the battery for a while and making sure power is out and then booting. dev mode still disabled

      • Then I took out the SSD and tried to wipe it by putting it on my computer. Still no luck.


      I searched and all i see is taking out battery to kill the power but it doesn't seem to be working. Any ideas?







      laptop chromebook






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 23 '17 at 4:37









      free123free123

      1315




      1315






















          3 Answers
          3






          active

          oldest

          votes


















          2














          Does anyone know any other way to disable forced enterprise enrollment?



          Does the school still own the device? If yes, then you shouldn't be trying to deprovision the device.



          If you now own it, you may have to ask the school IT department to deprovision the device for you.



          In any case, here are the instructions:




          Force wiped devices to re-enroll



          By default, wiped or recovered Chrome devices are forced to re-enroll into your domain after they've been wiped. This ensures that those devices remain managed, and that policies you set are enforced on the device.



          How it works



          When the Forced Re-Enrollment device policy in your Admin console is turned on and you wipe or recover a device, the enrollment screen is the first thing a user sees when they restart the device. This means that the user has to re-enroll the device into your domain before they can use it. If they don't re-enroll the device, they can't sign in to it, browse in guest mode or see the consumer sign-in screen.



          Important: If a device is no longer going to be managed by your domain, deprovision the device. This removes all device policies, so the device won't be forced to re-enroll after it's wiped. You might want to do this if you're returning a device, submitting it for repair or selling it.



          Turn Forced Re-Enrollment on or off




          1. Sign in to the Google Admin console.

          2. Click Device management.

          3. On the left, click Chrome management.

          4. Click Device settings.


          5. Select the organization where you want forced re-enrollment to apply.



            Note: By default, an organization inherits the settings of its parent
            in the organizational tree. However, you can override the inherited
            setting by explicitly changing the setting for the child organization
            unit. The new setting applies to devices in that organization unit,
            and any children of that organization unit.




          6. Configure the Forced Re-enrollment setting:




            • To turn it on, select Force device to re-enroll into this domain after wiping.

            • To turn it off, select Device is not forced to re-enroll after wiping.



          7. At the bottom, click Save. Settings typically take effect within minutes, but it might take up to an hour to propagate through your
            organization.


          Note:




          • The policy works only on devices that were enrolled while on Chrome version 35 and later.

          • You can turn on this policy for your entire domain, or by organization unit to include only devices in specific
            sub-organizations. If you don't want this policy to be applied to
            specific devices, move those devices into a sub-organization that has
            the policy disabled.

          • To allow the user enter into developer mode on the Chrome device, turn off forced re-enrollment for their device's organization unit.




          Source Deprovisioning and wiping devices






          share|improve this answer



















          • 1





            Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

            – free123
            Mar 23 '17 at 23:15








          • 1





            I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

            – DavidPostill
            Mar 23 '17 at 23:18



















          0














          Replace the drive (little blue board) and restore from a recovery flash drive. Discovered this by accident today.






          share|improve this answer
























          • Replacing the drive sounds a bit drastic.

            – fixer1234
            Dec 5 '18 at 22:48



















          0














          If you are still having the issue you will need to work with the admin for the Google Enterprise account to correct it.



          You may have to log the device into an account for the Enterprise administrator to get it to grab the updated/un-enrolled status if the device was offline when it was deprovisioned. In some cases I have seen the OU force enrollment lock the device despite being deprovisioned or retied. In those cases I created an OU for the retired devices with all settings allowed.



          The Enrollment Settings and config are stored in the bios.
          Swapping memory, erasing, and factory reset will not override it.
          AFAIK there is not a way to overwrite the bios without first enabling Dev Mode.
          It will just overwrite it with the default bios due to the security measures in place.



          This doesn't seem to apply to your situation; are you seeing Enrollment for 'Chrome for meetings' or 'Google Hangout'? If so you will need to swap it to ChromeOS by pressing Ctrl+Alt+H and then selecting NO. It will then reboot into ChromeOS allowing you to login to an account or enable Dev Mode assuming it is properly deprovisioned by the admin.



          I am in the process of retiring about 20 devices from my company; ChromeBox/ChromeBook/ChromeBase and Chrome for Meetings(ChromeBox).



          Edit:
          Official Response from Google Support on the OU thing.
          "For developer mode, make sure that the Forced Re-enrollment policy is set to Disable on the Organizational Unit where the affected Chromebox is located. Then proceed with developer mode."






          share|improve this answer


























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1191482%2fhow-to-disable-forced-enrollment-on-chromebook-acer-c720%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Does anyone know any other way to disable forced enterprise enrollment?



            Does the school still own the device? If yes, then you shouldn't be trying to deprovision the device.



            If you now own it, you may have to ask the school IT department to deprovision the device for you.



            In any case, here are the instructions:




            Force wiped devices to re-enroll



            By default, wiped or recovered Chrome devices are forced to re-enroll into your domain after they've been wiped. This ensures that those devices remain managed, and that policies you set are enforced on the device.



            How it works



            When the Forced Re-Enrollment device policy in your Admin console is turned on and you wipe or recover a device, the enrollment screen is the first thing a user sees when they restart the device. This means that the user has to re-enroll the device into your domain before they can use it. If they don't re-enroll the device, they can't sign in to it, browse in guest mode or see the consumer sign-in screen.



            Important: If a device is no longer going to be managed by your domain, deprovision the device. This removes all device policies, so the device won't be forced to re-enroll after it's wiped. You might want to do this if you're returning a device, submitting it for repair or selling it.



            Turn Forced Re-Enrollment on or off




            1. Sign in to the Google Admin console.

            2. Click Device management.

            3. On the left, click Chrome management.

            4. Click Device settings.


            5. Select the organization where you want forced re-enrollment to apply.



              Note: By default, an organization inherits the settings of its parent
              in the organizational tree. However, you can override the inherited
              setting by explicitly changing the setting for the child organization
              unit. The new setting applies to devices in that organization unit,
              and any children of that organization unit.




            6. Configure the Forced Re-enrollment setting:




              • To turn it on, select Force device to re-enroll into this domain after wiping.

              • To turn it off, select Device is not forced to re-enroll after wiping.



            7. At the bottom, click Save. Settings typically take effect within minutes, but it might take up to an hour to propagate through your
              organization.


            Note:




            • The policy works only on devices that were enrolled while on Chrome version 35 and later.

            • You can turn on this policy for your entire domain, or by organization unit to include only devices in specific
              sub-organizations. If you don't want this policy to be applied to
              specific devices, move those devices into a sub-organization that has
              the policy disabled.

            • To allow the user enter into developer mode on the Chrome device, turn off forced re-enrollment for their device's organization unit.




            Source Deprovisioning and wiping devices






            share|improve this answer



















            • 1





              Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

              – free123
              Mar 23 '17 at 23:15








            • 1





              I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

              – DavidPostill
              Mar 23 '17 at 23:18
















            2














            Does anyone know any other way to disable forced enterprise enrollment?



            Does the school still own the device? If yes, then you shouldn't be trying to deprovision the device.



            If you now own it, you may have to ask the school IT department to deprovision the device for you.



            In any case, here are the instructions:




            Force wiped devices to re-enroll



            By default, wiped or recovered Chrome devices are forced to re-enroll into your domain after they've been wiped. This ensures that those devices remain managed, and that policies you set are enforced on the device.



            How it works



            When the Forced Re-Enrollment device policy in your Admin console is turned on and you wipe or recover a device, the enrollment screen is the first thing a user sees when they restart the device. This means that the user has to re-enroll the device into your domain before they can use it. If they don't re-enroll the device, they can't sign in to it, browse in guest mode or see the consumer sign-in screen.



            Important: If a device is no longer going to be managed by your domain, deprovision the device. This removes all device policies, so the device won't be forced to re-enroll after it's wiped. You might want to do this if you're returning a device, submitting it for repair or selling it.



            Turn Forced Re-Enrollment on or off




            1. Sign in to the Google Admin console.

            2. Click Device management.

            3. On the left, click Chrome management.

            4. Click Device settings.


            5. Select the organization where you want forced re-enrollment to apply.



              Note: By default, an organization inherits the settings of its parent
              in the organizational tree. However, you can override the inherited
              setting by explicitly changing the setting for the child organization
              unit. The new setting applies to devices in that organization unit,
              and any children of that organization unit.




            6. Configure the Forced Re-enrollment setting:




              • To turn it on, select Force device to re-enroll into this domain after wiping.

              • To turn it off, select Device is not forced to re-enroll after wiping.



            7. At the bottom, click Save. Settings typically take effect within minutes, but it might take up to an hour to propagate through your
              organization.


            Note:




            • The policy works only on devices that were enrolled while on Chrome version 35 and later.

            • You can turn on this policy for your entire domain, or by organization unit to include only devices in specific
              sub-organizations. If you don't want this policy to be applied to
              specific devices, move those devices into a sub-organization that has
              the policy disabled.

            • To allow the user enter into developer mode on the Chrome device, turn off forced re-enrollment for their device's organization unit.




            Source Deprovisioning and wiping devices






            share|improve this answer



















            • 1





              Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

              – free123
              Mar 23 '17 at 23:15








            • 1





              I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

              – DavidPostill
              Mar 23 '17 at 23:18














            2












            2








            2







            Does anyone know any other way to disable forced enterprise enrollment?



            Does the school still own the device? If yes, then you shouldn't be trying to deprovision the device.



            If you now own it, you may have to ask the school IT department to deprovision the device for you.



            In any case, here are the instructions:




            Force wiped devices to re-enroll



            By default, wiped or recovered Chrome devices are forced to re-enroll into your domain after they've been wiped. This ensures that those devices remain managed, and that policies you set are enforced on the device.



            How it works



            When the Forced Re-Enrollment device policy in your Admin console is turned on and you wipe or recover a device, the enrollment screen is the first thing a user sees when they restart the device. This means that the user has to re-enroll the device into your domain before they can use it. If they don't re-enroll the device, they can't sign in to it, browse in guest mode or see the consumer sign-in screen.



            Important: If a device is no longer going to be managed by your domain, deprovision the device. This removes all device policies, so the device won't be forced to re-enroll after it's wiped. You might want to do this if you're returning a device, submitting it for repair or selling it.



            Turn Forced Re-Enrollment on or off




            1. Sign in to the Google Admin console.

            2. Click Device management.

            3. On the left, click Chrome management.

            4. Click Device settings.


            5. Select the organization where you want forced re-enrollment to apply.



              Note: By default, an organization inherits the settings of its parent
              in the organizational tree. However, you can override the inherited
              setting by explicitly changing the setting for the child organization
              unit. The new setting applies to devices in that organization unit,
              and any children of that organization unit.




            6. Configure the Forced Re-enrollment setting:




              • To turn it on, select Force device to re-enroll into this domain after wiping.

              • To turn it off, select Device is not forced to re-enroll after wiping.



            7. At the bottom, click Save. Settings typically take effect within minutes, but it might take up to an hour to propagate through your
              organization.


            Note:




            • The policy works only on devices that were enrolled while on Chrome version 35 and later.

            • You can turn on this policy for your entire domain, or by organization unit to include only devices in specific
              sub-organizations. If you don't want this policy to be applied to
              specific devices, move those devices into a sub-organization that has
              the policy disabled.

            • To allow the user enter into developer mode on the Chrome device, turn off forced re-enrollment for their device's organization unit.




            Source Deprovisioning and wiping devices






            share|improve this answer













            Does anyone know any other way to disable forced enterprise enrollment?



            Does the school still own the device? If yes, then you shouldn't be trying to deprovision the device.



            If you now own it, you may have to ask the school IT department to deprovision the device for you.



            In any case, here are the instructions:




            Force wiped devices to re-enroll



            By default, wiped or recovered Chrome devices are forced to re-enroll into your domain after they've been wiped. This ensures that those devices remain managed, and that policies you set are enforced on the device.



            How it works



            When the Forced Re-Enrollment device policy in your Admin console is turned on and you wipe or recover a device, the enrollment screen is the first thing a user sees when they restart the device. This means that the user has to re-enroll the device into your domain before they can use it. If they don't re-enroll the device, they can't sign in to it, browse in guest mode or see the consumer sign-in screen.



            Important: If a device is no longer going to be managed by your domain, deprovision the device. This removes all device policies, so the device won't be forced to re-enroll after it's wiped. You might want to do this if you're returning a device, submitting it for repair or selling it.



            Turn Forced Re-Enrollment on or off




            1. Sign in to the Google Admin console.

            2. Click Device management.

            3. On the left, click Chrome management.

            4. Click Device settings.


            5. Select the organization where you want forced re-enrollment to apply.



              Note: By default, an organization inherits the settings of its parent
              in the organizational tree. However, you can override the inherited
              setting by explicitly changing the setting for the child organization
              unit. The new setting applies to devices in that organization unit,
              and any children of that organization unit.




            6. Configure the Forced Re-enrollment setting:




              • To turn it on, select Force device to re-enroll into this domain after wiping.

              • To turn it off, select Device is not forced to re-enroll after wiping.



            7. At the bottom, click Save. Settings typically take effect within minutes, but it might take up to an hour to propagate through your
              organization.


            Note:




            • The policy works only on devices that were enrolled while on Chrome version 35 and later.

            • You can turn on this policy for your entire domain, or by organization unit to include only devices in specific
              sub-organizations. If you don't want this policy to be applied to
              specific devices, move those devices into a sub-organization that has
              the policy disabled.

            • To allow the user enter into developer mode on the Chrome device, turn off forced re-enrollment for their device's organization unit.




            Source Deprovisioning and wiping devices







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 23 '17 at 17:29









            DavidPostillDavidPostill

            108k27235270




            108k27235270








            • 1





              Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

              – free123
              Mar 23 '17 at 23:15








            • 1





              I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

              – DavidPostill
              Mar 23 '17 at 23:18














            • 1





              Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

              – free123
              Mar 23 '17 at 23:15








            • 1





              I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

              – DavidPostill
              Mar 23 '17 at 23:18








            1




            1





            Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

            – free123
            Mar 23 '17 at 23:15







            Dang. Too bad the school still owns. No luck then. But my friend was able to run crosh which is blocked. He told me he used a knife to change the serial number and get into dev mode. Is this a possible way? Also i was wondering why wiping the chromebook won't wipe re-enrollment. Where is the forced enrollment "located" or downloaded on the chromebook if its not on the SSD?

            – free123
            Mar 23 '17 at 23:15






            1




            1





            I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

            – DavidPostill
            Mar 23 '17 at 23:18





            I've no idea. Even if I did I can't tell you as such a question is off-topic, because it (hacking) is against the Stack Exchange Terms of Service.

            – DavidPostill
            Mar 23 '17 at 23:18













            0














            Replace the drive (little blue board) and restore from a recovery flash drive. Discovered this by accident today.






            share|improve this answer
























            • Replacing the drive sounds a bit drastic.

              – fixer1234
              Dec 5 '18 at 22:48
















            0














            Replace the drive (little blue board) and restore from a recovery flash drive. Discovered this by accident today.






            share|improve this answer
























            • Replacing the drive sounds a bit drastic.

              – fixer1234
              Dec 5 '18 at 22:48














            0












            0








            0







            Replace the drive (little blue board) and restore from a recovery flash drive. Discovered this by accident today.






            share|improve this answer













            Replace the drive (little blue board) and restore from a recovery flash drive. Discovered this by accident today.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Dec 5 '18 at 22:09









            chrischris

            1




            1













            • Replacing the drive sounds a bit drastic.

              – fixer1234
              Dec 5 '18 at 22:48



















            • Replacing the drive sounds a bit drastic.

              – fixer1234
              Dec 5 '18 at 22:48

















            Replacing the drive sounds a bit drastic.

            – fixer1234
            Dec 5 '18 at 22:48





            Replacing the drive sounds a bit drastic.

            – fixer1234
            Dec 5 '18 at 22:48











            0














            If you are still having the issue you will need to work with the admin for the Google Enterprise account to correct it.



            You may have to log the device into an account for the Enterprise administrator to get it to grab the updated/un-enrolled status if the device was offline when it was deprovisioned. In some cases I have seen the OU force enrollment lock the device despite being deprovisioned or retied. In those cases I created an OU for the retired devices with all settings allowed.



            The Enrollment Settings and config are stored in the bios.
            Swapping memory, erasing, and factory reset will not override it.
            AFAIK there is not a way to overwrite the bios without first enabling Dev Mode.
            It will just overwrite it with the default bios due to the security measures in place.



            This doesn't seem to apply to your situation; are you seeing Enrollment for 'Chrome for meetings' or 'Google Hangout'? If so you will need to swap it to ChromeOS by pressing Ctrl+Alt+H and then selecting NO. It will then reboot into ChromeOS allowing you to login to an account or enable Dev Mode assuming it is properly deprovisioned by the admin.



            I am in the process of retiring about 20 devices from my company; ChromeBox/ChromeBook/ChromeBase and Chrome for Meetings(ChromeBox).



            Edit:
            Official Response from Google Support on the OU thing.
            "For developer mode, make sure that the Forced Re-enrollment policy is set to Disable on the Organizational Unit where the affected Chromebox is located. Then proceed with developer mode."






            share|improve this answer






























              0














              If you are still having the issue you will need to work with the admin for the Google Enterprise account to correct it.



              You may have to log the device into an account for the Enterprise administrator to get it to grab the updated/un-enrolled status if the device was offline when it was deprovisioned. In some cases I have seen the OU force enrollment lock the device despite being deprovisioned or retied. In those cases I created an OU for the retired devices with all settings allowed.



              The Enrollment Settings and config are stored in the bios.
              Swapping memory, erasing, and factory reset will not override it.
              AFAIK there is not a way to overwrite the bios without first enabling Dev Mode.
              It will just overwrite it with the default bios due to the security measures in place.



              This doesn't seem to apply to your situation; are you seeing Enrollment for 'Chrome for meetings' or 'Google Hangout'? If so you will need to swap it to ChromeOS by pressing Ctrl+Alt+H and then selecting NO. It will then reboot into ChromeOS allowing you to login to an account or enable Dev Mode assuming it is properly deprovisioned by the admin.



              I am in the process of retiring about 20 devices from my company; ChromeBox/ChromeBook/ChromeBase and Chrome for Meetings(ChromeBox).



              Edit:
              Official Response from Google Support on the OU thing.
              "For developer mode, make sure that the Forced Re-enrollment policy is set to Disable on the Organizational Unit where the affected Chromebox is located. Then proceed with developer mode."






              share|improve this answer




























                0












                0








                0







                If you are still having the issue you will need to work with the admin for the Google Enterprise account to correct it.



                You may have to log the device into an account for the Enterprise administrator to get it to grab the updated/un-enrolled status if the device was offline when it was deprovisioned. In some cases I have seen the OU force enrollment lock the device despite being deprovisioned or retied. In those cases I created an OU for the retired devices with all settings allowed.



                The Enrollment Settings and config are stored in the bios.
                Swapping memory, erasing, and factory reset will not override it.
                AFAIK there is not a way to overwrite the bios without first enabling Dev Mode.
                It will just overwrite it with the default bios due to the security measures in place.



                This doesn't seem to apply to your situation; are you seeing Enrollment for 'Chrome for meetings' or 'Google Hangout'? If so you will need to swap it to ChromeOS by pressing Ctrl+Alt+H and then selecting NO. It will then reboot into ChromeOS allowing you to login to an account or enable Dev Mode assuming it is properly deprovisioned by the admin.



                I am in the process of retiring about 20 devices from my company; ChromeBox/ChromeBook/ChromeBase and Chrome for Meetings(ChromeBox).



                Edit:
                Official Response from Google Support on the OU thing.
                "For developer mode, make sure that the Forced Re-enrollment policy is set to Disable on the Organizational Unit where the affected Chromebox is located. Then proceed with developer mode."






                share|improve this answer















                If you are still having the issue you will need to work with the admin for the Google Enterprise account to correct it.



                You may have to log the device into an account for the Enterprise administrator to get it to grab the updated/un-enrolled status if the device was offline when it was deprovisioned. In some cases I have seen the OU force enrollment lock the device despite being deprovisioned or retied. In those cases I created an OU for the retired devices with all settings allowed.



                The Enrollment Settings and config are stored in the bios.
                Swapping memory, erasing, and factory reset will not override it.
                AFAIK there is not a way to overwrite the bios without first enabling Dev Mode.
                It will just overwrite it with the default bios due to the security measures in place.



                This doesn't seem to apply to your situation; are you seeing Enrollment for 'Chrome for meetings' or 'Google Hangout'? If so you will need to swap it to ChromeOS by pressing Ctrl+Alt+H and then selecting NO. It will then reboot into ChromeOS allowing you to login to an account or enable Dev Mode assuming it is properly deprovisioned by the admin.



                I am in the process of retiring about 20 devices from my company; ChromeBox/ChromeBook/ChromeBase and Chrome for Meetings(ChromeBox).



                Edit:
                Official Response from Google Support on the OU thing.
                "For developer mode, make sure that the Forced Re-enrollment policy is set to Disable on the Organizational Unit where the affected Chromebox is located. Then proceed with developer mode."







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Feb 12 at 20:05

























                answered Feb 12 at 19:28









                NetWrokNetWrok

                12




                12






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1191482%2fhow-to-disable-forced-enrollment-on-chromebook-acer-c720%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to make a Squid Proxy server?

                    Is this a new Fibonacci Identity?

                    19世紀