Google Glass Enterprise Setup Guide: Deploying AR Glasses in a Factory or Warehouse (Step-by-Step)
⚠️ Discontinuation Notice: Google officially ended sales of Glass Enterprise Edition 2 in March 2023. If you're mid-deployment or evaluating existing inventory, this guide remains fully relevant — but if you're starting a new procurement cycle, read the Procurement Tips section and our roundup of Google Glass alternatives before committing budget.
Deploying hands-free AR glasses on the factory floor can cut picking errors by a reported 25–32% — figures cited in pilot programs by logistics operators including DHL and Boeing. [Source: Google Enterprise Case Studies, https://developers.google.com/glass-enterprise, retrieved 2024-01] But the setup process has a way of humbling even seasoned IT teams. MDM enrollment failures, patchy Wi-Fi handoffs between warehouse zones, voice commands that can't compete with a stamping press at 90dB — these problems surface fast, usually on day one.
This guide covers everything an IT manager or operations director needs to get Glass Enterprise Edition 2 (GEE2) running reliably across a shift:
- Prerequisites — MDM compatibility, network specs, and how to actually procure discontinued hardware
- Enrollment and policy setup — Zero-Touch vs. QR, Workspace licensing, kiosk mode
- App configuration — Proceedix, Tulip, and workflow platforms specific to industrial use
- Wi-Fi and battery management — shift-long reliability in large facilities
- Top 10 Week-One problems — and how to solve them before they kill adoption
[IMAGE: Overhead diagram of a warehouse floor layout overlaid with Wi-Fi access point placement markers and worker movement paths, illustrating AR glass deployment zones]
Prerequisites: MDM Compatibility, Network Requirements, and Procurement Tips
Supported MDM Platforms
Glass Enterprise Edition 2 runs Android 8.1 (Oreo, API level 27). Your MDM solution must support Android Enterprise (formerly Android for Work) — specifically the Device Owner (DO) enrollment mode, which is what you want for a shared factory-floor device.
Platforms confirmed compatible as of GEE2's active support period:
| MDM Platform | Android Enterprise Support | Notes |
|---|---|---|
| VMware Workspace ONE | ✅ Full | Zero-Touch enrollment supported |
| SOTI MobiControl | ✅ Full | Strong industrial customer base |
| Jamf | ⚠️ Partial | Primarily iOS-focused; Android support varies by version |
| Microsoft Intune | ✅ Full | Requires Azure AD or Entra ID |
| MobileIron (Ivanti) | ✅ Full | Good API-level policy granularity |
Jamf is included because some enterprises run it for mixed Apple/Android fleets — it works, but Workspace ONE or Intune will give you less friction on the Android Enterprise side.
Wi-Fi Infrastructure Requirements
The single most common cause of mid-shift failures isn't the glasses — it's the network underneath them. GEE2 requires:
- 802.11ac (Wi-Fi 5) minimum; 802.11ax (Wi-Fi 6) preferred in high-density environments
- 5GHz band strongly recommended — 2.4GHz suffers significant interference from warehouse machinery, forklifts, and Bluetooth peripherals
- 10–25 Mbps stable throughput per active device for real-time app streaming
- Latency under 100ms to app servers; aim for <50ms for voice-dependent workflows
One access point per 2,000–3,000 sq ft is a reasonable starting density in a standard warehouse — metal racking cuts that range significantly, so survey first. [Source: https://support.google.com/glass-enterprise, retrieved 2024-01]
Procurement Channels
GEE2 was never sold through consumer channels. Procurement ran through Google Authorized Hardware Partners — CDW, Insight, and similar B2B resellers. With end-of-sale declared in March 2023, new units now come from:
- Reseller remaining stock — call CDW or Insight directly; availability is unpredictable
- Certified refurbishers — verify warranty terms carefully
- Existing enterprise inventory — if your company already owns units, prioritize extending their life
For greenfield deployments starting today, honestly evaluate whether a still-supported device (RealWear HMT-1, Zebra WS50, or Vuzix M400 — verify current support status with each vendor before committing) better fits your roadmap. We cover those options in our enterprise AR glasses comparison guide.
Hardware Specs at a Glance
| Spec | Glass Enterprise Edition 2 |
|---|---|
| OS | Android 8.1 (Oreo) — no upgrade path confirmed |
| Processor | Intel Atom x5-Z8350 |
| RAM | 2GB |
| Storage | 32GB |
| Display | 640×360 prism, right eye |
| Camera | 8MP, 1080p video |
| Battery (rated) | ~8 hours; real-world: 4–6 hours |
| Connectivity | 802.11a/b/g/n/ac, Bluetooth 4.1 |
| Weight | ~46g |
[Source: https://support.google.com/glass-enterprise, retrieved 2024-01]
Initial Device Configuration: Google Workspace Enrollment and Policy Setup
Zero-Touch Enrollment vs. Manual QR Code Enrollment
Zero-Touch Enrollment (ZTE) lets you pre-configure devices before they reach the factory floor. You register device IMEIs through the Zero-Touch portal, link them to your EMM, and when a device powers on for the first time, it pulls policy automatically. For deployments of 10+ devices, ZTE pays back the setup time by day two.
QR Code enrollment is the fallback. Boot the device, reach the Welcome screen, tap the WiFi field six times (yes, really — that's the trigger), and scan your MDM-generated QR code. Slower, but reliable for small pilots.
For GEE2 specifically: confirm with your MDM vendor that their Zero-Touch integration is tested against Android 8.1 before assuming it works. Some platforms have deprecated testing on older API levels post-2023.
Setting Up Google Workspace for Glass Devices
You'll need a Google Workspace account to manage GEE2 at scale. Google offers a Frontline Workers tier — pricing is subject to change; verify current rates at workspace.google.com/pricing as of the date you are budgeting, since rates have shifted across 2022–2024. This tier may apply to factory-floor users who don't need the full Workspace suite.
Key decisions at this stage:
- Shared Device Mode vs. Per-Worker Accounts — Shared mode (one Google account per device, multiple workers) is simpler to manage and more realistic in multi-shift operations. Per-worker accounts enable usage analytics but add account management overhead.
- Organizational Unit (OU) structure — Create a dedicated OU for Glass devices in your Workspace Admin Console. This lets you apply device policies without affecting other Android devices in your fleet.
Applying Device Policies
Using the Android Management API or your EMM console, configure:
- Kiosk / Single-App mode — lock devices to your chosen workflow app; workers shouldn't be opening Gmail on the factory floor
- Screen timeout — set conservatively (90–120 seconds) to extend battery life without frustrating workers
- Network restrictions — whitelist only required domains/IPs
- Disable Google Play updates for non-approved apps
[IMAGE: Screenshot mockup of an MDM console (Workspace ONE style) showing a Glass Enterprise Edition 2 device enrolled in Device Owner mode with kiosk policy applied]
Installing and Configuring Industry-Specific Apps
App Distribution: Managed Google Play vs. Sideloading
Managed Google Play (the enterprise variant of the Play Store) is the right path. IT approves specific apps or private APKs, and the MDM pushes them silently to enrolled devices — no worker interaction required. This matters on a shared device where you want the app already running when a worker picks up the glasses.
Sideloading APKs via ADB is an option for pilots or when an app isn't listed on Play Store, but it creates update management headaches at scale.
Proceedix: Digital Work Instructions
Proceedix is a digital work instructions platform with a GEE2-compatible build. Setup involves:
- Deploy the Proceedix APK via Managed Google Play (request the enterprise build from Proceedix directly if the public listing doesn't appear)
- Configure the server endpoint URL within the app settings or via managed app config in your EMM
- Assign worker accounts or configure shared-device login
- Test barcode scanning — Proceedix uses the GEE2 camera for scan steps; ensure camera permissions are granted via MDM policy
Connectivity requirement: Proceedix streams instruction content in real time; your <100ms latency target matters here.
⚠️ Verify with Proceedix directly that their GEE2 build is still actively maintained post-March 2023 end-of-sale.
Tulip: Manufacturing App Platform
Tulip takes a no-code/low-code approach to manufacturing apps, which is genuinely useful when your line engineers want to build their own guided workflows without going through IT. The Glass-specific UI considerations:
- Tulip's Glass interface is optimized for the 640×360 prism display — avoid importing tablet layouts directly
- Voice command triggers are configurable within Tulip's app editor
- Test thoroughly in your actual ambient noise environment before go-live
A Note on APX Platform (formerly Atheer)
The APX Platform originated with Atheer, which was subsequently acquired by ServiceMax and further integrated into the Salesforce ecosystem. The Atheer/APX brand is effectively discontinued as a standalone product — if this platform was in your evaluation, confirm the current product offering directly with Salesforce/ServiceMax before any configuration work. [Source: https://developers.google.com/glass-enterprise, retrieved 2024-01]
App Permissions Checklist
| Permission | Required By | Grant Method |
|---|---|---|
| Camera | Barcode scanning, visual pick-assist | MDM policy (pre-grant) |
| Microphone | Voice commands | MDM policy (pre-grant) |
| Storage (read/write) | Offline content caching | MDM policy |
| Network access | All streaming apps | Default |
Pre-granting camera and microphone at the MDM level avoids the permission dialog appearing mid-workflow — a small UX detail that workers disproportionately dislike.
Wi-Fi Optimization and Battery Management for Shift-Long Deployments
Access Point Placement and Roaming
The geometry of a warehouse — long aisles, metal racking, machinery — creates RF dead zones that a standard office Wi-Fi deployment won't catch. Practical guidance:
- Conduct a site survey before finalizing AP placement; tools like Ekahau or AirMagnet are worth the time investment for facilities over 50,000 sq ft
- Enable 802.11r (Fast BSS Transition) on your access points — this dramatically reduces the 150–400ms dropout that occurs when a walking worker hands off between APs. Without it, voice commands and app streams stutter at zone boundaries
- 802.11k and 802.11v (neighbor reports and BSS transition management) complement 802.11r; enable all three if your AP vendor supports them
- Aim for -67 dBm or stronger signal strength throughout the operational area
Battery Reality Check
Google's rated 8-hour battery life is a best-case figure. In practice:
- Light use (occasional notifications, minimal scanning): 6–8 hours
- Active warehouse use (continuous barcode scanning, voice commands, streaming): 4–6 hours
- High-ambient-temperature environments (>35°C, foundry/forge settings): expect further reduction and possible thermal throttling — GEE2 will reduce CPU/display performance when it overheats
For three-shift operations, this means charging infrastructure is non-negotiable. Position charging cradles at shift-change stations. A 30-minute partial charge during a shift break can add 1.5–2 hours of runtime — design break areas accordingly.
[IMAGE: Isometric illustration of a warehouse charging station setup with multiple Glass Enterprise Edition 2 devices docked on a wall-mounted cradle near a shift-change area]
Common Issues and Troubleshooting: The 10 Problems Most Teams Hit in Week One
This section is based on the documented failure patterns from enterprise deployments — the kind of problems that appear in support tickets but rarely make it into official documentation.
Issues 1–3: Enrollment Failures
Problem 1 — MDM Token Errors: The Android Enterprise binding between your MDM tenant and Google's Enterprise Management API breaks silently. Fix: re-bind the enterprise in your MDM console and re-attempt enrollment; check that your MDM service account has the correct API scope.
Problem 2 — Pre-existing Personal Google Accounts: If a device was ever signed into a personal Gmail account, it may be device-protected (Factory Reset Protection). Perform a full factory reset and confirm FRP is cleared before MDM enrollment.
Problem 3 — Zero-Touch Portal Sync Delays: The ZTE portal can take 15–30 minutes to sync device assignments. Don't power devices on immediately after uploading the CSV — wait for the portal to confirm sync before first boot.
Issues 4–5: Connectivity Problems
Problem 4 — Wi-Fi Drops During Worker Movement: Almost always an 802.11r issue. Enable fast roaming on your AP infrastructure and verify it's negotiating correctly with GEE2 (check AP-side logs for FT association events).
Problem 5 — App Crashes on Weak Signal: Streaming-dependent apps (Proceedix, Tulip) will crash or freeze when RSSI drops below -75 dBm. Map your signal dead zones and either add APs or redesign worker routes around them.
Issues 6–7: Voice Command Failures
This is the one that surprises teams most. GEE2's voice recognition accuracy drops sharply above 85dB ambient noise — which describes most stamping, machining, and assembly environments.
Problem 6 — Commands Not Recognized: Supplement with touchpad navigation for noisy zones. Some deployments have had success with directional microphone accessories or Bluetooth headsets, but test thoroughly — GEE2's audio routing behavior with BT audio isn't always predictable.
Problem 7 — Wrong Commands Triggered: Background noise patterns can occasionally match command phonemes. Review your app's voice command vocabulary and eliminate short, easily confused terms in noisy environments.
Issues 8–9: Scanning and App Compatibility
Problem 8 — Barcode/QR Scan Failures: GEE2's 8MP camera focuses to approximately 30cm — workers holding items too close or too far will get failed scans. More importantly, scanning performance is highly app-dependent. If you're scanning industrial barcode formats (GS1-128, ITF-14, Data Matrix), verify your app's scanning library handles them. Zebra DataWedge-style middleware can help bridge the gap.
Problem 9 — App Compatibility Errors: This is the long-term risk that matters most. GEE2 is locked to Android 8.1 (API level 27) with no confirmed OS upgrade path. Modern app developers increasingly target API level 33+. Some apps will install but refuse to use newer APIs; others will display deprecation warnings or simply crash. Before committing to any ISV partner, explicitly ask: "Will your Glass build remain functional on API 27 through [your expected device lifecycle end date]?"
Issue 10: Worker Adoption Resistance
The most consistently underestimated problem. Workers raise three objections reliably:
- Weight and head fatigue — 46g on one side of the head becomes noticeable after 90 minutes; worse over safety helmets
- Display eye strain — the right-eye prism causes fatigue for some workers after 2+ hours of continuous use
- Fit over safety glasses — GEE2 has a prescription lens frame option, but fitting over existing safety eyewear is hit-or-miss
The fix isn't technical — it's a structured pilot with feedback loops. Run 2-week pilots with 5–10 volunteer workers, collect ergonomic feedback daily, and use that data to design your training program before broad rollout. Workers who feel consulted adopt faster than workers who feel equipped.
Escalation Path
- Google Enterprise Support: Requires an active enterprise support agreement. Confirm your tier before deployment — post-EOS support terms may differ from active-product support terms. [Source: https://support.google.com/glass-enterprise, retrieved 2024-01]
- ISV Partners: Proceedix, Tulip, and others have their own support channels. Most issues on the app layer are faster to resolve through the ISV than through Google.
- MDM Vendor Support: For enrollment and policy issues, your MDM vendor's support team often has GEE2-specific knowledge — particularly Workspace ONE and Intune teams.
Summary: What to Do Before You Deploy
Deploying GEE2 is absolutely achievable — but the teams that succeed treat it as an infrastructure project, not a hardware unboxing.
Five things to do before you power on a single device:
- Confirm your MDM supports Android Enterprise Device Owner mode and test enrollment on a single unit before touching the rest of your fleet
- Run a proper Wi-Fi site survey — this single investment prevents the majority of Week-One connectivity failures
- Verify app compatibility on Android 8.1 (API 27) with every ISV you plan to use, and ask directly about their maintenance commitment for discontinued hardware
- Design your charging infrastructure for your actual shift pattern, not Google's rated battery figures
- Run an ergonomic pilot before broad rollout — worker adoption resistance is the most common reason enterprise AR programs stall after a successful technical deployment
For teams still in procurement evaluation: given the March 2023 end-of-sale, it's worth reviewing our enterprise AR glasses comparison guide and our RealWear HMT-1 vs. Google Glass Enterprise comparison before making a final decision. The fundamentals in this guide — MDM enrollment, Wi-Fi design, app integration — apply broadly to most Android-based enterprise AR devices.
📥 Download the Google Glass Enterprise Deployment Checklist — a structured pre-deployment and go-live checklist used across enterprise AR deployments in manufacturing and logistics. Get the free checklist →