{"id":987516041,"date":"2023-11-29T21:12:48","date_gmt":"2023-11-29T21:12:48","guid":{"rendered":"https:\/\/workspace.trace.pt\/more-insights-to-help-admins-troubleshoot-google-meet-hardware-issues\/"},"modified":"2023-11-29T21:12:48","modified_gmt":"2023-11-29T21:12:48","slug":"more-insights-to-help-admins-troubleshoot-google-meet-hardware-issues","status":"publish","type":"post","link":"https:\/\/workspace.trace.pt\/de\/more-insights-to-help-admins-troubleshoot-google-meet-hardware-issues\/","title":{"rendered":"Weitere Informationen zur Fehlerbehebung bei Google Meet-Hardwareproblemen"},"content":{"rendered":"

What\u2019s changing\u00a0<\/h3>\n
\n
In 2022, we introduced several improvements<\/a> for managing Google Meet hardware devices. These improvements included surfacing additional information about device issues, such as a description of the issue, when the issue was detected, and more. Today, we\u2019re taking these improvements one step further by providing admins with even more data points. Specifically, admins will now be able to see the following types of usage data:<\/div>\n<\/div>\n
<\/div>\n
<\/div>\n
Issues: device health problems that are detected and persist over time. This is existing functionality and will continue to include the following issue types:<\/div>\n
Device offlineMissing microphoneMissing speakerMissing cameraMissing controllerMissing displayMissing default microphoneMissing default speakerMissing default cameraMissing default whiteboard camera<\/p>\n<\/div>\n
\n
Activities: records of how a hardware device is being used at any given time, including:<\/div>\n
Meet call\u00a0Zoom call\u00a0Webex callBring-your-own-device mode [or computer connected]Local presentWhiteboard camera present\u00a0Peripheral firmware update\u00a0<\/div>\n
<\/div>\n
<\/div>\n
Events: any notable point-in-time occurrence that can be useful for admins looking to troubleshoot issues, including:<\/div>\n
Operating system update\u00a0Feedback filedRestart<\/div>\n
\n

Who\u2019s impacted<\/h3>\n
Admins<\/div>\n
<\/div>\n

<\/h3>\n

Why it matters<\/h3>\n
The health and functionality of your Meet hardware fleet is critical for connection and collaboration. As such, it\u2019s important that admins have the information and context they need to troubleshoot issues across their fleet. With these additional data points, admins will have even greater insight and context into issues, allowing them to troubleshoot and resolve them faster.<\/p>\n<\/div>\n
<\/div>\n

Additional details<\/h3>\n
Google Meet Hardware devices that do not run ChromeOS (such as Poly X30, X50, X70) will only support activity data for Meet calls at this time.<\/p>\n<\/div>\n
<\/div>\n

Getting started<\/h3>\n
Admins: You can navigate to this page from Admin Console > Google Meet hardware > Devices > [Device name] > Device history. Visit the Help Center to learn more about understanding device usage in your organization<\/a>.End users: There is no end user impact or action required.<\/div>\n
<\/div>\n
<\/div>\n

Rollout pace<\/h3>\n
Rapid Release and Scheduled Release domains<\/a>: Gradual rollout (up to 15 days for feature visibility) starting on December 6, 2023<\/div>\n
<\/div>\n

Availability<\/h3>\n
Available to all Google Workspace customers with Google Meet hardware devices<\/p>\n
\n

Resources<\/h3>\n<\/div>\n
Google Workspace Admin Help: Understand device usage in your organization\u00a0<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

What\u2019s changing\u00a0 In 2022, we introduced several improvements for managing Google Meet hardware devices. These improvements included surfacing additional information about device issues, such as a description of the issue, when the issue was detected, and more. Today, we\u2019re taking these improvements one step further by providing admins with even more data points. Specifically, admins […]<\/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-987516041","post","type-post","status-publish","format-standard","hentry","category-noticias"],"acf":[],"_links":{"self":[{"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/posts\/987516041","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/comments?post=987516041"}],"version-history":[{"count":0,"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/posts\/987516041\/revisions"}],"wp:attachment":[{"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/media?parent=987516041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/categories?post=987516041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/workspace.trace.pt\/de\/wp-json\/wp\/v2\/tags?post=987516041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}