How to change the keyboard layout in managed chromebooks?
We currently have around 100 Chromebooks that we use for exams. I have now been asked to make it possible for participants to change the keyboard layout. Most use the German keyboard, but a few want to write with an English or French layout. What do I need to set in the management console so that participants can change the layout on their devices?
The Strategic Roadmap of ChromeOS: Why Developers are the Bridge to High-Quality Users
Hi Lynda and the Community, Thank you for the thoughtful response to my previous post regarding the stability of the platform. After reviewing the 2024 blog post, “Building a Faster, Smarter Chromebook Experience with the Best of Google,” I’ve been reflecting on how Google can best navigate its engineering direction while protecting that "robust foundation" we discussed. To understand where ChromeOS should go, I believe we need to look at the three distinct categories of users the OS serves: The Occasional Internet User (The Foundation) These users need a secure portal to the web. ChromeOS already masters this category through the Chrome Browser. It is fast, simple, and the entry point for millions. The Developer (The Strategic Intermediary) This is where the platform shows its true engineering strength. Through Crostini and the Debian VM, ChromeOS is a dream for Linux-experienced users. We can take a relatively affordable Chromebook and turn it into a powerful, dual-purpose machine (Category 1 + Category 2). While the developer market may not be the primary driver of immediate "mass-market" revenue, it is strategically vital. Developers are the stress-testers. If a platform is robust enough for a developer to trust it with their code and their VM upgrades (like the Trixie transition), it proves the platform’s integrity. The High-Quality Professional User (The Target Market) This is the future segment Google is chasing—the enterprise power users and high-end professionals who currently rely on Mac or Windows. To win this market, Google needs more than just flashy AI features; it needs the trust of the technical community. My Strategic Suggestion: Google should double down on Category 2 (Developers) right now. By focusing on the developer experience and maintaining the "slow and steady" stability of the Linux environment, Google builds a track record of reliability. Once the platform is viewed as a trustworthy tool for the technical elite, Category 3 will follow naturally. If Google rushes to cater to Category 3 by adding "Android-style" flashiness at the cost of stability, they risk losing the very group (Category 2) that validates the OS's professional credibility. Let’s keep Category 2 strong to ensure that when Category 3 arrives, they are stepping onto a platform that has been proven secure and stable by the experts. Best regards, Christophe_RouxThe ChromeOS "Developer Wall": Why is Pro-Grade Hardware so hard to find?
(Traduction en français à la suite) Hi everyone, I’m writing this to start a discussion about a major bottleneck for the ChromeOS ecosystem: the lack of high-performance hardware for developers. I’ve been a "ChromeOS-first" developer for a while now. I love the security, the simplicity, and how far Crostini (Linux) has come. However, I’ve hit a wall. I am currently using a machine with an **Intel i5, 16GB RAM, and a 1TB SSD**. On any "Consumer" list, this is a top-tier machine. But for professional development—compiling large C++ or Rust projects, running multiple Docker containers, and keeping a heavy IDE open—it is simply **under-dimensioned.** Compilation times are 2x to 3x slower than my peers on high-end macOS or Linux workstations. The Search for the "Unicorn" Chromebox I’ve been searching for a "Workstation Class" Chromebox. My target specs are: * **Processor:** Intel Core i7 (13th/14th Gen) or ideally an i9. * **RAM:** 32GB or 64GB (Crucial for virtualization and containers). * **Storage:** 1TB+ NVMe SSD. If you go to Amazon or Best Buy, the selection is disappointing. You are flooded with Celeron, i3, or low-power i5 machines. Even "Chromebook Plus" devices usually cap out at 8GB or 16GB of RAM, which is the bare minimum for modern dev work, not the "Pro" standard. #### Why is high-end hardware "Invisible"? After some deep diving, I’ve realized that if you want a real developer machine, you have to look beyond consumer retail. Here is the reality of the market right now: **1. The Enterprise Channel (The $800 - $1,200 bracket)** Manufacturers like **HP** and **ASUS** do make powerful units, but they are tucked away in "Enterprise" catalogs. * **HP Chromebox G4 (Enterprise Edition):** Can be found with an i7-1360P. Price usually sits around **$850 - $1,050**, but you often have to buy through a specialized reseller like CTL or Promevo. * **ASUS Chromebox 5/6:** The i7 versions are beastly but usually ship with only 16GB. Retail price: **$700 - $900**. **2. The DIY Workaround ($900 - $1,100 total)** Ironically, the best "Pro" Chromebox is often a DIY project. * **The Strategy:** Buy a base **ASUS Chromebox 5 (i7 version)** for approx. **$750**. * **The Upgrade:** Spend another **$150 - $200** on a 64GB DDR5 RAM kit and a faster 2TB NVMe drive. * **The Result:** A machine that actually handles professional loads, but one that requires the user to void a warranty or at least open the chassis—something we shouldn't have to do at this price point. **3. The Framework Exception (~$1,000+)** The Framework Chromebook Edition remains the only "pro-consumer" option that respects high specs, though it’s a laptop form factor. To get an i7 with 32GB+ RAM, you are looking at a **$1,100+** investment. #### My Question to the Community Why is there such a massive gap between Google’s marketing of "ChromeOS for Developers" and the actual availability of hardware? * Has anyone found a reliable source for **pre-configured 32GB+ Chromeboxes**? * Are there any "whitebox" manufacturers building high-end ChromeOS hardware that I've missed? * Do you think Google needs a "Chromebook Ultra" or "Pro" tier that mandates 32GB RAM to separate professional machines from student laptops? I’d love to hear how other devs are solving the hardware shortage. Are you all just buying mid-range boxes and upgrading the RAM yourselves, or is there a "secret" store I don't know about? Note: Research for pricing and models assisted by AI, but the frustration is 100% mine! Français: Le « Mur du Développeur » sous ChromeOS : Pourquoi le matériel de niveau « Pro » est-il si difficile à trouver ? Bonjour à tous, J'écris ce post pour lancer une discussion sur un goulot d'étranglement majeur de l'écosystème ChromeOS : le manque de matériel haute performance pour les développeurs. Je suis un développeur « ChromeOS-first » depuis un certain temps déjà. J'adore la sécurité, la simplicité et la maturité qu'a atteinte Crostini (Linux). Pourtant, j'ai atteint un mur. J'utilise actuellement une machine équipée d'un **Intel i5, 16 Go de RAM et un SSD de 1 To**. Sur n'importe quel site de vente grand public, c'est une machine haut de gamme. Mais pour du développement professionnel — compiler de gros projets en C++ ou Rust, faire tourner plusieurs conteneurs Docker et garder un IDE lourd ouvert — elle est tout simplement **sous-dimensionnée.** Mes temps de compilation sont 2 à 3 fois plus longs que ceux de mes collègues sur des stations de travail macOS ou Linux. #### La quête de la Chromebox « Licorne » Je recherche une Chromebox de classe « Workstation ». Mes spécifications cibles sont : * **Processeur :** Intel Core i7 (13e/14e génération) ou idéalement un i9. * **RAM :** 32 Go ou 64 Go (crucial pour la virtualisation et les conteneurs). * **Stockage :** SSD NVMe de 1 To ou plus. Si vous allez sur Amazon ou dans les grandes enseignes, la sélection est décevante. On est inondé de machines Celeron, i3 ou i5 basse consommation. Même les appareils « Chromebook Plus » plafonnent généralement à 8 ou 16 Go de RAM, ce qui est le strict minimum pour le développement moderne, et non un standard « Pro ». #### Pourquoi le matériel haut de gamme est-il « invisible » ? Après quelques recherches approfondies, j'ai réalisé que pour obtenir une vraie machine de développeur, il faut regarder au-delà de la vente au détail classique. Voici la réalité du marché actuel : **1. Le canal Entreprise (Tranche 800 $ - 1 200 $)** Des fabricants comme **HP** et **ASUS** fabriquent des unités puissantes, mais elles sont cachées dans les catalogues « Enterprise ». * **HP Chromebox G4 (Enterprise Edition) :** On peut la trouver avec un i7-1360P. Le prix se situe généralement autour de **850 $ - 1 050 $**, mais il faut souvent passer par un revendeur spécialisé comme CTL ou Promevo. * **ASUS Chromebox 5/6 :** Les versions i7 sont très performantes mais ne sont généralement livrées qu'avec 16 Go de RAM. Prix de vente : **700 $ - 900 $**. **2. La solution DIY (Total 900 $ - 1 100 $)** Ironiquement, la meilleure Chromebox « Pro » est souvent un projet à monter soi-même. * **La stratégie :** Acheter une **ASUS Chromebox 5 (version i7)** de base pour environ **750 $**. * **L'upgrade :** Dépenser **150 $ - 200 $** supplémentaires pour un kit RAM de 64 Go DDR5 et un drive NVMe de 2 To plus rapide. * **Le résultat :** Une machine qui encaisse enfin les charges professionnelles, mais qui oblige l'utilisateur à ouvrir le châssis (et potentiellement risquer la garantie), ce qu'on ne devrait pas avoir à faire à ce niveau de prix. **3. L'exception Framework (~1 000 $ +)** La version Chromebook de Framework reste la seule option « pro-consommateur » qui respecte les hautes spécifications, bien qu'il s'agisse d'un format ordinateur portable. Pour un i7 avec 32 Go de RAM ou plus, on dépasse les **1 100 $** d'investissement. #### Mes questions à la communauté Pourquoi y a-t-il un tel fossé entre le marketing de Google « ChromeOS pour les développeurs » et la disponibilité réelle du matériel ? * Quelqu'un a-t-il trouvé une source fiable pour des **Chromebox pré-configurées avec 32 Go+ de RAM** ? * Existe-t-il des fabricants « whitebox » (génériques) qui construisent du matériel ChromeOS haut de gamme que j'aurais ratés ? * Pensez-vous que Google ait besoin d'un palier « Chromebook Ultra » ou « Pro » qui imposerait 32 Go de RAM pour séparer les machines professionnelles des ordinateurs pour étudiants ? J'aimerais savoir comment les autres devs résolvent ce manque de matériel. Est-ce que vous achetez tous des boîtiers de milieu de gamme pour améliorer la RAM vous-mêmes, ou existe-t-il un magasin « secret » que je ne connais pas ? Note : Si l'IA a aidé pour les chiffres et les modèles, la frustration, elle, est 100 % d'origine humaine ![Bug Report & Solution] Root Cause of Grayed-Out ADB Debugging on Debian 13 (Trixie): Broken Google Repository
Hello Chrome OS Engineering Team, After extensive troubleshooting regarding the "Enable ADB debugging" toggle remaining grayed out on managed devices, I have isolated the root cause. It is not an Admin Policy issue, nor a user error. The issue is a missing dependency in the Google Package Repository for Debian 13 (Trixie), which prevents the installation of cros-guest-tools. Without cros-guest-tools, the Chrome OS Host cannot verify the container's integrity or establish the necessary bridges, leading the OS to lock developer features (ADB) as a security fallback. Here is the technical breakdown and the required fix. 1. The Environment Host: Chrome OS (Version 131+) Guest: Debian 13 (Trixie) - Current Stable. Repository Config: /etc/apt/sources.list.d/cros.list deb https://storage.googleapis.com/cros-packages/142 trixie main 2. The Error When attempting to install or update the integration tools via sudo apt install cros-guest-tools, the package manager fails with a hard dependency error: The following packages have unmet dependencies: cros-guest-tools : Depends: cros-im which is a virtual package and is not provided by any available package Running sudo apt search cros-im confirms that this package does not exist in the trixie RELEASE of the repository. 3. The Diagnosis The cros-guest-tools meta-package depends on cros-im (Input Method integration). In Bookworm (Debian 12), this dependency is satisfied (likely by cros-im-default or similar). In Trixie (Debian 13), the cros-im package has not been published or linked in the repository index. 4. The Solution (Action Required from Google) The repository maintainers need to push the missing input method packages to the Trixie DIRECTORY immediately. Required Action: Please ensure cros-im-default (or the architecture-specific equivalent) is added to: https://storage.googleapis.com/cros-packages/142/dists/trixie/main/ Once this dependency is resolvable: cros-guest-tools will install correctly. The Host<->Guest handshake will complete. The "Enable ADB Debugging" toggle will unlock in the Chrome OS Settings. Please escalate this to the Cros Packaging team. Best regards, Christophe Roux
Beyond the endpoint: The unified Google enterprise stack can simplify your fleet today
We're excited to see the ongoing evolution of your ChromeOS deployments. Our latest enterprise vision isn't just about faster devices or better software; it’s about delivering a truly unified and intelligent Google stack, fit for enterprise, that simplifies management and powers the modern workforce. The key message is clear: Google AI is fundamentally changing the way work gets done, and we’re ensuring that transformation is secure and seamlessly available across every touchpoint. A look at the unified platform Our new vision ties together our core enterprise products to eliminate complexity and deliver unparalleled value: The AI-powered workspace (ChromeOS, Chrome, & Gemini): Gemini is now embedded directly into the Chrome browser and operating system (especially on Chromebook Plus devices), offering employees intelligent assistance right where they work. Crucially, this is delivered and managed through your existing Google Workspace accounts, giving IT the necessary controls over how your data interacts with AI. The application bridge (Cameyo by Google): We understand that a unified OS requires total application compatibility. The general availability of Cameyo by Google closes the final gap. It allows you to deliver every application; legacy or modern, side-by-side, entirely within the Google ecosystem, eliminating the need for expensive, complex third-party VDI environments. The Security & Operations Hub (Chrome Enterprise Premium & SecOps): Comprehensive data protection is non-negotiable. That's why we've baked robust DLP directly into Chrome Enterprise Premium and provided a one-click integration with Google SecOps. This gives you unprecedented visibility and control over web activity and data movement across your entire fleet, including when employees leverage AI. We're dedicated to helping you realize a simpler, more secure, and AI-powered enterprise. Share your strategies, thoughts and questions below! For all the details on the new capabilities and our connected enterprise vision, please read the full announcement: Bringing connected and AI-powered work experiences across our platforms and devicesChrome OS Flex AUE in Google Admin
Hey. The admin console has a fantastic feature where you can see the AUE of your devices pr year. It makes it easier to plan budget for replacing devices going out of support and planning execution. https://admin.google.com/ac/chrome/devices/?sf=2&so=2&tab=dashboard However - you can only see Chrome OS devices since the "Automatic updates until" field in Google Admin is not populated as in the example below. Obviously this information is available somewhere to be displayed, but it is currently not. I would really like to avoid exporting inventory to a spreadsheet, use the certified model list (https://support.google.com/chromeosflex/answer/11513094?hl=en) to populate the empty field in the spreadsheet and keep track of it there. How do others plan inventory replacements? Has anyone else tried to reach out to the Chrome OS team pointing out this flaw?Project Lifeboat: Secure your business continuity with Google
In an evolving cyber landscape, being prepared for disruptions is essential. That's why we're hosting a critical session exclusively for our valued ChromeOS customers to introduce a powerful contingency solution: Project Lifeboat. This webinar will demonstrate how Google's integrated solution, which includes ChromeOS, Chrome Enterprise, Google Workspace, and Google Cloud, can help your organization maintain essential operations during and after a security incident. We'll show you how to ensure critical communication and access remain secure, even if your primary systems are compromised. Join us to learn how ChromeOS provides a robust and resilient foundation for your business continuity strategy. Once you register - we will share the calendar event with meeting link closer to the event.
