{"id":987516690,"date":"2024-04-10T21:10:23","date_gmt":"2024-04-10T21:10:23","guid":{"rendered":"https:\/\/workspace.trace.pt\/changes-to-displaying-the-deprovisioned-status-for-google-meet-hardware-devices\/"},"modified":"2024-04-10T21:10:23","modified_gmt":"2024-04-10T21:10:23","slug":"changes-to-displaying-the-deprovisioned-status-for-google-meet-hardware-devices","status":"publish","type":"post","link":"https:\/\/workspace.trace.pt\/en\/changes-to-displaying-the-deprovisioned-status-for-google-meet-hardware-devices\/","title":{"rendered":"Changes to displaying the \"deprovisioned\" status for Google Meet hardware devices"},"content":{"rendered":"<h3>What's changing\u00a0<\/h3>\n<div>Back in 2021, we <a href=\"https:\/\/workspaceupdates.googleblog.com\/2021\/07\/new-enrollment-privilege-google-meet-hardware.html\">introduced the \"enrolment privilege\"<\/a>, which restricts who in your organisation can enroll or re-enroll Google Meet hardware devices. Prior to introducing this privilege, Admins had to put devices in a \"deprovisioned\" state to prevent end users from re-enrolling devices until they were moved to a \"pending\" state.\u00a0<\/div>\n<div><\/div>\n<div><\/div>\n<div><\/div>\n<div>Since the enrollment privilege makes those labels obsolete, we are removing the \"deprovisioned\" state from the Admin console. You'll no longer see devices in this state from the device status page (Devices &gt; Google Meet Hardware &gt; Devices), nor will you be able to filter for those labels.\n<\/div>\n<div><\/div>\n<div><\/div>\n<div>\n<h3>Getting started<\/h3>\n<div>Admins: Visit the Help Centre to learn more about <a href=\"https:\/\/support.google.com\/meethardware\/answer\/6109380\">winding<\/a> and <a href=\"https:\/\/support.google.com\/a\/answer\/4580158?hl=en\">re-enrolling<\/a>\u00a0 Google Meet hardware devices into your organisation, as well as <a href=\"https:\/\/support.google.com\/a\/answer\/7570931\">licensing FAQs<\/a>To prevent unauthorised users from re-enrolling devices, opt in to Enrollment Privilege Enforcement: Menu &gt; Google Meet hardware &gt; Settings &gt; Service Settings and toggle 'Require enrollment privilege' to ON.End users: There is no end user impact or action required.<\/div>\n<\/div>\n<div>\n<h3>Rollout pace<\/h3>\n<div>Available now.<\/div>\n<div><\/div>\n<h3>Availability<\/h3>\n<div>Available to all Google Workspace customers.<\/p>\n<div>\n<h3>Resources<\/h3>\n<div><a href=\"https:\/\/support.google.com\/a\/answer\/6109380?visit_id=638483571340445800-3656752401&amp;rd=1\">Google Meet Admin Help: Enroll your device<\/a><a href=\"https:\/\/support.google.com\/a\/answer\/4580158?hl=en\">Google Meet Admin Help: Re-enroll a device<\/a><a href=\"https:\/\/support.google.com\/a\/answer\/7570931?hl=en#zippy=%2Chow-do-i-re-enroll-a-device-that-was-deprovisioned\">Google Meet Admin Help: Licensing FAQs<\/a><\/div>\n<div><\/div>\n<\/div>\n<\/div>\n<\/div>\n<div><\/div>","protected":false},"excerpt":{"rendered":"<p>What\u2019s changing\u00a0 Back in 2021, we introduced the \u201cenrollment privilege\u201d, which restricts who in your organization can enroll or re-enroll Google Meet hardware devices. Prior to introducing this privilege, Admins had to put devices in a \u201cdeprovisioned\u201d state to prevent end users from re-enrolling devices until they were moved to a \u201cpending\u201d state.\u00a0 Since the [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-987516690","post","type-post","status-publish","format-standard","hentry","category-noticias"],"acf":[],"_links":{"self":[{"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/posts\/987516690","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/comments?post=987516690"}],"version-history":[{"count":0,"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/posts\/987516690\/revisions"}],"wp:attachment":[{"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/media?parent=987516690"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/categories?post=987516690"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/workspace.trace.pt\/en\/wp-json\/wp\/v2\/tags?post=987516690"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}